Merge PR #285392 notes and suggestions

Author: yousefi-msft

articles/modeling-simulation-workbench/concept-chamber.md

@@ -11,7 +11,7 @@ ms.date: 01/01/2023
 ---
 # Chambers in the Azure Modeling and Simulation Workbench
 
-In the Azure Modeling and Simulation Workbench, Chambers are a security boundary for a group virtual machines (VM) (nodes) and share common users. A Chamber provides a full-featured and secure environment for users to run engineering applications and workloads together in isolation. Chamber VMs are all on the same subnet and have no internet access.
+In the Azure Modeling and Simulation Workbench, chambers are a security boundary for a group virtual machines (VM) (nodes) and share common users. A chamber provides a full-featured and secure environment for users to run engineering applications and workloads together in isolation. chamber VMs are all on the same subnet and have no internet access.
 
 ## Key features
 
@@ -21,25 +21,25 @@ In the Azure Modeling and Simulation Workbench, Chambers are a security boundary
 
 ## Chamber environment
 
-Chambers create a secure and isolated environment by adding private IP access and removing internet access. Public domain access is restricted to authorized networks over encrypted sessions enabled by the connector component. A [Connector](./concept-connector.md)  exists per chamber that supports the protocols established through VPN, Azure Express Route, or allowlisted Public IP addresses.
+Chambers create a secure and isolated environment by adding private IP access and removing internet access. Public domain access is restricted to authorized networks over encrypted sessions enabled by the connector component. A [connector](./concept-connector.md)  exists per chamber that supports the protocols established through VPN, Azure Express Route, or allowlisted Public IP addresses.
 
-Only provisioned users can access the chamber environment. User provisioning is done at the Chamber level using Azure's [Identity Access Management](/azure/role-based-access-control/role-assignments-portal). This enables cross-team and/or cross-organization collaboration on the same projects through  Chambers. Multifactor authentication (MFA) enabled through Microsoft Entra ID is recommended to enhance your organization's security.
+Only provisioned users can access the chamber environment. User provisioning is done at the chamber level using Azure's [Identity Access Management](/azure/role-based-access-control/role-assignments-portal). This enables cross-team and/or cross-organization collaboration on the same projects through chambers. Multifactor authentication (MFA) enabled through Microsoft Entra ID is recommended to enhance your organization's security.
 
 ## Chamber storage
 
-Users can resize and tailor the chambers to support storage requirement needs throughout the design process. Chamber users can also allocate Chamber VMs on demand, select the right-sized VM/CPU for the task/job at hand, and decommission the workload when the job is done to save costs.
+Users can resize and tailor the chambers to support storage requirement needs throughout the design process. Chamber users can also allocate chamber VMs on demand, select the right-sized VM/CPU for the task/job at hand, and decommission the workload when the job is done to save costs.
 
 ### Cost optimization
 
 Administrators can optimize their resource consumption without necessarily destroying resources or moving data by:
 
 * Managing the size and number of virtual machines.
-* [Idling](./how-to-guide-idle.md) unused Connectors and Chambers to reduce cost without deleting VMs or storage.
-* Managing the size and performance tier of Chamber storages.
+* [Idling](./how-to-guide-idle.md) unused connectors and chambers to reduce cost without deleting VMs or storage.
+* Managing the size and performance tier of chamber storages.
 
 Learn more about reducing service costs using [Azure Advisor](/azure/advisor/advisor-cost-recommendations#optimize-spend-for-mariadb-mysql-and-postgresql-servers-by-right-sizing) and [right-size VMs best practices](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs#best-practice-right-size-vms).
 
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Create a Chamber VM](./how-to-guide-chamber.md)
+> [Create a chamber VM](./how-to-guide-chamber.md)

articles/modeling-simulation-workbench/concept-connector.md

@@ -12,25 +12,25 @@ ms.date: 01/01/2023
 ---
 # Connectors in Azure Modeling and Simulation Workbench
 
-Connectors define the network access method between users and the Azure Modeling and Simulation Workbench Chamber. Connectors support connectivity through allowlisted public IPs, VPN, or Azure ExpressRoute. A Chamber can have only one Connector configured at a time. Connectors also configure copy-paste functionality into Chamber VMs. Connector types are immutable and once created can't be changed to another access model. Connectors are part of the Idle mode setting to reduce cost.
+Connectors define the network access method between users and the Azure Modeling and Simulation Workbench chamber. Connectors support connectivity through allowlisted public IPs, VPN, or Azure ExpressRoute. A chamber can have only one connector configured at a time. Connectors also configure copy-paste functionality into chamber VMs. Connector types are immutable and once created can't be changed to another access model. Connectors are part of the Idle mode setting to reduce cost.
 
 ## Public IP access via allowlist
 
-The Workbench can be built to allow users to connect directly from the internet, allowing flexible, open access. When a Public IP Connection is built, connections are permitted using an allowlist. The allowlist uses CIDR (Classless Interdomain Routing) notation to conveniently manage access from large network ranges, such as conference centers or corporate exit nodes. Only IPs listed in the allowlist are able to make connections to its associated Chamber.
+The Workbench can be built to allow users to connect directly from the internet, allowing flexible, open access. When a Public IP Connection is built, connections are permitted using an allowlist. The allowlist uses CIDR (Classless Interdomain Routing) notation to conveniently manage access from large network ranges, such as conference centers or corporate exit nodes. Only IPs listed in the allowlist are able to make connections to its associated chamber.
 
 ## Private Azure networking
 
-A Connector can be created for private network access from Azure virtual networks. This method is best suited where a private or controlled connection is required. Azure ExpressRoutes provide a dedicated connection from an on-premises infrastructure to an Azure data center and can be peered to the Workbench. With a VPN gateway, the Workbench can use a private network with extra encryption layers.
+A connector can be created for private network access from Azure virtual networks. This method is best suited where a private or controlled connection is required. Azure ExpressRoutes provide a dedicated connection from an on-premises infrastructure to an Azure data center and can be peered to the Workbench. With a VPN gateway, the Workbench can use a private network with extra encryption layers.
 
 ### VPN
 
-A VPN Connector can be created which deploys infrastructure specifically for VPN access. The VPN Connector is required if the Chamber is accessed through a point-to-site or site-to-site VPN.
+A VPN connector can be created which deploys infrastructure specifically for VPN access. The VPN connector is required if the chamber is accessed through a point-to-site or site-to-site VPN.
 
 ### Azure ExpressRoute
 
-[Azure ExpressRoute](/azure/expressroute/expressroute-introduction) provides secure, dedicated, encrypted connectivity from on-premises to an Azure landing zone. A Workbench Owner must create a Connector expressly for ExpressRoute, providing the necessary virtual network, supporting network infrastructure, and peer the appropriate vnets.
+[Azure ExpressRoute](/azure/expressroute/expressroute-introduction) provides secure, dedicated, encrypted connectivity from on-premises to an Azure landing zone. A Workbench Owner must create a connector expressly for ExpressRoute, providing the necessary virtual network, supporting network infrastructure, and peer the appropriate vnets.
 
 ## Next step
 
 > [!div class="nextstepaction"]
-> [Create a Connector](./how-to-guide-set-up-networking.md)
+> [Create a connector](./how-to-guide-set-up-networking.md)

articles/modeling-simulation-workbench/concept-data-pipeline.md

@@ -24,9 +24,9 @@ Users with access to the chamber can bring data into the chamber via AzCopy and
 
 Users with access to the chamber can export data from the chamber via the data pipeline.
 
-1. **Identify file to export.** The export process is triggered when a user places a file to export into a designated area within the chamber.  A Chamber Admin or Chamber User copies the file to the data out folder within the pipeline. The data pipeline detects the copied file and creates a file object. The file creation activity is traceable in the logs and enables the next step of the data pipeline.
+1. **Identify file to export.** The export process is triggered when a user places a file to export into a designated area within the chamber.  A chamber Admin or chamber User copies the file to the data out folder within the pipeline. The data pipeline detects the copied file and creates a file object. The file creation activity is traceable in the logs and enables the next step of the data pipeline.
 
-1. **Request file to export.** A Chamber Admin reviews files staged in the data pipeline and requests to export. The pipeline manager creates a file request object. The export request activity is traceable in the logs and enables the next step of the data pipeline.
+1. **Request file to export.** A chamber Admin reviews files staged in the data pipeline and requests to export. The pipeline manager creates a file request object. The export request activity is traceable in the logs and enables the next step of the data pipeline.
 
 1. **Approve/reject export request.** The Workbench Owner either approves or rejects the export file request. Only a Workbench Owner can approve or reject requests. The individual who approves or denies can't be the same person who initially requested the export.
 

articles/modeling-simulation-workbench/concept-storage.md

@@ -15,32 +15,32 @@ The Modeling and Simulation Workbench offers several tiers of storage classes. T
 
 ## Local storage on VMs
 
-Depending on the [Virtual Machine (VM) selected](./concept-vm-offerings.md), local temporary storage might not be available. Modeling and Simulation Workbench doesn't have controls for specifying data and OS disks as in conventional Azure VMs. Since VMs are frequently created and deleted, Microsoft recommends that users install applications and workspaces to the Chamber or Shared Storage volume to improve reliability. Chamber and Shared Storages are high-performance and high-reliability volumes based on Azure NetApp Files.
+Depending on the [Virtual Machine (VM) selected](./concept-vm-offerings.md), local temporary storage might not be available. Modeling and Simulation Workbench doesn't have controls for specifying data and OS disks as in conventional Azure VMs. Since VMs are frequently created and deleted, Microsoft recommends that users install applications and workspaces to the chamber or Shared Storage volume to improve reliability. Chamber and Shared Storages are high-performance and high-reliability volumes based on Azure NetApp Files.
 
 ## Chamber-tier storage
 
-Chamber-accessible storage is accessible across the entire Chamber, its VMs, and users. Chamber-tier storage has three classes: user home directories, data pipeline mount points, and Chamber Storage.
+Chamber-accessible storage is accessible across the entire chamber, its VMs, and users. Chamber-tier storage has three classes: user home directories, data pipeline mount points, and chamber Storage.
 
 ### User home directories
 
-The conventional Linux `/home` directory is mounted at `/mount/sharedhome`. The `/mount/sharedhome` is a single volume accessible across all Chamber VMs and isn't accessible outside the Chamber. This volume isn't high-performance and users are discouraged from attempting to install large files or operate intense workloads there. This directory is intended for user resource (rc), configuration, and small private directories.
+The conventional Linux `/home` directory is mounted at `/mount/sharedhome`. The `/mount/sharedhome` is a single volume accessible across all chamber VMs and isn't accessible outside the chamber. This volume isn't high-performance and users are discouraged from attempting to install large files or operate intense workloads there. This directory is intended for user resource (rc), configuration, and small private directories.
 
 ### Data pipeline mount points
 
 The data pipeline file structure has two directories: `/mount/datapipeline/datain` where imported data is staged and `/mount/datapipeline/dataout` where file exports are staged for file requests. This volume is large to accommodate large file imports and exports but files shouldn't be stored here long term. This mount is only for data import and export operations and isn't high-performance.
 
 ### Chamber Storage
 
-Chamber Storage is the high-performance, high-capacity storage solution for use within Chambers. Based on Azure NetApp Files, it's available in two high-performance tiers, and dynamically scalable after creation. Chamber Storage can be accessed at `/mount/chamberstorages` where a different directory exists for each created volume. Volumes are sizable in 4 TB increments up to the user's subscription quota.
+Chamber Storage is the high-performance, high-capacity storage solution for use within chambers. Based on Azure NetApp Files, it's available in two high-performance tiers, and dynamically scalable after creation. chamber Storage can be accessed at `/mount/chamberstorages` where a different directory exists for each created volume. Volumes are sizable in 4 TB increments up to the user's subscription quota.
 
 > [!TIP]
-> Users are encouraged to place all working directories and point all application runs at a Chamber Storage volume for increased performance and data reliablity.
+> Users are encouraged to place all working directories and point all application runs at a chamber Storage volume for increased performance and data reliablity.
 
 ## Workbench tier Shared Storage
 
-Shared Storage is accessible across select Chambers in a Workbench. With each Shared Storage volume, you specify which Chambers  have access to the volume. Shared Storage volumes appear under the `/mount/sharedstorage` mount point in every VM in the Chamber to which access was granted.
+Shared Storage is accessible across select chambers in a Workbench. With each Shared Storage volume, you specify which chambers  have access to the volume. Shared Storage volumes appear under the `/mount/sharedstorage` mount point in every VM in the chamber to which access was granted.
 
-To enable secure cross team and/or cross-enterprise collaboration, a Shared Storage resource allows for selective data sharing between Chambers. Shared Storage is built on Azure NetApp Files storage volumes and is available to deploy in multiples of 4 TB. Workbench owners can create multiple shared storage instances on demand and dynamically link them to existing Chambers to facilitate collaboration.
+To enable secure cross team and/or cross-enterprise collaboration, a Shared Storage resource allows for selective data sharing between chambers. Shared Storage is built on Azure NetApp Files storage volumes and is available to deploy in multiples of 4 TB. Workbench owners can create multiple shared storage instances on demand and dynamically link them to existing chambers to facilitate collaboration.
 
 Users who are provisioned to a specific chamber can access all shared storage volumes linked to that chamber. Once users get deprovisioned from a chamber or that chamber gets deleted, they lose access to any linked shared storage volumes.
 
@@ -53,10 +53,10 @@ Users who are provisioned to a specific chamber can access all shared storage vo
 **Management**: Workbench Owners can manage storage capacity, resize storage, and change performance tiers through the Azure portal.
 
 > [!IMPORTANT]
-> All members of a Chamber have access to a Shared Storage resource once that Chamber has been granted access to the storage volume. Do not place any data in Shared Storage that you do not wish to share with all members of that Chamber. Create a separate Chamber for select users if access needs to be restricted.
+> All members of a chamber have access to a Shared Storage resource once that chamber has been granted access to the storage volume. Do not place any data in Shared Storage that you do not wish to share with all members of that chamber. Create a separate chamber for select users if access needs to be restricted.
 
 ## Resources
 
-* [Create Chamber Storage](./how-to-guide-manage-chamber-storage.md)
+* [Create chamber Storage](./how-to-guide-manage-chamber-storage.md)
 * [Create Shared Storage](./how-to-guide-manage-shared-storage.md)
 * [Chamber VM offerings and local storage](./concept-vm-offerings.md)

articles/modeling-simulation-workbench/concept-user-personas.md

@@ -20,7 +20,7 @@ The IT Admin is responsible for infrastructure deployment and user provisioning,
 
 A Workbench Owner can create and delete chambers, and invite, remove, or change user roles. They can also define the connectivity methods that their users employ to connect into the workload. The Workbench Owner is also responsible for approving all data export requests and costs accrued by resource consumption during workbench usage.
 
-## Project Manager (Chamber Admin)
+## Project Manager (chamber Admin)
 
 The Project Manager, also known as the *Chamber Admin*, is responsible for installing and managing applications and licenses. They also own the installation and configuration of tools related to compute, network, and storage within the chamber. Chamber Admins set up and manage the chamber and have a higher elevated access within the workloads and the environment. They're responsible for procuring the licenses from the software vendors to enable design teams to run simulations on the deployed workloads.
 

articles/modeling-simulation-workbench/concept-vm-offerings.md

@@ -21,7 +21,7 @@ VM quotas in Modeling and Simulation Workbench are handled differently than in t
 
 ## General purpose
 
-General purpose VM sizes provide balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers. They make ideal management VMs for managing Chambers, Facilitating file imports or exports, compiling applications, or installing applications to shared storage.
+General purpose VM sizes provide balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers. They make ideal management VMs for managing chambers, Facilitating file imports or exports, compiling applications, or installing applications to shared storage.
 
 ### Dv4-series
 
@@ -101,4 +101,4 @@ M-series VMs have fixed-size temporary storage.
 ## Next step
 
 > [!div class="nextstepaction"]
-> [Create a Chamber VM](./how-to-guide-chamber-vm.md)
+> [Create a chamber VM](./how-to-guide-chamber-vm.md)