Merge pull request #125159 from ArieHein/Spelling-Wave-39

ttorble · web-flow · commit 846b99f661a1 · 2024-12-17T16:43:37.000Z
Spelling Fixes
diff --git a/articles/service-bus-messaging/deprecate-service-bus-management.md b/articles/service-bus-messaging/deprecate-service-bus-management.md
@@ -22,7 +22,7 @@ For more information on Service Manager and Resource Manager APIs for Azure Serv
 | Service Manager APIs (Deprecated) | Resource Manager - Service Bus API | Resource Manager - Event Hubs API | Resource Manager - Relay API |
 | --------------- | ----------------- | ----------------- | ----------------- | 
 | **Namespaces-GetNamespaceAsync** <br/>[Service Bus Get Namespace](/rest/api/servicebus/get-namespace)<br/>[Event Hubs Get Namespace](/rest/api/eventhub/get-event-hub)<br/>[Relay Get Namespace](/rest/api/servicebus/get-relays)<br/> ```GET https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}``` | [get](/rest/api/servicebus/controlplane-stable/namespaces/get) | [get](/rest/api/eventhub/controlplane-stable/namespaces/get) | [get](/rest/api/relay/controlplane-preview/namespaces/get) |
-| **ConnectionDetails-GetConnectionDetails**<br/>Service Bus/Event Hub/Relay GetConnectionDetals<br/>```GET https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/ConnectionDetails``` | [listkeys](/rest/api/servicebus/controlplane-stable/namespaces-authorization-rules/list-keys) | [listkeys](/rest/api/eventhub/controlplane-stable/authorization-rules-event-hubs/list-keys) | [listkeys](/rest/api/relay/controlplane-stable/wcf-relays/list-keys) |
+| **ConnectionDetails-GetConnectionDetails**<br/>Service Bus/Event Hub/Relay GetConnectionDetails<br/>```GET https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/ConnectionDetails``` | [listkeys](/rest/api/servicebus/controlplane-stable/namespaces-authorization-rules/list-keys) | [listkeys](/rest/api/eventhub/controlplane-stable/authorization-rules-event-hubs/list-keys) | [listkeys](/rest/api/relay/controlplane-stable/wcf-relays/list-keys) |
 | **Topics-GetTopicsAsync**<br/>Service Bus<br/>```GET https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/topics? $skip={skip}&$top={top}``` | [list](/rest/api/servicebus/controlplane-preview/topics/list-by-namespace) | &nbsp; | &nbsp; | 
 | **Queues-GetQueueAsync** <br/>Service Bus<br/>```GET https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/queues/{queueName}``` | [get](/rest/api/servicebus/controlplane-stable/queues/get) | &nbsp; | &nbsp; | 
 | **Relays-GetRelaysAsync**<br/>[Get Relays](/rest/api/servicebus/get-relays)<br/>```GET https://management.core.windows.net/{subscription ID}/services/ServiceBus/Namespaces/{namespace name}/relays? $skip={skip}&$top={top}```| &nbsp; | &nbsp; | [list](/rest/api/relay/controlplane-stable/wcf-relays/list-by-namespace) | 
diff --git a/articles/service-bus-messaging/disable-local-authentication.md b/articles/service-bus-messaging/disable-local-authentication.md
@@ -3,7 +3,7 @@ title: Disable local authentication with Azure Service Bus
 description: This article explains how to disable local or Shared Access Signature key authentication for a Service Bus namespace. 
 ms.topic: how-to
 ms.date: 07/25/2024 
-#customer intent: As a developer or IT adminstrator, I want to know how to disable shared access key authentication and use only the Microsoft Entra ID authentication for higher security.
+#customer intent: As a developer or IT administrator, I want to know how to disable shared access key authentication and use only the Microsoft Entra ID authentication for higher security.
 ---
 
 # Disable local or shared access key authentication with Azure Service Bus
diff --git a/articles/service-bus-messaging/message-expiration.md b/articles/service-bus-messaging/message-expiration.md
@@ -65,7 +65,7 @@ Here's what considered idleness of entities (queues, topics, and subscriptions):
 | Subscription | <ul><li>No receives</li><li>No updates to the subscription</li><li>No new rules added to the subscription</li><li>No browse/peek</li></ul> |
 
  > [!IMPORTANT] 
-> If you have auto forwarding setup on the queue or subscription, that is equivalent to having a receiver peform receives on the queue or subscription and they will not be idle.
+> If you have auto forwarding setup on the queue or subscription, that is equivalent to having a receiver perform receives on the queue or subscription and they will not be idle.
  
 ## SDKs
 You can set the time-to-live property using Software Development Kits (SDKs). 
diff --git a/articles/service-bus-messaging/service-bus-dotnet-multi-tier-app-using-service-bus-queues.md b/articles/service-bus-messaging/service-bus-dotnet-multi-tier-app-using-service-bus-queues.md
@@ -135,7 +135,7 @@ queue and displays status information about the queue.
 
    Note that the required client assemblies are now referenced and some new code files have been added.
 10. Follow the same steps to add the `Azure.Identity` NuGet package to the project.  
-10. In **Solution Explorer**, expand **FronendWebRole**, right-click **Models** and select **Add**,
+10. In **Solution Explorer**, expand **FrontendWebRole**, right-click **Models** and select **Add**,
     then select **Class**. In the **Name** box, type the name
     **OnlineOrder.cs**. Then select **Add**.
 
diff --git a/articles/service-bus-messaging/service-bus-geo-replication.md b/articles/service-bus-messaging/service-bus-geo-replication.md
@@ -217,14 +217,14 @@ You can automate promotion either with monitoring systems, or with custom-built
 
 In the portal, click on the **Promote** icon, and follow the instructions in the pop-up blade to delete the region. 
 
-:::image type="content" source="./media/service-bus-geo-replication/promote-secondary-region.png" alt-text="Screeshot showing the flow to promote secondary region." lightbox="./media/service-bus-geo-replication/promote-secondary-region.png":::
+:::image type="content" source="./media/service-bus-geo-replication/promote-secondary-region.png" alt-text="Screenshot showing the flow to promote secondary region." lightbox="./media/service-bus-geo-replication/promote-secondary-region.png":::
 
 ### Using Azure CLI
 
 Execute the Azure CLI command to initiate the promotion. The **Force** property is optional, and defaults to **false**.
 
 ```azurecli
-az rest --method post --url https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.ServiceBus/namespaces/<namespaceName>/failover?api-version=2023-01-01-preview --body "{'properties': {'PrimaryLocation': '<newPrimaryocation>', 'api-version':'2023-01-01-preview', 'Force':'false'}}"
+az rest --method post --url https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.ServiceBus/namespaces/<namespaceName>/failover?api-version=2023-01-01-preview --body "{'properties': {'PrimaryLocation': '<newPrimaryLocation>', 'api-version':'2023-01-01-preview', 'Force':'false'}}"
 ```
 
 ### Monitoring data replication
diff --git a/articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md b/articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md
@@ -211,7 +211,7 @@ We recommend that you follow these verification steps, depending on the type of
 - The replication queue for an entity exceeds its maximum size in bytes. The maximum size in bytes for a replication queue is an internal limit set by Service Bus. 
     - **Example**: Replication queue size 73128000 exceeded threshold 67108864.  
 - In synchronous replication, a request times out while waiting for another request to replicate. 
-    - **Example**: High volume of requests from client application for skarri-stroage-exp1(westus3)/q1:MessagingJournal. Replication to other region(s) is in progress.  
+    - **Example**: High volume of requests from client application for skarri-storage-exp1(westus3)/q1:MessagingJournal. Replication to other region(s) is in progress.  
 
 #### Resolution 
 
diff --git a/articles/service-bus-messaging/service-bus-messaging-sql-rule-action.md b/articles/service-bus-messaging/service-bus-messaging-sql-rule-action.md
@@ -214,7 +214,7 @@ Here are a few important points:
 
 - Only properties on a message can be modified. 
 - All user properties can be modified. 
-- All publicly updatable system properties can also be modified, like `ReplyTo` and `CorreationId`, but we recommend that you don't alter system properties as part of a rule action. It's still allowed for backward compatibility reasons.
+- All publicly updatable system properties can also be modified, like `ReplyTo` and `CorrelationId`, but we recommend that you don't alter system properties as part of a rule action. It's still allowed for backward compatibility reasons.
 - When setting properties, only numeric, Boolean, and string literals are allowed. A string literal in turn is converted to a type based on the property being modified. If the property being set doesn't already exist, there's no type conversion from string. If the property being modified already exists and its value is one of these types `Guid`, `DateTimeOffset`, `TimeSpan`, `Uri`, `DateTime`, then the string literal is converted to that type and set as the property value. To be more specific, the action tries to convert the string literal to the type of property. If it's successful, the property is set. Otherwise, the rule action evaluation throws an exception and the message is dead-lettered.
 
 ## Next steps
diff --git a/articles/service-connector/how-to-build-connections-with-iac-tools.md b/articles/service-connector/how-to-build-connections-with-iac-tools.md
@@ -51,7 +51,7 @@ Authoring the template from scratch is the preferred and recommended way to prov
 
 ```bicep
 // This template creates a webapp and a storage account.
-// In order to make it more readable, we use only the mininal set of parameters to create the resources.
+// In order to make it more readable, we use only the minimal set of parameters to create the resources.
 
 param location string = resourceGroup().location
 // App Service plan parameters
@@ -175,7 +175,7 @@ resource webApp 'Microsoft.Web/sites@2022-09-01' existing = {
   name: webAppName
 }
 
-// Get an existig storage
+// Get an existing storage
 resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' existing = {
   name: storageAccountName
 }
diff --git a/articles/service-connector/how-to-use-service-connector-in-aks.md b/articles/service-connector/how-to-use-service-connector-in-aks.md
@@ -63,7 +63,7 @@ Different kubernetes resources are created when the target service type and auth
 
 #### Kubernetes secret
 
-A kubernetes secret is created when the authentication type is `Connection String` or `Service Principal`. Your cluster workload definition can reference the secret directly. The following snnipet is an example.
+A kubernetes secret is created when the authentication type is `Connection String` or `Service Principal`. Your cluster workload definition can reference the secret directly. The following snippet is an example.
 
 ```yaml
 apiVersion: batch/v1
@@ -89,7 +89,7 @@ Then, your application codes can consume the connection string in the secret fro
 
 #### Kubernetes service account
 
-Both a kubernetes service account and a secret are created when the authentication type is `Workload Identity`. Your cluster workload definition can reference the service account and secret to authenticate through workload identity. The following snipet provides an example.
+Both a kubernetes service account and a secret are created when the authentication type is `Workload Identity`. Your cluster workload definition can reference the service account and secret to authenticate through workload identity. The following snippet provides an example.
 
 ```yaml
 apiVersion: batch/v1
diff --git a/articles/service-connector/includes/code-cosmoscassandra-me-id.md b/articles/service-connector/includes/code-cosmoscassandra-me-id.md
@@ -132,7 +132,7 @@ ms.author: wchi
     import javax.net.ssl.*;
     import java.net.InetSocketAddress;
     import com.azure.identity.*;
-    import com.azure.core.credentital.*;
+    import com.azure.core.credential.*;
     import java.net.http.*;
     import java.net.URI;
 
@@ -233,7 +233,7 @@ Authentication type is not supported for Spring Boot.
     ssl_context = SSLContext(PROTOCOL_TLSv1_2)
     ssl_context.verify_mode = CERT_NONE
     auth_provider = PlainTextAuthProvider(username, password)
-    cluster = Cluster([contanctPoint], port = port, auth_provider=auth_provider,ssl_context=ssl_context)
+    cluster = Cluster([contactPoint], port = port, auth_provider=auth_provider,ssl_context=ssl_context)
     session = cluster.connect()
     ```
 
@@ -260,12 +260,12 @@ Authentication type is not supported for Spring Boot.
     )
     
     func GetSession() *gocql.Session {
-        cosmosCassandraContactPoint = os.Getenv("AAZURE_COSMOS_CONTACTPOINT")
+        cosmosCassandraContactPoint = os.Getenv("AZURE_COSMOS_CONTACTPOINT")
         cosmosCassandraPort = os.Getenv("AZURE_COSMOS_PORT")
         cosmosCassandraUser = os.Getenv("AZURE_COSMOS_USERNAME")
         cosmosCassandraKeyspace = os.Getenv("AZURE_COSMOS_KEYSPACE")
         listKeyUrl = os.Getenv("AZURE_COSMOS_LISTKEYURL")
-        scope = os.Getenv("AZUE_COSMOS_SCOPE")
+        scope = os.Getenv("AZURE_COSMOS_SCOPE")
 
         // Uncomment the following lines corresponding to the authentication type you want to use.
         // For system-assigned identity.
diff --git a/articles/service-connector/includes/code-cosmoscassandra-secret.md b/articles/service-connector/includes/code-cosmoscassandra-secret.md
@@ -134,7 +134,7 @@ Set up your Spring App application according to [How to use Spring Data with Azu
     ssl_context = SSLContext(PROTOCOL_TLSv1_2)
     ssl_context.verify_mode = CERT_NONE
     auth_provider = PlainTextAuthProvider(username, password)
-    cluster = Cluster([contanctPoint], port = port, auth_provider=auth_provider,ssl_context=ssl_context)
+    cluster = Cluster([contactPoint], port = port, auth_provider=auth_provider,ssl_context=ssl_context)
     session = cluster.connect()
     ```
 
diff --git a/articles/service-connector/includes/code-cosmosgremlin-me-id.md b/articles/service-connector/includes/code-cosmosgremlin-me-id.md
@@ -104,7 +104,7 @@ ms.author: wchi
     import javax.net.ssl.*;
     import java.net.InetSocketAddress;
     import com.azure.identity.*;
-    import com.azure.core.credentital.*;
+    import com.azure.core.credential.*;
     import java.net.http.*;
     import java.net.URI;
 
@@ -230,7 +230,7 @@ ms.author: wchi
         endpoint = os.getenv("AZURE_COSMOS_RESOURCEENDPOINT")
         port = os.getenv("AZURE_COSMOS_PORT")
         listKeyUrl = os.Getenv("AZURE_COSMOS_LISTKEYURL")
-        scope = os.Getenv("AZUE_COSMOS_SCOPE")
+        scope = os.Getenv("AZURE_COSMOS_SCOPE")
 
         // Uncomment the following lines corresponding to the authentication type you want to use.
         // For system-assigned identity.
@@ -283,7 +283,7 @@ ms.author: wchi
     const axios = require('axios');
     
     let username = process.env.AZURE_COSMOS_USERNAME;
-    let endoint = process.env.AZURE_COSMOS_RESOURCEENDPOINT;
+    let endpoint = process.env.AZURE_COSMOS_RESOURCEENDPOINT;
     let port = process.env.AZURE_COSMOS_PORT;
     let listKeyUrl = process.env.AZURE_COSMOS_LISTKEYURL;
     let scope = process.env.AZURE_COSMOS_SCOPE;
diff --git a/articles/service-connector/includes/code-cosmosmongo-me-id.md b/articles/service-connector/includes/code-cosmosmongo-me-id.md
@@ -93,7 +93,7 @@ ms.author: wchi
     import javax.net.ssl.*;
     import java.net.InetSocketAddress;
     import com.azure.identity.*;
-    import com.azure.core.credentital.*;
+    import com.azure.core.credential.*;
     import java.net.http.*;
     import java.net.URI;
 
@@ -213,7 +213,7 @@ The authentication type is not supported for Spring Boot.
     
     endpoint = os.Getenv("AZURE_COSMOS_RESOURCEENDPOINT")
     listConnectionStringUrl = os.Getenv("AZURE_COSMOS_LISTCONNECTIONSTRINGURL")
-    scope = os.Getenv("AZUE_COSMOS_SCOPE")
+    scope = os.Getenv("AZURE_COSMOS_SCOPE")
 
     // Uncomment the following lines corresponding to the authentication type you want to use.
     // For system-assigned identity.
diff --git a/articles/service-connector/includes/code-cosmostable-me-id.md b/articles/service-connector/includes/code-cosmostable-me-id.md
@@ -83,7 +83,7 @@ ms.author: wchi
     import javax.net.ssl.*;
     import java.net.InetSocketAddress;
     import com.azure.identity.*;
-    import com.azure.core.credentital.*;
+    import com.azure.core.credential.*;
     import java.net.http.*;
 
     String endpoint = System.getenv("AZURE_COSMOS_RESOURCEENDPOINT");
@@ -199,7 +199,7 @@ ms.author: wchi
     func main() {
         endpoint = os.Getenv("AZURE_COSMOS_RESOURCEENDPOINT")
         listConnectionStringUrl = os.Getenv("AZURE_COSMOS_LISTCONNECTIONSTRINGURL")
-        scope = os.Getenv("AZUE_COSMOS_SCOPE")
+        scope = os.Getenv("AZURE_COSMOS_SCOPE")
 
         // Uncomment the following lines corresponding to the authentication type you want to use.
         // For system-assigned identity.
diff --git a/articles/service-connector/quickstart-cli-functions-connection.md b/articles/service-connector/quickstart-cli-functions-connection.md
@@ -48,7 +48,7 @@ This quickstart shows you how to connect Azure Functions to other Cloud resource
 Use the Azure CLI [az functionapp connection](/cli/azure/functionapp/connection) command to create a service connection to a Blob Storage with a system-assigned managed identity, providing the following information:
 
 - **Source compute service resource group name:** the resource group name of the Function App.
-- **Function App name:** the name of your FunctioApp that connects to the target service.
+- **Function App name:** the name of your FunctionApp that connects to the target service.
 - **Target service resource group name:** the resource group name of the Blob Storage.
 - **Storage account name:** the account name of your Blob Storage.
 
diff --git a/articles/service-connector/tutorial-python-functions-storage-blob-as-input.md b/articles/service-connector/tutorial-python-functions-storage-blob-as-input.md
@@ -88,7 +88,7 @@ Follow the [tutorial](../azure-functions/create-first-function-vs-code-python.md
 
 1. Select the storage account you used when creating the Azure Function resource if you're prompted to connect to Storage. It is for Azure Function runtime's internal use, and isn't necessarily the same with the one you use for input.
 1. To start the function locally, press `<kbd>`F5 `</kbd>` or select the **Run and Debug** icon in the left-hand side Activity bar.
-1. To verify the function can read the blob, right click `Exucute Function Now...` on the function in the Visual Studio Code **WORKSPACE** and check the function response. The response message should contain the content in your blob file.
+1. To verify the function can read the blob, right click `Execute Function Now...` on the function in the Visual Studio Code **WORKSPACE** and check the function response. The response message should contain the content in your blob file.
 
 ## Create a connection using Service Connector
 
@@ -103,7 +103,7 @@ Now you'll learn how to configure the connection between the Azure Function and
 az functionapp connection create storage-blob --source-id "<your-function-resource-id>" --target-id "<your-storage-blob-resource-id>" --system-identity --customized-keys AZURE_STORAGEBLOB_RESOURCEENDPOINT=MyBlobInputConnection__serviceUri
 ```
 
-* `--source-id` format: `/subscriptions/{subscription}/resourceG roups/{source_resource_group}/providers/Microsoft.Web/sites/{site}`
+* `--source-id` format: `/subscriptions/{subscription}/resourceGroups/{source_resource_group}/providers/Microsoft.Web/sites/{site}`
 * `--target-id` format: `/subscriptions/{subscription}/resourceGroups/{target_resource_group}/providers/Microsoft.Storage/storageAccounts/{account}/blobServices/default`
 
 You have created a connection between Azure Function and Azure Blob Storage using Service Connector, with a system-assigned managed identity.
@@ -115,11 +115,11 @@ Service Connector configured a `MyBlobInputConnection__serviceUri` variable in t
 Now you can deploy your function to Azure and verify the storage blob input binding works.
 
 1. Follow the [tutorial](../azure-functions/create-first-function-vs-code-python.md?pivots=python-mode-configuration#deploy-the-project-to-azure) to deploy your function to Azure.
-1. To verify the function can read the blob, right click `Exucute Function Now...` on the function in the Visual Studio Code **RESOURCES** view and check the function response. The response message should contain the content in your blob file.
+1. To verify the function can read the blob, right click `Execute Function Now...` on the function in the Visual Studio Code **RESOURCES** view and check the function response. The response message should contain the content in your blob file.
 
 ## Troubleshoot
 
-If there are any errors related with storage host, such as `No such host is known (<acount-name>.blob.core.windows.net:443)`, you need to check whether the connection string you use to connect to Azure Storage contains the blob endpoint or not. If it doesn't, go to Azure Storage in the Azure portal, copy the connection string from the `Access keys` blade, and replace the values.
+If there are any errors related with storage host, such as `No such host is known (<account-name>.blob.core.windows.net:443)`, you need to check whether the connection string you use to connect to Azure Storage contains the blob endpoint or not. If it doesn't, go to Azure Storage in the Azure portal, copy the connection string from the `Access keys` blade, and replace the values.
 
 If the error happens when you start the project locally, check the `local.settings.json` file.
 
diff --git a/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md b/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md
diff --git a/articles/service-connector/tutorial-python-functions-storage-table-as-output.md b/articles/service-connector/tutorial-python-functions-storage-table-as-output.md

Original file line number	Diff line number	Diff line change
`@@ -51,7 +51,7 @@ Authoring the template from scratch is the preferred and recommended way to prov`
`51`	`51`
`52`	`52`	```bicep
`53`	`53`	`// This template creates a webapp and a storage account.`
`54`		`-// In order to make it more readable, we use only the mininal set of parameters to create the resources.`
	`54`	`+// In order to make it more readable, we use only the minimal set of parameters to create the resources.`
`55`	`55`
`56`	`56`	`param location string = resourceGroup().location`
`57`	`57`	`// App Service plan parameters`
`@@ -175,7 +175,7 @@ resource webApp 'Microsoft.Web/sites@2022-09-01' existing = {`
`175`	`175`	`name: webAppName`
`176`	`176`	`}`
`177`	`177`
`178`		`-// Get an existig storage`
	`178`	`+// Get an existing storage`
`179`	`179`	`resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' existing = {`
`180`	`180`	`name: storageAccountName`
`181`	`181`	`}`