diff --git a/docs/dci-deploysas9.md b/docs/dci-deploysas9.md
index 9f52f74..9b44419 100644
--- a/docs/dci-deploysas9.md
+++ b/docs/dci-deploysas9.md
@@ -146,9 +146,34 @@ The items deployed to metadata include:
 
 We strongly recommend that the Data Controller configuration tables are stored in a database for concurrency reasons.
 
-We have customers in production using Oracle, Postgres, Netezza, SQL Server to name a few.  Contact us for support with DDL and migration steps for your chosen vendor.
+We have customers in production using Oracle, Postgres, Netezza, Redshift and SQL Server to name a few.  Contact us for support with DDL and migration steps for your chosen vendor.
 
 !!! note
     Data Controller does NOT modify schemas! It will not create or drop tables, or add/modify columns or attributes.  Only data _values_ (not the model) can be modified using this tool.
 
 To caveat the above - it is also quite common for customers to use a BASE engine library.  Data Controller ships with mechananisms to handle locking (internally) but it cannot handle external contentions, such as those caused when end users open datasets directly, eg with Enterprise Guide or Base SAS.
+
+
+## Redeployment
+
+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)
+* _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
+* 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 
+* Test and make sure the new instance works as expected
+* Delete (or rename) the **old** instance 
+  * Metadata + frontend, NOT the underlying DC library data
+* Rename the new instance so it is the same as the old
+  * 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.
\ No newline at end of file
diff --git a/mkdocs.yml b/mkdocs.yml
index 2f074e7..d23a125 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -45,9 +45,9 @@ nav:
 - Macros: macros.md
 - Installation:
     - System Requirements: dci-requirements.md
-    - SAS Viya Deploy: dci-deploysasviya.md
-    - SAS 9 Deploy: dci-deploysas9.md
-    - SAS 9 Dedicated STP: dci-stpinstance.md
+    - SAS Viya: dci-deploysasviya.md
+    - SAS 9 EBI: dci-deploysas9.md
+    - SAS 9 STP Hardening: dci-stpinstance.md
     - Troubleshooting: dci-troubleshooting.md
 - Legal:
     - Privacy Policy: privacy.md