docs: merge mutlsitore docs

Author: jagoral

Diff for: docs/content/guides/7.multistore/3.patterns/5.subpath/1.subpath.md

@@ -24,14 +24,47 @@ For example, with this setup you could have:
 
 All of this is served from a single Frontend deployment.
 
-## Setting Up the Middleware
+### How Config Switcher Works
 
-The first step is to configure your Middleware to support different configurations using the Config Switcher extension.
+The Config Switcher dynamically changes your middleware integration configuration based on the current request configuration ID sent with the `x-alokai-middleware-config-id` header. This means:
+
+1. **Path-Based Configuration**
+    - Different configuration ID set by different paths allow to fetch data from different sources
+    - Example: `/apparel` path shows apparel products, while `/electronics` shows electronics products
+
+2. **Configuration ID vs Store ID**
+    - Each configuration has its own distinct ID
+    - This is different from the store ID (`storeId`)
+    - Multiple configurations can exist within a single store
+
+3. **Same-Store Operation**
+    - Config Switcher works within a single store instance
+    - It extracts the configuration ID from the request
+    - It executes requests using the appropriate configuration
 
 ::tip Config Switcher Documentation
 This section provides a brief overview of setting up Config Switcher. For complete documentation, refer to the [Config Switcher guide](https://docs.alokai.com/middleware/guides/config-switcher).
 ::
 
+### Key Distinctions To File-Based Inheritance
+
+`ConfigSwitcher` operates differently from file-based inheritance:
+
+| **File-Based Inheritance**              | **Config Switcher**                                              |
+| --------------------------------------- | ---------------------------------------------------------------- |
+| Works **between different stores**      | Works **within a single store**                                  |
+| Creates separate deployable instances   | Uses a single deployable instance                                |
+| Full codebase customization             | Only middleware configuration changes, Storefront code is shared |
+| Requires separate builds for each store | Single build supports multiple configurations                    |
+
+Take a look at the diagram to see the difference:
+
+<img src="../../img/file-based-vs-switcher-diagram.png" alt="Comparison of File-based Inheritance vs Config Switcher" class="mx-auto">
+
+## Setting Up the Middleware
+
+The first step is to configure your Middleware to support different configurations using the Config Switcher extension.
+
 Create a Config Switcher extension for your integration:
 
 ```ts