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

Spelling Fixes

Author: ttorble

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
 

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
 

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. |
 

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]

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.     

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

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",

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 |

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",

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": {