Merge pull request #125092 from ArieHein/Spelling-Wave-21

ttorble · web-flow · commit 4a8c59f16550 · 2024-12-09T15:13:46.000Z
Spelling Fixes
diff --git a/articles/event-grid/authenticate-with-entra-id-namespaces.md b/articles/event-grid/authenticate-with-entra-id-namespaces.md
@@ -52,7 +52,7 @@ Besides managed identities, another identity option is to create a security prin
 Once you have an application security principal and followed above steps, [assign the permission to publish events to that identity](#assign-permission-to-a-security-principal-to-publish-events).
 
 > [!NOTE]
-> When you register an application in the portal, an [application object](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#application-object) and a [service principal](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#service-principal-object) are created automatically in your home tenant. Alternatively, you can use Microsot Graph to register your application. However, if you register or create an application using the Microsoft Graph APIs, creating the service principal object is a separate step. 
+> When you register an application in the portal, an [application object](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#application-object) and a [service principal](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#service-principal-object) are created automatically in your home tenant. Alternatively, you can use Microsoft Graph to register your application. However, if you register or create an application using the Microsoft Graph APIs, creating the service principal object is a separate step. 
 
 ## Assign permission to a security principal to publish events
 
diff --git a/articles/event-grid/authenticate-with-microsoft-entra-id.md b/articles/event-grid/authenticate-with-microsoft-entra-id.md
@@ -54,7 +54,7 @@ Besides managed identities, another identity option is to create a security prin
 Once you have an application security principal and followed above steps, [assign the permission to publish events to that identity](#assign-permission-to-a-security-principal-to-publish-events).
 
 > [!NOTE]
-> When you register an application in the portal, an [application object](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#application-object) and a [service principal](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#service-principal-object) are created automatically in your home tenant. Alternatively, you can use Microsot Graph to register your application. However, if you register or create an application using the Microsoft Graph APIs, creating the service principal object is a separate step. 
+> When you register an application in the portal, an [application object](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#application-object) and a [service principal](/entra/identity-platform/app-objects-and-service-principals?tabs=browser#service-principal-object) are created automatically in your home tenant. Alternatively, you can use Microsoft Graph to register your application. However, if you register or create an application using the Microsoft Graph APIs, creating the service principal object is a separate step. 
 
 
 ## Assign permission to a security principal to publish events
@@ -136,7 +136,7 @@ Microsoft Entra authentication provides a superior authentication support than t
 Once you decide to use Microsoft Entra authentication, you can disable authentication based on access keys or SAS tokens. 
 
 > [!NOTE]
-> Acess keys or SAS token authentication is a form of **local authentication**. you'll hear sometimes referring to "local auth" when discussing this category of authentication mechanisms that don't rely on Microsoft Entra ID. The API parameter used to disable local authentication is called, appropriately so, ``disableLocalAuth``.
+> Access keys or SAS token authentication is a form of **local authentication**. you'll hear sometimes referring to "local auth" when discussing this category of authentication mechanisms that don't rely on Microsoft Entra ID. The API parameter used to disable local authentication is called, appropriately so, ``disableLocalAuth``.
 
 ### Azure portal
 
diff --git a/articles/event-grid/communication-services-advanced-messaging-events.md b/articles/event-grid/communication-services-advanced-messaging-events.md
@@ -266,7 +266,7 @@ Details for the attributes specific to `Microsoft.Communication.AdvancedMessageA
 
 | Attribute      | Type     | Nullable | Description                                 |
 |:---------------|:--------:|:--------:|---------------------------------------------|
-| language    | `string` | ✔️      | The languege detected.    |
+| language    | `string` | ✔️      | The language detected.    |
 | confidenceScore | `float` | ✔️      | The confidence score of the language detected. |
 | translation | `string` | ✔️      | The message translation. |
 
diff --git a/articles/event-grid/configure-private-endpoints.md b/articles/event-grid/configure-private-endpoints.md
@@ -129,7 +129,7 @@ To create a private endpoint, use the [az network private-endpoint create](/cli/
 
 ```azurecli-interactive
 az network private-endpoint create \
-    --resource-group <RESOURECE GROUP NAME> \
+    --resource-group <RESOURCE GROUP NAME> \
     --name <PRIVATE ENDPOINT NAME> \
     --vnet-name <VIRTUAL NETWORK NAME> \
     --subnet <SUBNET NAME> \
@@ -147,7 +147,7 @@ For descriptions of the parameters used in the example, see documentation for [a
 To delete a private endpoint, use the [az network private-endpoint delete](/cli/azure/network/private-endpoint?#az-network-private-endpoint-delete) method as shown in the following example:
 
 ```azurecli-interactive
-az network private-endpoint delete --resource-group <RESOURECE GROUP NAME> --name <PRIVATE ENDPOINT NAME>
+az network private-endpoint delete --resource-group <RESOURCE GROUP NAME> --name <PRIVATE ENDPOINT NAME>
 ```
 
 > [!NOTE]
@@ -173,7 +173,7 @@ To create a private endpoint, use the [az network private-endpoint create](/cli/
 
 ```azurecli-interactive
 az network private-endpoint create \
-    --resource-group <RESOURECE GROUP NAME> \
+    --resource-group <RESOURCE GROUP NAME> \
     --name <PRIVATE ENDPOINT NAME> \
     --vnet-name <VIRTUAL NETWORK NAME> \
     --subnet <SUBNET NAME> \
@@ -191,7 +191,7 @@ For descriptions of the parameters used in the example, see documentation for [a
 To delete a private endpoint, use the [az network private-endpoint delete](/cli/azure/network/private-endpoint?#az-network-private-endpoint-delete) method as shown in the following example:
 
 ```azurecli-interactive
-az network private-endpoint delete --resource-group <RESOURECE GROUP NAME> --name <PRIVATE ENDPOINT NAME>
+az network private-endpoint delete --resource-group <RESOURCE GROUP NAME> --name <PRIVATE ENDPOINT NAME>
 ```
 
 > [!NOTE]
diff --git a/articles/event-grid/cross-tenant-delivery-using-managed-identity.md b/articles/event-grid/cross-tenant-delivery-using-managed-identity.md
@@ -57,7 +57,7 @@ For more information, see the following articles:
 
     - In the URL, use the multitenant app object ID. 
     - For **Name**, provide a unique name for the federated client credential.
-    - For **Issuer**, use `https://login.microsoftonline.com/TENANTAID/v2.0` where `TENANTAID` is the ID of the tenant where the user-assigned identity is located. 
+    - For **Issuer**, use `https://login.microsoftonline.com/TENANTID/v2.0` where `TENANTID` is the ID of the tenant where the user-assigned identity is located. 
     - For **Subject**, specify the client ID of the user-assigned identity. 
    
     Verify and wait for the API call to succeed.     
diff --git a/articles/event-grid/dead-letter-event-subscriptions-namespace-topics.md b/articles/event-grid/dead-letter-event-subscriptions-namespace-topics.md
@@ -35,7 +35,7 @@ The format used when storing dead-letter events is the [CloudEvents JSON format]
     - `deliveryresult` - The last result during the last time the service attempted to deliver the event.
     - `publishutc` - The UTC time at which the event was persisted and accepted (HTTP 200 OK, for example) by Event Grid.
     - `deliveryattemptutc` - The UTC time of the last delivery attempt.
-- `customDeliveryProperties` - Headers (custom push delivery properties) configured on the event subscription to go with every outgoing HTTP push delivery request. One or more of these custom properties might be present in the persisted dead-letter JSON. Custom properties identified as secrets aren't stored. This metadata are described using a separate object whose key name is `customDeliveryProperties`. The property key names inside that object and their values are exactly the same as the ones set in the event subscription. Here's an exmaple: 
+- `customDeliveryProperties` - Headers (custom push delivery properties) configured on the event subscription to go with every outgoing HTTP push delivery request. One or more of these custom properties might be present in the persisted dead-letter JSON. Custom properties identified as secrets aren't stored. This metadata are described using a separate object whose key name is `customDeliveryProperties`. The property key names inside that object and their values are exactly the same as the ones set in the event subscription. Here's an example: 
 
     ```
     Custom-Header-1: value1
diff --git a/articles/event-grid/enable-diagnostic-logs-topic.md b/articles/event-grid/enable-diagnostic-logs-topic.md
@@ -104,7 +104,7 @@ You can also enable collection of all **metrics** for the system topic.
     ```json
     {
         "time": "2019-11-01T00:17:13.4389048Z",
-        "resourceId": "/SUBSCRIPTIONS/SAMPLE-SUBSCTIPTION-ID /RESOURCEGROUPS/SAMPLE-RESOURCEGROUP-NAME/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/SAMPLE-TOPIC-NAME ",
+        "resourceId": "/SUBSCRIPTIONS/SAMPLE-SUBSCRIPTION-ID /RESOURCEGROUPS/SAMPLE-RESOURCEGROUP-NAME/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/SAMPLE-TOPIC-NAME ",
         "eventSubscriptionName": "SAMPLEDESTINATION",
         "category": "DeliveryFailures",
         "operationName": "Deliver",
diff --git a/articles/event-grid/event-schema-compatibility.md b/articles/event-grid/event-schema-compatibility.md
@@ -11,7 +11,7 @@ ms.custom: FY25Q1-Linter
 # Event schema compatibility
 When a topic is created, an incoming event schema is defined. And, when a subscription is created, an outgoing event schema is defined. This article shows you the compatibility between input and output schema that's allowed when creating an event subscription.
 
-## Input schema to outupt schema
+## Input schema to output schema
 The following table shows you the compatibility allowed when creating a subscription. 
 
 | Incoming event schema | Outgoing event schema | Supported |
diff --git a/articles/event-grid/event-schema-resources.md b/articles/event-grid/event-schema-resources.md
@@ -243,7 +243,7 @@ This section shows the `CreatedOrUpdated` event generated when an Azure Storage
   "data": {
     "resourceInfo": {
       "tags": {},
-      "id": "/subscriptions/{subcription-id}/resourceGroups/{rg-name}/providers/Microsoft.Storage/storageAccounts/{storageAccount-name}",
+      "id": "/subscriptions/{subscription-id}/resourceGroups/{rg-name}/providers/Microsoft.Storage/storageAccounts/{storageAccount-name}",
       "name": "StorageAccount-name",
       "type": "Microsoft.Storage/storageAccounts",
       "location": "eastus",
@@ -320,7 +320,7 @@ This section shows the `CreatedOrUpdated` event generated when an Azure Storage
   "data": {
     "resourceInfo": {
       "tags": {},
-      "id": "/subscriptions/{subcription-id}/resourceGroups/{rg-name}/providers/Microsoft.Storage/storageAccounts/{storageAccount-name}",
+      "id": "/subscriptions/{subscription-id}/resourceGroups/{rg-name}/providers/Microsoft.Storage/storageAccounts/{storageAccount-name}",
       "name": "StorageAccount-name",
       "type": "Microsoft.Storage/storageAccounts",
       "location": "eastus",
diff --git a/articles/event-grid/handle-health-resources-events-using-azure-monitor-alerts.md b/articles/event-grid/handle-health-resources-events-using-azure-monitor-alerts.md
@@ -128,7 +128,7 @@ Here's a sample `AvailabilityStatusChanged` event. Notice that the `type` is set
     "time": "2024-02-22T01:40:17.6532683Z",
     "data": {
         "resourceInfo": {
-            "id": "/subscriptions/sample-subscription/resourceGroups/sample-rg/providers/Microsoft.Compute/virtualMachines/sample-machinee/providers/Microsoft.ResourceHealth/availabilityStatuses/current",
+            "id": "/subscriptions/sample-subscription/resourceGroups/sample-rg/providers/Microsoft.Compute/virtualMachines/sample-machine/providers/Microsoft.ResourceHealth/availabilityStatuses/current",
             "name": "current",
             "type": "Microsoft.ResourceHealth/availabilityStatuses",
             "properties": {
diff --git a/articles/event-grid/manage-event-delivery.md b/articles/event-grid/manage-event-delivery.md
@@ -75,7 +75,7 @@ New-AzEventGridSubscription `
 To turn off dead-lettering, rerun the command to create the event subscription but don't provide a value for `DeadLetterEndpoint`. You don't need to delete the event subscription.
 
 > [!NOTE]
-> If you are using Azure Poweshell on your local machine, use Azure PowerShell version 1.1.0 or greater. Download and install the latest Azure PowerShell from [Azure downloads](https://azure.microsoft.com/downloads/).
+> If you are using Azure PowerShell on your local machine, use Azure PowerShell version 1.1.0 or greater. Download and install the latest Azure PowerShell from [Azure downloads](https://azure.microsoft.com/downloads/).
 
 ## Set retry policy
 
diff --git a/articles/event-grid/monitor-pull-reference.md b/articles/event-grid/monitor-pull-reference.md
@@ -24,7 +24,7 @@ This article provides a reference of log and metric data collected to analyze th
 | FailedPublishedEvents | Failed to publish events | Number of events that failed because Event Grid didn't accept them. This count doesn't include events that were published but failed to reach Event Grid due to a network issue. | 
 | SuccessfulReceivedEvents | Successful received event | Number of events that were successfully returned to (received by) clients. |
 | FailedReceivedEvents | Failed to receive event | Number of events requested by clients that Event Grid couldn't deliver successfully. |
-| SuccessfulAcknowlegedEvents | Successful acknowledged events | Number of events acknowledged by clients. |
+| SuccessfulAcknowledgedEvents | Successful acknowledged events | Number of events acknowledged by clients. |
 | FailedAcknowledgedEvents | Failed to acknowledge events | Number of events that clients didn't acknowledge. |
 | SuccessfulReleasedEvents | Successful released events | Number of events released by queue subscriber clients. |
 | FailedReleasedEvents | Failed to release event counts | Number of events that failed to be released back to Event Grid. |
diff --git a/articles/event-grid/monitor-push-reference.md b/articles/event-grid/monitor-push-reference.md
@@ -125,7 +125,7 @@ Diagnostic settings allow Event Grid users to capture and view **publish and del
 ```json
 {
     "time": "2019-11-01T00:17:13.4389048Z",
-    "resourceId": "/SUBSCRIPTIONS/SAMPLE-SUBSCTIPTION-ID /RESOURCEGROUPS/SAMPLE-RESOURCEGROUP-NAME/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/SAMPLE-TOPIC-NAME ",
+    "resourceId": "/SUBSCRIPTIONS/SAMPLE-SUBSCRIPTION-ID /RESOURCEGROUPS/SAMPLE-RESOURCEGROUP-NAME/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/SAMPLE-TOPIC-NAME ",
     "eventSubscriptionName": "SAMPLEDESTINATION",
     "category": "DeliveryFailures",
     "operationName": "Deliver",
diff --git a/articles/event-grid/mqtt-clients.md b/articles/event-grid/mqtt-clients.md
@@ -54,10 +54,10 @@ Use the "Thumbprint Match" option while using self-signed certificate to authent
 
 > [!NOTE]
 > - clientCertificateAuthentication is always required with a valid value of validationScheme.
-> - authenticationName is not required, but after the first create request, authenticatioName value defaults to ARM name, and then it can not be updated.
+> - authenticationName is not required, but after the first create request, authenticationName value defaults to ARM name, and then it can not be updated.
 > - authenticationName can not be updated.
 > - If validationScheme is anything other than ThumbprintMatch, then allowedThumbprints list can not be provided.
-> - allowedThumbprints list can only be provided and must be provided if validationScheme is ThumbprintMatch with atleast one thumbprint.
+> - allowedThumbprints list can only be provided and must be provided if validationScheme is ThumbprintMatch with at least one thumbprint.
 > - allowedThumbprints can only hold maximum of 2 thumbprints.
 > - Allowed validationScheme values are SubjectMatchesAuthenticationName, DnsMatchesAuthenticationName, UriMatchesAuthenticationName, IpMatchesAuthenticationName, EmailMatchesAuthenticationName, ThumbprintMatch
 > - Using thumbprint with allow reuse of the same certificate across multiple clients.  For other types of validation, the authentication name needs to be in the chosen field of the client certificate.
diff --git a/articles/event-grid/mqtt-establishing-multiple-sessions-per-client.md b/articles/event-grid/mqtt-establishing-multiple-sessions-per-client.md
@@ -54,6 +54,6 @@ Second connect packet:
 - username: “ipv4=127.0.0.1”
 - clientId: “sessionId2”
 
-:::image type="content" source="./media/mqtt-establishing-multiple-sessions-per-client/mqtt-mqttx-app-session-2-connect-configuration.png" alt-text="creenshot showing the MQTTX application client configuration with second session.":::
+:::image type="content" source="./media/mqtt-establishing-multiple-sessions-per-client/mqtt-mqttx-app-session-2-connect-configuration.png" alt-text="Screenshot showing the MQTTX application client configuration with second session.":::
 
 You can use the same client certificate credentials to authenticate both the sessions.
diff --git a/articles/event-grid/mqtt-routing-event-schema.md b/articles/event-grid/mqtt-routing-event-schema.md
@@ -55,7 +55,7 @@ For MQTT v5 messages that are already enveloped in a CloudEvent according to the
 
 ```json
 {
-	"specverion": "1.0",
+	"specversion": "1.0",
 	"id": "9aeb0fdf-c01e-0131-0922-9eb54906e20", // original id stamped by the client. 
 	"time": "2019-11-18T15:13:39.4589254Z", // timestamp when the message was received by the client
 	"type": "Custom.Type", // original type value stamped by the client.
diff --git a/articles/event-grid/mqtt-routing-filtering.md b/articles/event-grid/mqtt-routing-filtering.md
@@ -20,7 +20,7 @@ You can use the Event Grid Subscription’s filtering capability to filter the r
 You can filter on the messages’ MQTT topics through filtering on the "subject" property in the Cloud Event schema. Event Grid Subscriptions supports free simple subject filtering by specifying a starting or ending value for the subject. For example,
 
 - If each vehicle is publishing its location on its own topic (vehicles/vehicle1/gps, vehicles/vehicle2/gps, etc.), you can use the filter: subject ends with "gps" to route only all the location messages.
-- If machines from each section of each factory are publishing on topics that mimic the factory hierarchy (for example, factory1/area2/machine4/telemetry), you can use the filter: subject begins with "factory1/area2/" to route only the messages that belong to facotry1 and area 2 to a specific endpoint. You can replicate this configuration to route messages from other factories/areas to different endpoints.
+- If machines from each section of each factory are publishing on topics that mimic the factory hierarchy (for example, factory1/area2/machine4/telemetry), you can use the filter: subject begins with "factory1/area2/" to route only the messages that belong to factory1 and area 2 to a specific endpoint. You can replicate this configuration to route messages from other factories/areas to different endpoints.
 
 You can also take advantage of the [Event Subscription’s advanced filtering](event-filtering.md) to filter based on the MQTT topic through filtering on the subject property in the Cloud Event Schema. Advanced filters enable you to set more complex filters by specifying a comparison operator, key, and value.
 
diff --git a/articles/event-grid/mqtt-support.md b/articles/event-grid/mqtt-support.md
diff --git a/articles/event-grid/namespace-handler-webhook.md b/articles/event-grid/namespace-handler-webhook.md
diff --git a/articles/event-grid/namespaces-cloud-events.md b/articles/event-grid/namespaces-cloud-events.md
diff --git a/articles/event-grid/outlook-events.md b/articles/event-grid/outlook-events.md
diff --git a/articles/event-grid/partner-events-overview-for-partners.md b/articles/event-grid/partner-events-overview-for-partners.md
diff --git a/articles/event-grid/receive-events-from-namespace-topics-java.md b/articles/event-grid/receive-events-from-namespace-topics-java.md
diff --git a/articles/event-grid/troubleshoot-network-connectivity.md b/articles/event-grid/troubleshoot-network-connectivity.md

Original file line number	Diff line number	Diff line change
`@@ -104,7 +104,7 @@ You can also enable collection of all metrics for the system topic.`
`104`	`104`	```json
`105`	`105`	`{`
`106`	`106`	`"time": "2019-11-01T00:17:13.4389048Z",`
`107`		`- "resourceId": "/SUBSCRIPTIONS/SAMPLE-SUBSCTIPTION-ID /RESOURCEGROUPS/SAMPLE-RESOURCEGROUP-NAME/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/SAMPLE-TOPIC-NAME ",`
	`107`	`+ "resourceId": "/SUBSCRIPTIONS/SAMPLE-SUBSCRIPTION-ID /RESOURCEGROUPS/SAMPLE-RESOURCEGROUP-NAME/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/SAMPLE-TOPIC-NAME ",`
`108`	`108`	`"eventSubscriptionName": "SAMPLEDESTINATION",`
`109`	`109`	`"category": "DeliveryFailures",`
`110`	`110`	`"operationName": "Deliver",`