Remove extra newlines at the beginning/end of files

Those are redundant, and yaml parser strips them in fact. By removing
them, loading and saving yaml file without any change indeed produce the
same output. This is useful for prepare_for_translation.py script (which
adds lang and ref tags) - to produce only change that indeed was made.

developer/debugging/automated-tests.md

@@ -9,7 +9,6 @@ ref: 45
 title: Automated Tests
 ---
 
-
 ## Unit and Integration Tests
 
 Starting with Qubes R3 we use [python unittest](https://docs.python.org/3/library/unittest.html) to perform automatic tests of Qubes OS.
@@ -260,4 +259,3 @@ In practice, however, either Xen or QEMU crashes when this is attempted.
 Nonetheless, PV works well, which is sufficient for automated installation testing.
 
 Thanks to an anonymous donor, our openQA system is hosted in a datacenter on hardware that meets these requirements.
-

developer/debugging/mount-lvm-image.md

@@ -6,7 +6,6 @@ ref: 46
 title: How to Mount LVM Images
 ---
 
-
 You want to read your LVM image (e.g., there is a problem where you can't start any VMs except dom0).
 
 1: make the image available for qubesdb.
@@ -53,4 +52,3 @@ From the GUI, or from the command line:
 # References
 
 Please consult this issue's [comment](https://github.com/QubesOS/qubes-issues/issues/4687#issuecomment-451626625).
-

developer/debugging/profiling.md

@@ -10,7 +10,6 @@ ref: 48
 title: Python Profiling
 ---
 
-
 This is a python profiling primer.
 
 For the purpose of this document, `qubes-dev` is name of the domain used for postprocessing profiling stats.

developer/debugging/safe-remote-ttys.md

@@ -8,7 +8,6 @@ ref: 49
 title: Safe Remote Dom0 Terminals
 ---
 
-
 If you do not have working graphics in Dom0, then using a terminal can be quite annoying!
 This was the case for the author while trying to debug PCI-passthrough of a machine's primary (only) GPU.
 

developer/debugging/test-bench.md

@@ -10,7 +10,6 @@ ref: 44
 title: How to Set Up a Test Bench
 ---
 
-
 This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal.
 
 We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/doc/qubes-builder/) and you have it set up and running flawlessly.

developer/debugging/vm-interface.md

@@ -11,7 +11,6 @@ ref: 47
 title: VM Configuration Interface
 ---
 
-
 Qubes VM have some settings set by dom0 based on VM settings. There are multiple configuration channels, which includes:
 
 - QubesDB

developer/debugging/windows-debugging.md

@@ -10,7 +10,6 @@ ref: 50
 title: Windows Debugging
 ---
 
-
 Debugging Windows code can be tricky in a virtualized environment. The guide below assumes Xen hypervisor and Windows 7 VMs.
 
 User-mode debugging is usually straightforward if it can be done on one machine. Just duplicate your normal debugging environment in the VM.