Edits to recovery page, add to navigation.

Author: Nathan Tallman

docs/preservation/recovery.md

@@ -5,20 +5,20 @@ When a fixity check fails, APTrust sends an alert to Institutional Admin users a
 ## High Assurance
 
 - This class includes two copies:
-  - **Hot copy (S3)** – used for regular access and fixity checks.
-  - **Cold copy (Glacier)** – used as a second copy.
+    - **Hot copy (S3)** – used for regular access and fixity checks.
+    - **Cold copy (Glacier)** – used as a second copy.
 
 - Fixity checks are performed on the hot (S3) copy.
 - If a fixity check fails:
-  1. Contact APTrust support.
-  2. We will work with you to restore the Glacier copy.
-  3. We'll verify the Glacier copy's fixity.
-  4. If valid, we’ll replace the corrupted S3 copy with the Glacier version and record a PREMIS event.
+    1. Contact APTrust support.
+    2. We will work with you to restore the Glacier copy.
+    3. We'll verify the Glacier copy's fixity.
+    4. If valid, we’ll replace the corrupted S3 copy with the Glacier version and record a PREMIS event.
 
 ## Basic Archive and Deep Archive
 
 - These classes store **a single copy only**.
 - If a fixity check fails, the object cannot be recovered by APTrust.
 - To remediate:
-  - Deposit a new version of the object.
-  - Use an [update bag](updates.md) to replace the corrupted file in preservation storage.
+    1. Deposit a new version of the object.
+    2. Use an [update bag](updates.md) to replace the corrupted file in preservation storage. You only need to include the impacted file (keeping the same file name and path).

mkdocs.yml

@@ -29,6 +29,7 @@ nav:
   - Preservation Actions:
       - preservation/ingest.md
       - preservation/updates.md
+      - preservation/recovery.md
       - preservation/restoration.md
       - preservation/deletion.md
   - Depositing: