Merge pull request #288080 from kgremban/oct8-aioedits

Typos and naming fixes

Author: prmerger-automator[bot]

articles/iot-operations/connect-to-cloud/howto-configure-dataflow-endpoint.md

@@ -26,7 +26,7 @@ To get started, use the following table to choose the endpoint type to configure
 | [Kafka](howto-configure-kafka-endpoint.md) | For bi-directional messaging with Kafka brokers, including Azure Event Hubs. | Yes | Yes |
 | [Data Lake](howto-configure-adlsv2-endpoint.md) | For uploading data to Azure Data Lake Gen2 storage accounts. | No | Yes |
 | [Microsoft Fabric OneLake](howto-configure-fabric-endpoint.md) | For uploading data to Microsoft Fabric OneLake lakehouses. | No | Yes |
-| [Local storage](howto-configure-local-storage-endpoint.md) | For sending data to a locally available persistent volume, through which you can upload data via Edge Storage Accelerator edge volumes. | No | Yes |
+| [Local storage](howto-configure-local-storage-endpoint.md) | For sending data to a locally available persistent volume, through which you can upload data via Azure Container Storage enabled by Azure Arc edge volumes. | No | Yes |
 
 ## Reuse endpoints
 

articles/iot-operations/connect-to-cloud/howto-configure-local-storage-endpoint.md

@@ -25,7 +25,7 @@ To send data to local storage in Azure IoT Operations Preview, you can configure
 
 ## Create a local storage dataflow endpoint
 
-Use the local storage option to send data to a locally available persistent volume, through which you can upload data via Edge Storage Accelerator edge volumes.
+Use the local storage option to send data to a locally available persistent volume, through which you can upload data via Azure Container Storage enabled by Azure Arc edge volumes.
 
 # [Kubernetes](#tab/kubernetes)
 

articles/iot-operations/deploy-iot-ops/overview-deploy.md

@@ -55,9 +55,9 @@ The following table described Azure IoT Operations deployment and management tas
 | ---- | ------------------- | -------- |
 | Deploy Azure IoT Operations | **Contributor** role at the subscription level. |  |
 | Register resource providers | **Contributor** role at the subscription level. | Only required to do once per subscription. |
-| Create a schema registry. | **Microsoft/Authorization/roleAssignments/write** permissions at the resource group level. |  |
+| Create a schema registry. | **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level. |  |
 | Create secrets in Key Vault | **Key Vault Secrets Officer** role at the resource level. | Only required for secure settings deployment. |
-| Enable resource sync rules on an Azure IoT Operations instance | **Microsoft/Authorization/roleAssignments/write** permissions at the resource group level. | Resource sync rules are disabled by default, but can be enabled during instance creation. |
+| Enable resource sync rules on an Azure IoT Operations instance | **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level. | Resource sync rules are disabled by default, but can be enabled during instance creation. |
 
 If you use the Azure CLI to assign roles, use the [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) command to give permissions. For example, `az role assignment create --assignee sp_name --role "Role Based Access Control Administrator" --scope subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MyResourceGroup`
 

articles/iot-operations/get-started-end-to-end-sample/quickstart-deploy.md

@@ -40,7 +40,7 @@ Before you begin, prepare the following prerequisites:
 
 * Visual Studio Code installed on your development machine. For more information, see [Download Visual Studio Code](https://code.visualstudio.com/download).
 
-* **Microsoft/Authorization/roleAssignments/write** permissions at the resource group level.
+* **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level.
 
 ## What problem will we solve?
 
@@ -131,7 +131,7 @@ This helper command checks connectivity to Azure Resource Manager and Microsoft
 
 Azure IoT Operations requires a schema registry on your cluster. Schema registry requires an Azure storage account so that it can synchronize schema information between cloud and edge.
 
-The command to create a schema registry in this section requires **Microsoft/Authorization/roleAssignments/write** permissions at the resource group level.
+The command to create a schema registry in this section requires **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level.
 
 Run the following CLI commands in your Codespaces terminal.