Merge pull request #1184 from neogopher/address-review-comments

Address review comments

docs/pages/architecture/overview.mdx

@@ -16,7 +16,7 @@ By default, vclusters run as a single pod (scheduled by a StatefulSet) that cons
 - [**Control Plane**](control_plane)
 - [**Syncer**](syncer)
 
-### Host Cluster & Namespace
+## Host Cluster & Namespace
 Every vcluster runs on top of another Kubernetes cluster, called host cluster. Each vcluster runs as a regular StatefulSet inside a namespace of the host cluster. This namespace is called host namespace. Everything that you create inside the vcluster lives either inside the vcluster itself or inside the host namespace. 
 
 It is possible to run multiple vclusters inside the same namespace and you can even run vclusters inside another vcluster (vcluster nesting).

docs/pages/architecture/syncer/single_vs_multins.mdx

@@ -1,4 +1,21 @@
 ---
 title: Single vs Multi Namespace Sync
 sidebar_label: Single vs Multi Namespace Sync
----
+---
+
+[Multinamespace mode Architecture Diagram here]
+
+In this mode vcluster diverges from the [architecture described previously](/architecture/overview). By default, all namespaced resources that need to be synced to the host cluster are created in the namespace where vcluster is installed. But in multi-namespace mode vcluster will create a namespace in the host cluster for each namespace in the virtual cluster. The namespace name is modified to avoid conflicts between multiple vcluster instances in the same host, but the synced namespaced resources are created with the same name as in the virtual cluster. To enable this mode use the following helm value:
+
+```yaml
+multiNamespaceMode:
+  enabled: true
+```
+
+:::warning This mode must be enabled during vcluster creation.
+Enabling, or disabling, it on an existing vcluster instance will force it into an inconsistent state.
+:::
+
+:::warning Alpha feature
+Multi-namespace mode is currently in an alpha state. This is an advanced feature that requires more permissions in the host cluster, and as a result, it can potentially cause significant disruption in the host cluster. 
+:::