diff --git a/doc/deploymentCompose.md b/doc/deploymentCompose.md
new file mode 100644
index 0000000000000000000000000000000000000000..052db7329edfabc075123230eac6a3a4648df1c0
--- /dev/null
+++ b/doc/deploymentCompose.md
@@ -0,0 +1 @@
+Docker Compose WIP
\ No newline at end of file
diff --git a/doc/deploymentK8s.md b/doc/deploymentK8s.md
new file mode 100644
index 0000000000000000000000000000000000000000..537b5ab8fe747f73e19ab4862a09aaa5fca9d81d
--- /dev/null
+++ b/doc/deploymentK8s.md
@@ -0,0 +1 @@
+Kubernetes WIP
\ No newline at end of file
diff --git a/doc/nfvoconfig.md b/doc/nfvoconfig.md
index 2247a7c66ac0c05be49924d83b456fd76ec62805..ed437de5155ddaec707405ce63817e37de248232 100644
--- a/doc/nfvoconfig.md
+++ b/doc/nfvoconfig.md
@@ -10,11 +10,13 @@ Configuration of your target(s) NFVOs/MANO services with Openslice is performed
 
 3. Navigate to Admin > Manage MANO providers > Add New MANO Provider and enter its details:
 
-* Name and description of your choice. The selected name will supplement the NFV artifacts of this provider.
-* One of the already defined MANO platforms
-* API URL Endpoint, eg: https://10.10.10.10:9999 (This is the SOL005 NBI endpoint - *Note the port 9999*)
-* Username, Password and Project of your OSM tenant.
+    - Name and description of your choice. The selected name will supplement the NFV artifacts of this provider.
+    - One of the already defined MANO platformssynchronization
+    - API URL Endpoint, eg: https://10.10.10.10:9999 (This is the SOL005 NBI endpoint - *Note the port 9999*)
+    - Username, Password and Project of your OSM tenant.
 
 Check EnabledForONBOARDING, if you want VNF/NS packages uploaded through the UI by the user, to also be automatically ONBOARDED to this MANO (1 step process). If left unchecked, the onboarding process must be performed manually after the VNF/NS package is uploaded to the portal, by the designated UI (2 step process).
 
-Check EnabledForSYNC, if you want to support the automatic synchronization of this MANO with OpenSlice. When enabled, the existing VNF/NS packages and VIMs (and any updates on them) of the registered MANO are also reflected to the portal to the respective UIs (Registered VNFs/NSDs and Manage Infrastructures). The synchronization is a continuous process that will confirm that the artifacts are still present in the MANO, updating the status field of the respective artifacts to `OSM_PRESENT`. If during this process, an artifact is deleted from the MANO, the respective status field will be updated to `OSM_MISSING`.
\ No newline at end of file
+Check EnabledForSYNC, if you want to support the automatic synchronization of this MANO with OpenSlice. When enabled, the existing VNF/NS packages and VIMs (and any updates on them) of the registered MANO are also reflected to the portal to the respective UIs (Registered VNFs/NSDs and Manage Infrastructures). 
+
+The synchronization is a continuous process that will confirm that the artifacts are still present in the MANO, updating the status field of the respective artifacts to `OSM_PRESENT`. If during this process, an artifact is deleted from the MANO, the respective status field will be updated to `OSM_MISSING`.
\ No newline at end of file
diff --git a/mkdocs.yml b/mkdocs.yml
index 2236d6a58e132d88d413d4b156c44b7b3ce958bf..daabd12871b4726310016ca0bc9c7d1482d8cbb9 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -72,7 +72,10 @@ nav:
   - Overview:
       - Introduction: index.md
   - Getting Started:
-      - Deployment/Installation: deployment.md
+      - Deployment/Installation: 
+          - deployment.md
+          - Docker Compose: deploymentCompose.md
+          - Kubernetes: deploymentK8s.md
       - NFV Orchestrator Configuration: nfvoconfig.md
       - Service Catalogs: catalogs.md
       - NFV Catalogs: nfvcatalogs.md