fix: redeploy process

docs/dci-deploysas9.md

@@ -161,19 +161,19 @@ The full redeployment process is as follows:
 * Back up metadata (export DC folder as SPK file)
 * Back up the physical tables in the DC library
 * Deploy a brand new instance of DC
-  - To a new metadata folder
-  - To a new frontend folder (if full deploy)
+    - To a new metadata folder
+    - To a new frontend folder (if full deploy)
 * _Delete_ the **new** DC library (metadata + physical tables)
 * _Move_ the **old** DC library (metadata only) to the new DC metadata folder
 * Copy the _content_ of the old `services/public/Data_Controller_Settings` STP to the new one
-  - This will link the new DC instance to the old DC library / logs directory
-  - It will also re-apply any site-specific DC mods
+    - This will link the new DC instance to the old DC library / logs directory
+    - It will also re-apply any site-specific DC mods
 * Run any/all DB migrations between the old and new DC version
-  - See [migrations](https://git.datacontroller.io/dc/dc/src/branch/main/sas/sasjs/db/migrations) folder 
+    - See [migrations](https://git.datacontroller.io/dc/dc/src/branch/main/sas/sasjs/db/migrations) folder 
 * Test and make sure the new instance works as expected
 * Delete (or rename) the **old** instance 
-  - Metadata + frontend, NOT the underlying DC library data
+    - Metadata + frontend, NOT the underlying DC library data
 * Rename the new instance so it is the same as the old
-  - Both frontend and metadata
+    - Both frontend and metadata
 
 If you are unfamiliar with, or unsure about, the above steps - don't hesitate to contact the Data Controller team for assistance and support.