Changes from #285392 comments by @denrea

Author: yousefi-msft

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

@@ -8,7 +8,7 @@ ms.service: modeling-simulation-workbench
 ms.topic: conceptual
 ms.date: 01/01/2023
 
-#Customer intent: As a Modeling and Simulation Workbench user, I want to understand the Connector component.
+#Customer intent: As a Modeling and Simulation Workbench user, I want to understand the component.
 ---
 # Connectors in Azure Modeling and Simulation Workbench
 

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

@@ -26,7 +26,7 @@ Users with access to the chamber can export data from the chamber via the data p
 
 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 the 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-license-service.md

@@ -24,7 +24,7 @@ For each deployed chamber within the workbench, we set up a license server and e
 
 ## Additional information
 
-For silicon Electronic Design Automation (EDA), our service automation deploys license servers for each of the four common software vendors (Synopsys, Cadence, Siemens, and Ansys) as part of resource creation to enable multi-vendor flows. The workbench also supports license service beyond these common EDA tool vendors with some manual configuration.
+For semiconductor Electronic Design Automation (EDA), our service automation deploys license servers for each of the four common software vendors (Synopsys, Cadence, Siemens, and Ansys) as part of resource creation to enable multi-vendor flows. The workbench also supports license service beyond these common EDA tool vendors with some manual configuration.
 
 This flow is extendible and can also include other software vendors across industry verticals."
 

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

@@ -15,11 +15,11 @@ 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
 
@@ -34,29 +34,29 @@ The data pipeline file structure has two directories: `/mount/datapipeline/datai
 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
+## 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.
 
 ## Key features of shared storage
 
-**Performance**: Shared Storage is based on Azure NetApp Files and is ideal for complex engineering or scientific workloads such as simulations.
+**Performance**: Shared storage is based on Azure NetApp Files and is ideal for complex engineering or scientific workloads such as simulations.
 
 **Scalability**: Users can adjust the storage capacity and performance tier according to their needs, just like chamber private storage.
 
 **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 Shared Storage](./how-to-guide-manage-shared-storage.md)
-* [Chamber VM offerings and local storage](./concept-vm-offerings.md)
+* [Create chamber storage](./how-to-guide-manage-chamber-storage.md)
+* [Create shared storage](./how-to-guide-manage-shared-storage.md)
+* [About chamber VM offerings and local storage](./concept-vm-offerings.md)

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

@@ -85,7 +85,7 @@ Esv5-series virtual machines run on Intel® Xeon® Platinum 8473C (Sapphire Rapi
 
 ### M family
 
-The 'M' family of VM size series are one of Azure's ultra memory-optimized VM instances. They're designed for memory-intensive workloads, such as large in-memory databases, data warehousing, and high-performance computing (HPC). Equipped with substantial RAM capacities and high vCPU capabilities, M-family VMs support applications and services that require massive amounts of memory and significant computational power. This makes them well-suited for handling tasks like real-time data processing, complex scientific simulations, and large-scale enterprise resource planning (ERP) systems, ensuring peak performance for the most demanding data-centric applications.
+The 'M' family of VM size series are one of Azure's ultra memory-optimized VM instances. They're designed for memory-intensive workloads, such as large in-memory databases, data warehousing, and high-performance computing (HPC). The M-family is equipped with substantial RAM capacities and high vCPU capabilities, M-family VMs support applications and services that require massive amounts of memory and significant computational power. This makes them well-suited for handling tasks like real-time data processing, complex scientific simulations, and large-scale enterprise resource planning (ERP) systems, ensuring peak performance for the most demanding data-centric applications.
 
 M-series VMs have fixed-size temporary storage.
 

articles/modeling-simulation-workbench/disaster-recovery.md

@@ -1,6 +1,6 @@
 ---
 title: Disaster recovery for Modeling and Simulation Workbench
-description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench workbench .component.
+description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench.
 author: meaghanlewis
 ms.author: mosagie
 ms.service: modeling-simulation-workbench
@@ -10,11 +10,11 @@ ms.date: 08/21/2024
 
 # Disaster recovery for Modeling and Simulation Workbench
 
-This article explains how to configure a disaster recovery environment for Azure Modeling and Simulation Workbench. Azure data center outages are rare but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to the environments hosted in that data center. By following the steps in this article, Azure Modeling and Simulation workbench customers will continue to operate in the cloud in the event of a data center outage for the primary region hosting your workbench instance.
+This article explains how to configure a disaster recovery environment for Azure Modeling and Simulation Workbench. Azure data center outages are rare but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to the environments hosted in that data center. This article gives Azure Modeling and Simulation workbench customers a resource to continue operations in the cloud in the event of a data center outage in the primary region hosting your workbench instance.
 
 Planning for disaster recovery involves identifying expected recovery point objectives (RPO) and recovery time objectives (RTO) for your instance. Based upon your risk-tolerance and expected RPO, follow these instructions at an interval appropriate for your business needs.
 
-A typical disaster recovery workflow starts with a failure of a critical service in your primary region. As the issue gets investigated, Azure publishes an expected time for the primary region to recover. If this timeframe is not acceptable for business continuity, and the problem does not impact your secondary region, you would start the process to fail over to the secondary region.
+A typical disaster recovery workflow starts with a failure of a critical service in your primary region. As the issue gets investigated, Azure publishes an expected time for the primary region to recover. If this timeframe isn't acceptable for business continuity, and the problem doesn't impact your secondary region, you would start the process to fail over to the secondary region.
 
 ## Achieving business continuity for Azure Modeling and Simulation Workbench
 
@@ -28,9 +28,9 @@ Alternatively, if you don't want to have an Azure Modeling and Simulation Workbe
 
 - Ensure that the services and features that your account uses are supported in the target secondary region.
 
-## Verify Entra ID tenant
+## Verify Microsoft Entra ID tenant information
 
-The workspace source and destination can be in the same subscription. If source and destination for workbench are different subscriptions, the subscriptions must exist within the same Entra ID tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
+The workspace source and destination can be in the same subscription. If source and destination for workbench are different subscriptions, the subscriptions must exist within the same Microsoft Entra ID tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
 
 ```powershell
 Get-AzSubscription -SubscriptionId <your-source-subscription>.TenantId
@@ -48,18 +48,18 @@ List of supported regions can be found on the [Azure product availability roadma
 
 Then, create a backup of your Azure Key Vault and keys used by Azure Modeling and Simulation in Key Vault including:
 
-1. Application Client Id key
+1. Application Client key
 2. Application Secret key
 
 ## Configure the new instance
 
-In the event of your primary region failure, and decision to work in a backup region, you would create a Modeling and Simulation Workbench instance in your backup region.
+In the event of a primary region failure, and decision to work in a backup region, you would create a Modeling and Simulation Workbench instance in your backup region.
 
 1. Register to the Azure Modeling and Simulation Workbench Resource Provider as described in [Create an Azure Modeling and Simulation Workbench](/azure/modeling-simulation-workbench/quickstart-create-portal#register-azure-modeling-and-simulation-workbench-resource-provider).
 
 1. Create an Azure Modeling and Simulation Workbench using this section of the Quickstart.
 
-1. If desired, upload data into the new backup instance following Upload Files section of instructions.
+1. Upload data into the new backup instance following Upload Files section of instructions, if necessary.
 
 You can now do your work in the new workbench instance created in the backup region.
 

articles/modeling-simulation-workbench/how-to-guide-add-redirect-uris.md

@@ -11,12 +11,12 @@ ms.date: 08/20/2024
 ---
 # Add redirect URIs for Modeling and Simulation Workbench
 
-A redirect Uniform Resource Identifier (URI) is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. Each Connector has two redirect URIs that must be registered in Microsoft Entra ID. A single Application Registration handles all the redirects and security tokens for a workbench.
+A redirect Uniform Resource Identifier (URI) is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. Each has two redirect URIs that must be registered in Microsoft Entra ID. A single Application Registration handles all the redirects and security tokens for a workbench.
 
 ## Prerequisites
 
 * An application registration in Microsoft Entra ID for the Azure Modeling and Simulation Workbench
-* A Workbench instance with a chamber and Connector created.
+* A Workbench instance with a chamber and created.
 
 ## Add redirect URIs for the application in Microsoft Entra ID
 

articles/modeling-simulation-workbench/how-to-guide-chamber-vm.md

@@ -10,13 +10,13 @@ ms.date: 08/16/2024
 ---
 # Chamber VMs
 
-Chamber Workload Virtual Machines (VM) are Azure VMs that are managed by the Workbench. Chamber VMs don't require expert users to select, deploy, configure, or manage. VMs are deployed quickly, preconfigured with drivers for the most common EDA (Electronic Design Automation) workloads, and with access to thousands of managed applications.
+Chamber Workload Virtual Machines (VM) are Azure VMs managed by the Workbench. Chamber VMs don't require expert users to select, deploy, configure, or manage. VMs are deployed quickly, preconfigured with drivers for the most common EDA (Electronic Design Automation) workloads, and with access to thousands of managed applications.
 
 Chamber VMs deploy quickly and with little configuration in as little as 10 minutes.  Chamber VMs are automatically:
 
 * Deployed directly into the chamber with no more configuration
 * Networked to the chamber's private virtual network
-* Mounted to any existing chamber Storage, user home directories, and the [Data Pipeline](./concept-data-pipeline.md) mount points
+* Mounted to any existing chamber storage, user home directories, and the [Data Pipeline](./concept-data-pipeline.md) mount points
 * Preconfigured with drivers to work with major semiconductor design tools
 
 User administration is managed from the parent chamber and all users of a chamber have access into all VMs in the chamber.
@@ -51,11 +51,11 @@ All VMs are created with Red Hat Enterprise Linux version 8.8.
  Read about the [Chamber VM offerings] (./concept-vm-offerings.md) to help you select the correct VM for your workload.
 
 1. Select **Review + create**.
-1. If prevalidation checks are successful, the **Create** button will be enabled. Selecte **Create**. A chamber VM typically can take up to 10 minutes to deploy. Once deployed, the **Power state** status shows as "Running".
+1. If prevalidation checks are successful, the **Create** button is enabled. Selecte **Create**. A chamber VM typically can take up to 10 minutes to deploy. Once deployed, the **Power state** status shows as "Running".
 
 ## Manage a chamber VM
 
-Once a chamber VM is created, a Workbench Owner or chamber Admin can administer it. Chamber VMs can only be stopped, started, or restarted. Chamber VMs can't be migrated or resized. Chamber VMs don't accept user role assignments. User administration happens at the chamber level. Chambers have access to Shared Storage (shared between chambers) and chamber Storage, which is accessible only within the chamber by the members. IP addresses are managed by the deployment engine. Data and OS disks aren't configurable in chamber VMs. Microsoft recommends installing all your applications and data on the chamber Storage volumes to allow you to create and destroy VMs that are instantly ready for use. All VMs have access to the chamber License servers.
+Once a chamber VM is created, a Workbench Owner or chamber Admin can administer it. Chamber VMs can only be stopped, started, or restarted. Chamber VMs can't be migrated or resized. Chamber VMs don't accept user role assignments. User administration happens at the chamber level. Chambers have access to shared storage (shared between chambers) and chamber storage, which is accessible only within the chamber by the members. IP addresses are managed by the deployment engine. Data and OS disks aren't configurable in chamber VMs. Microsoft recommends installing all your applications and data on the chamber storage volumes to allow you to create and destroy VMs that are instantly ready for use. All VMs have access to the chamber License servers.
 
 * [Manage users](./how-to-guide-manage-users.md)
 * [How to start, stop, or restart a chamber](./how-to-guide-start-stop-restart.md)
@@ -73,5 +73,5 @@ If a chamber VM is no longer needed, it can be deleted. VMs don't need to be sto
 
 * [Manage users](./how-to-guide-manage-users.md)
 * [Start, stop, or restart a chamber](./how-to-guide-start-stop-restart.md)
-* [Manage chamber Storage](./how-to-guide-manage-chamber-storage.md)
+* [Manage chamber storage](./how-to-guide-manage-chamber-storage.md)
 * [License servers](./concept-license-service.md)