remove commented text

Author: ekpgh

articles/hpc-cache/add-namespace-paths.md

@@ -70,18 +70,6 @@ When planning your namespace for an NFS storage target, keep in mind that each p
 
 All of the namespace paths for an NFS storage system are created on one storage target. Most cache configurations can support up to ten namespace paths per storage target, but larger configurations can support up to 20.
 
-<!-- | Throughput value | Cache size | Maximum number of namespace paths per storage target |
-|------------------|------------|------------------------------------------------------|
-| Up to 2 GB/s     | 3 TB       | 10                                                   |
-| Up to 2 GB/s     | 6 TB       | 10                                                   |
-| Up to 2 GB/s     | 12 TB      | 20                                                   |
-| Up to 4 GB/s     | 6 TB       | 10                                                   |
-| Up to 4 GB/s     | 12 TB      | 10                                                   |
-| Up to 4 GB/s     | 24 TB      | 20                                                   |
-| Up to 8 GB/s     | 12 TB      | 10                                                   |
-| Up to 8 GB/s     | 24 TB      | 10                                                   |
-| Up to 8 GB/s     | 48 TB      | 20                                                   | -->
-
 This list shows the maximum number of namespace paths per configuration.
 
 * Up to 2 GB/s throughput:

articles/hpc-cache/hpc-cache-add-storage.md

@@ -62,8 +62,6 @@ To define an Azure Blob container, enter this information.
 
   ![screenshot of dialog to specify name and access level (private) for new container](media/add-blob-new-container.png)
 
-<!-- * **Virtual namespace path** - Set the client-facing file path for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature. -->
-
 When finished, click **OK** to add the storage target.
 
 > [!NOTE]
@@ -210,22 +208,6 @@ Provide this information for an NFS-backed storage target:
 * **Hostname** - Enter the IP address or fully qualified domain name for your NFS storage system. (Use a domain name only if your cache has access to a DNS server that can resolve the name.)
 
 * **Usage model** - Choose one of the data caching profiles based on your workflow, described in [Choose a usage model](#choose-a-usage-model) above.
-<!--
-### NFS namespace paths
-
-An NFS storage target can have multiple virtual paths, as long as each path represents a different export or subdirectory on the same storage system.
-
-Create all of the paths from one storage target.
-
-You can [add and edit namespace paths](hpc-cache-edit-storage.md) on a storage target at any time.
-
-Fill in these values for each namespace path:
-
-* **Virtual namespace path** - Set the client-facing file path for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
-
-* **NFS export path** - Enter the path to the NFS export.
-
-* **Subdirectory path** - If you want to mount a specific subdirectory of the export, enter it here. If not, leave this field blank. -->
 
 When finished, click **OK** to add the storage target.
 

articles/hpc-cache/hpc-cache-edit-storage.md

@@ -98,7 +98,7 @@ Details are below:
 
 You can use the Azure portal or the Azure CLI to change the client-facing namespace path, the storage export, and the export subdirectory (if used).
 
-Read the guidelines in [Add NFS namespace paths](add-namespace-paths.md#nfs-namespace-paths) if you need a reminder about how to create multiple valid paths on one storage target. <!-- is there some limit on junctions too? there was email about it -->
+Read the guidelines in [Add NFS namespace paths](add-namespace-paths.md#nfs-namespace-paths) if you need a reminder about how to create multiple valid paths on one storage target.
 
 ### [Portal](#tab/azure-portal)