Wrap lines and use actual numbering

This file is an exception to the normal line wrapping rule, since it is
specifically intended to be read as plain text.

common-tasks/backup-emergency-restore-v2.md

@@ -10,11 +10,16 @@ redirect_from:
 Emergency Backup Recovery without Qubes - format version 2
 ==========================================================
 
-This page describes how to perform emergency restore of backup created on Qubes R2 Beta3 or earlier (which uses backup format 2).
+This page describes how to perform emergency restore of backup created on Qubes
+R2 Beta3 or earlier (which uses backup format 2).
 
-The Qubes backup system has been designed with emergency disaster recovery in mind. No special Qubes-specific tools are required to access data backed up by Qubes. In the event a Qubes system is unavailable, you can access your data on any GNU/Linux system with the following procedure.
+The Qubes backup system has been designed with emergency disaster recovery in
+mind. No special Qubes-specific tools are required to access data backed up by
+Qubes. In the event a Qubes system is unavailable, you can access your data on
+any GNU/Linux system with the following procedure.
 
-**Note:** In the following example, the backup file is assumed to be both encrypted and compressed.
+**Note:** In the following example, the backup file is assumed to be both
+encrypted and compressed.
 
 1.  Untar the main backup file.
 
@@ -36,7 +41,7 @@ The Qubes backup system has been designed with emergency disaster recovery in mi
     dom0-home/dom0user.000.hmac
     ~~~
 
-1.  Verify the integrity of the `private.img` file which houses your data.
+2.  Verify the integrity of the `private.img` file which houses your data.
 
     ~~~
     [user@restore ~]$ cd vm1/
@@ -46,11 +51,15 @@ The Qubes backup system has been designed with emergency disaster recovery in mi
     (stdin)= cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
     ~~~
 
-  **Note:** The hash values should match. If they do not match, then the backup file may have been tampered with, or there may have been a storage error.
+  **Note:** The hash values should match. If they do not match, then the backup
+  file may have been tampered with, or there may have been a storage error.
 
-  **Note:** If your backup was hashed with a message digest algorithm other than `sha512`, you must substitute the correct message digest command. A complete list of supported message digest algorithms can be found with `openssl list-message-digest-algorithms`.
+  **Note:** If your backup was hashed with a message digest algorithm other
+  than `sha512`, you must substitute the correct message digest command. A
+  complete list of supported message digest algorithms can be found with
+  `openssl list-message-digest-algorithms`.
 
-1.  Decrypt the `private.img` file.
+3.  Decrypt the `private.img` file.
 
     ~~~
     [user@restore vm1]$ openssl enc -d -pass pass:your_passphrase -aes-256-cbc -in private.img.000 -out private.img.dec.000
@@ -65,18 +74,22 @@ The Qubes backup system has been designed with emergency disaster recovery in mi
   done
   ~~~
 
-  **Note:** If your backup was encrypted with a cipher algorithm other than `aes-256-cbc`, you must substitute the correct cipher command. A complete list of supported cipher algorithms can be found with `openssl list-cipher-algorithms`.
+  **Note:** If your backup was encrypted with a cipher algorithm other than
+  `aes-256-cbc`, you must substitute the correct cipher command. A complete
+  list of supported cipher algorithms can be found with `openssl
+  list-cipher-algorithms`.
 
-1.  Decompress the decrypted `private.img` file.
+4.  Decompress the decrypted `private.img` file.
 
     ~~~
     [user@restore vm1]$ zforce private.img.dec.*
     [user@restore vm1]$ gunzip private.img.dec.000.gz
     ~~~
 
-  **Note:** If your backup was compressed with a program other than `gzip`, you must substitute the correct compression program.
+  **Note:** If your backup was compressed with a program other than `gzip`, you
+  must substitute the correct compression program.
 
-1.  Untar the decrypted and decompressed `private.img` file.
+5.  Untar the decrypted and decompressed `private.img` file.
 
     ~~~
     [user@restore vm1]$ tar -M -xvf private.img.dec.000
@@ -95,9 +108,10 @@ The Qubes backup system has been designed with emergency disaster recovery in mi
         ~~~
 
     2.  `chmod +x new-volume-script`.
-    3.  `tar --new-volume-script=./new-volume-script -xvf private.img.dec.000`. (The `--new-volume-script` option enables multi-volume untaring.)
+    3.  `tar --new-volume-script=./new-volume-script -xvf private.img.dec.000`.
+        (The `--new-volume-script` option enables multi-volume untaring.)
 
-1.  Mount the private.img file and access your data.
+6.  Mount the private.img file and access your data.
 
     ~~~
     [user@restore vm1]$ sudo mkdir /mnt/img
@@ -106,6 +120,9 @@ The Qubes backup system has been designed with emergency disaster recovery in mi
     This data has been successfully recovered!
     ~~~
 
-  **Note:** You may wish to store a plain text copy of these instructions with your Qubes backups in the event that you fail to recall the above procedure while this web page is inaccessible. You may obtain a plaintext version of this file in Git repository housing all the documentation at:
+  **Note:** You may wish to store a plain text copy of these instructions with
+  your Qubes backups in the event that you fail to recall the above procedure
+  while this web page is inaccessible. You may obtain a plaintext version of
+  this file in Git repository housing all the documentation at:
 
     https://github.com/QubesOS/qubes-doc.git