Merge branch 'headings' of https://github.com/jpouellet/qubes-doc into jpouellet-headings

building/qubes-builder.md

@@ -126,7 +126,7 @@ If you want to somehow modify sources, you can also do it, here are some basic s
         make iso
 
 Code verification keys management
-=================================
+---------------------------------
 
 [QubesBuilder](/doc/qubes-builder/) by default verifies signed tags on every downloaded code. Public keys used for that are stored in `keyrings/git`. By default Qubes developers' keys are imported automatically, but if you need some additional keys (for example your own), you can add them using:
 

customization/dispvm-customization.md

@@ -9,8 +9,11 @@ redirect_from:
 - /wiki/UserDoc/DispVMCustomization/
 ---
 
+DispVM Customization
+====================
+
 Changing the template used as a basis for Disposable VM
-========================================================
+-------------------------------------------------------
 
 You may want to use a non-default template as a basis for Disposable VM. One example is to use a less-trusted template with some less trusted, 3rd party, often unsigned, applications installed, such as e.g. 3rd part printer drivers.
 
@@ -33,7 +36,7 @@ One can easily verify if the new Disposable VM template is indeed based on a cus
 
 
 Customization of Disposable VM
-==============================
+------------------------------
 
 It is possible to change the settings of each new Disposable VM (DispVM). This can be done by customizing the DispVM template:
 

managing-os/templates/debian/upgrade-8-to-9.md

@@ -17,7 +17,7 @@ Disclaimer: Debian 9 (Stretch) is marked testing for a reason. You may notice st
 Please note that if you installed packages from one of the testing repositories you must make sure that the repository is enabled in `/etc/apt/sources.list.d/qubes-r3.list` before attempting the upgrade. Otherwise, your upgrade will [break](https://github.com/QubesOS/qubes-issues/issues/2418).
 
 Summary: Upgrading a Debian 8 Template to Debian 9
--------------------------------------------------------------
+--------------------------------------------------
 
         [user@dom0 ~]$ qvm-clone debian-8 debian-9
         [user@dom0 ~]$ qvm-run -a debian-9 gnome-terminal
@@ -81,7 +81,7 @@ any template based on the standard Debian 8 template.
 	
 
 Compacting the Upgraded Template
-================================
+--------------------------------
 
 Neither `fstrim` nor the `discard` mount option works on the TemplateVM's root
 filesystem, so when a file is removed in the template, space is not freed in
@@ -113,7 +113,7 @@ TemplateVM's max size + the actually used space there) free space in dom0.
         [user@dom0 ~]$ mv root.img.new root.img
 
 Additional Information
-======================
+----------------------
 
 It should be noted that Debian 9 (Stretch) is currently marked testing and
 should be treat as such. For projects that need absolute stability, upgrading

managing-os/templates/fedora/upgrade-18-to-20.md

@@ -51,7 +51,7 @@ sudo yum --releasever=20 --setopt=cachedir=/mnt/removable distro-sync
 After upgrade is finished, you can remove /var/tmp/template-upgrade-cache.img file.
 
 Compacting templates root.img
-=============================
+-----------------------------
 
 fstrim, nor "discard" mount option do not work on template root fs, so when some file is removed in the template, space isn't freed in dom0. This means that template will use about twice a space that is really need after upgrade.
 

managing-os/templates/fedora/upgrade-20-to-21.md

@@ -158,7 +158,7 @@ minimal template) is the same as the procedure for the standard template above,
 
 
 Compacting the Upgraded Template
-================================
+--------------------------------
 
 Neither `fstrim` nor the `discard` mount option works on the TemplateVM's root
 filesystem, so when a file is removed in the template, space is not freed in
@@ -191,7 +191,7 @@ TemplateVM's max size + the actually used space there) free space in dom0.
 
 
 Additional Information
-======================
+----------------------
 
 As mentioned above, you may encounter the following `yum` error:
 
@@ -220,6 +220,6 @@ list which also apply to TemplateVM management and migration in general:
  * [Jason M](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/5PxDfI-RKAsJ)
 
 Known issues with Fedora 21
-===========================
+---------------------------
 
 * [The "Update VM" command in Qubes Manager does not work](https://github.com/QubesOS/qubes-issues/issues/982).

managing-os/templates/fedora/upgrade-21-to-23.md

@@ -141,7 +141,7 @@ minimal template) is the same as the procedure for the standard template above,
 
 
 Compacting the Upgraded Template
-================================
+--------------------------------
 
 Neither `fstrim` nor the `discard` mount option works on the TemplateVM's root
 filesystem, so when a file is removed in the template, space is not freed in
@@ -174,7 +174,7 @@ TemplateVM's max size + the actually used space there) free space in dom0.
 
 
 Additional Information
-======================
+----------------------
 
 As mentioned above, you may encounter the following `yum` error:
 
@@ -203,13 +203,13 @@ list which also apply to TemplateVM management and migration in general:
  * [Jason M](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/5PxDfI-RKAsJ)
 
 Upgrading to Fedora 22
-======================
+----------------------
 
 You may choose to upgrade to Fedora 22 instead of Fedora 23. In that case,
 simply replace version "23" with "22" in all above commands.
 
 Known issues with Fedora 23
-===========================
+---------------------------
 
 * [Graphical update tools (using PackageKit) does not work](https://github.com/QubesOS/qubes-issues/issues/982).
 * [Dnf (new Fedora package manager) needs a lot of time to process repository metadata](https://bugzilla.redhat.com/show_bug.cgi?id=1227014), you may want to use `yum-deprecated` for now

managing-os/windows/uninstalling-windows-tools-2.md

@@ -60,7 +60,7 @@ If you need network access to copy the uninstall script to the HVM, use *Safe Mo
 
 
 The uninstall script
-====================
+--------------------
 
 Save it as a .BAT file in the HVM and run in Safe Mode.