Merge pull request #125309 from ArieHein/Spelling-53

Spelling Fixes

Author: v-dirichards

articles/event-grid/assign-custom-domain-name.md

@@ -64,7 +64,7 @@ For information configuring system and user-assigned identities using the Azure
 1. Use the following command to create an Azure Key Vault account: 
 
     ```azurecli-interactive
-    az keyvault create --name "<your-unique-keyvault-name>" --resource-group "<resource group name>" --location "centraluseaup" 
+    az keyvault create --name "<your-unique-keyvault-name>" --resource-group "<resource group name>" --location "centraluseuap" 
     ```
 2. Use the following command to import a certificate to the Azure Key Vault 
 
@@ -268,7 +268,7 @@ To prove your domain ownership, follow these steps:
                                 "type": "SystemAssigned"
                             },
                             "certificateInfo": {
-                                "keyVaultArmId": " /subscriptions/AZURESUBCRIPTIONID/resourceGroups/RESOURCEGROUPNAME/providers/Microsoft.KeyVault/vaults/KEYVAULTNAME",
+                                "keyVaultArmId": " /subscriptions/AZURESUBSCRIPTIONID/resourceGroups/RESOURCEGROUPNAME/providers/Microsoft.KeyVault/vaults/KEYVAULTNAME",
                                 "certificateName": "CERTIFICATENAME"
                             }
                         }

articles/event-grid/authenticate-with-namespaces-using-json-web-tokens.md

@@ -49,7 +49,7 @@ For information configuring system and user-assigned identities using the Azure
 1. Use the following command to create an Azure Key Vault account: 
 
     ```azurecli-interactive
-    az keyvault create --name "<your-unique-keyvault-name>" --resource-group "<resource group name>" --location "centraluseaup" 
+    az keyvault create --name "<your-unique-keyvault-name>" --resource-group "<resource group name>" --location "centraluseuap" 
     ```
 2. Use the following command to import a certificate to the Azure Key Vault 
 

articles/event-grid/custom-event-quickstart-portal.md

@@ -105,7 +105,7 @@ The first example uses Azure CLI. It gets the URL and key for the custom topic,
 ### Azure CLI
 1. In the Azure portal, select **Cloud Shell**. The Cloud Shell opens in the bottom pane of the web browser. 
 
-    :::image type="content" source="./media/custom-event-quickstart-portal/select-cloud-shell.png" alt-text="Screnshot that shows the selection of Cloud Shell button." lightbox="./media/custom-event-quickstart-portal/select-cloud-shell.png":::
+    :::image type="content" source="./media/custom-event-quickstart-portal/select-cloud-shell.png" alt-text="Screenshot that shows the selection of Cloud Shell button." lightbox="./media/custom-event-quickstart-portal/select-cloud-shell.png":::
 1. If the Cloud Shell opens a PowerShell session, select **Switch to Bash** in the top-left corner of the Cloud Shell window. If not, continue to the next step. 
 
     :::image type="content" source="./media/custom-event-quickstart-portal/cloud-shell-bash.png" alt-text="Screenshot that shows the Cloud Shell with Bash selected in the top-left corner.":::

articles/event-grid/monitor-mqtt-delivery-reference.md

@@ -34,7 +34,7 @@ This article provides a reference of log and metric data collected to analyze th
 
 
 > [!NOTE]
-> Each subscription request increments the MQTT.RequestCount metric, while each topic filter within the subscription request increments the subscription operation metrics. For example, consider a subscription request that is sent with five different topic filters. Three of these topic filters were succeessfully processed while two of the topic filters failed to be processed. The following list represent the resulting increments to the metrics:
+> Each subscription request increments the MQTT.RequestCount metric, while each topic filter within the subscription request increments the subscription operation metrics. For example, consider a subscription request that is sent with five different topic filters. Three of these topic filters were successfully processed while two of the topic filters failed to be processed. The following list represent the resulting increments to the metrics:
 > - MQTT.RequestCount:1
 > - MQTT.SuccessfulSubscriptionOperations:3
 > - MQTT.FailedSubscriptionOperations:2

articles/event-grid/monitor-virtual-machine-changes-logic-app.md

@@ -222,7 +222,7 @@ Now add an [*action*](../logic-apps/logic-apps-overview.md#logic-app-concepts) s
 
 1. Provide information about the email as specified in the following table:
 
-   ![Screenshot that shows the workflow designer with dynamic content being addded to email subject line for a true condition.](./media/monitor-virtual-machine-changes-logic-app/logic-app-empty-email-action.png)
+   ![Screenshot that shows the workflow designer with dynamic content being added to email subject line for a true condition.](./media/monitor-virtual-machine-changes-logic-app/logic-app-empty-email-action.png)
 
    > [!TIP]
    > To select output from the previous steps in your workflow, click inside an edit box so that the dynamic content list appears, 

articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md

@@ -186,7 +186,7 @@ This section shows you how to create a .NET Core console application to send eve
     A batch of 3 events has been published.
     ```
     > [!NOTE]
-    > If you get an error "InvalidIssuer: Token issuer is invalid" when using Microsoft Entra authentication, it may be because the wrong Entra Tenant Id is being used. In you code replace'new DefaultAzureCredential()' with 'new DefaultAzureCredential(new DefaultAzureCredentialOptions {TenantId = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"})' to explictly specify Entra Tenant Id.
+    > If you get an error "InvalidIssuer: Token issuer is invalid" when using Microsoft Entra authentication, it may be because the wrong Entra Tenant Id is being used. In you code replace'new DefaultAzureCredential()' with 'new DefaultAzureCredential(new DefaultAzureCredentialOptions {TenantId = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"})' to explicitly specify Entra Tenant Id.
 
 
     > [!IMPORTANT]

articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md

@@ -266,7 +266,7 @@ This section shows how to write a .NET Core console application that receives ev
     // connection string for the Azure Storage account
     const string blobStorageConnectionString = "AZURESTORAGECONNECTIONSTRING";
 
-    // name of the blob container that will be userd as a checkpoint store
+    // name of the blob container that will be used as a checkpoint store
     const string blobContainerName = "BLOBCONTAINERNAME";
 
     // Create a blob container client that the event processor will use 

articles/external-attack-surface-management/modifying-inventory-assets.md

@@ -64,7 +64,7 @@ You should modify assets from the inventory list page if you want to update nume
 
 1. On the leftmost pane of your Microsoft Defender External Attack Surface Management (Defender EASM) resource, select **Inventory**.
 
-2. Apply filters to produce your intended results. In this example, we're looking for domains that expire within 30 days that require renewal. The applied label helps you more quickly access any expiring domains to simplify the remediation process. You can apply as many filters as necessary to obtain the specific results that are needed. For more information on filters, see [Inventory filters overview](inventory-filters.md). For instances where you'd like to mark CVEs as non-applicable, the relevant dashbaord chart drilldown provides a link that directly routes you to this Inventory page with the correct filters applied. 
+2. Apply filters to produce your intended results. In this example, we're looking for domains that expire within 30 days that require renewal. The applied label helps you more quickly access any expiring domains to simplify the remediation process. You can apply as many filters as necessary to obtain the specific results that are needed. For more information on filters, see [Inventory filters overview](inventory-filters.md). For instances where you'd like to mark CVEs as non-applicable, the relevant dashboard chart drilldown provides a link that directly routes you to this Inventory page with the correct filters applied. 
 
    ![Screenshot that shows the inventory list view with the Add filter dropdown opened to display the query editor.](media/labels-2.png)
 

articles/firewall/monitor-firewall-reference.md

@@ -76,7 +76,7 @@ The latency probe currently uses Microsoft's Ping Mesh technology, which is base
 - Recommended latency threshold: A recommended guideline is that latency should not exceed 3x the baseline. If this threshold is crossed, further investigation is recommended.
 - Check the rule limit: Ensure that the network rules are within the 20K rule limit. Exceeding this limit can affect performance. 
 - New application onboarding: Check for any newly onboarded applications that could be adding significant load or causing latency issues.
-- Support request: If you observe continuous latency degredation that does not align with expected behavior, consider filing a support ticket for further assistance. 
+- Support request: If you observe continuous latency degradation that does not align with expected behavior, consider filing a support ticket for further assistance. 
 
   :::image type="content" source="media/metrics/latency-probe.png" alt-text="Screenshot showing the Azure Firewall Latency Probe metric.":::
 

articles/firewall/premium-migrate.md

@@ -168,15 +168,15 @@ function TransformPolicyToPremium {
     Write-Host "Populating rules in new policy"
     foreach ($ruleCollectionGroup in $Policy.RuleCollectionGroups) {
         $ruleResource = Get-AzResource -ResourceId $ruleCollectionGroup.Id
-        $ruleToTransfom = Get-AzFirewallPolicyRuleCollectionGroup -AzureFirewallPolicy $Policy -Name $ruleResource.Name
+        $ruleToTransform = Get-AzFirewallPolicyRuleCollectionGroup -AzureFirewallPolicy $Policy -Name $ruleResource.Name
         $ruleCollectionGroup = @{
             FirewallPolicyObject = $premiumPolicy
-            Priority = $ruleToTransfom.Properties.Priority
-            Name = $ruleToTransfom.Name
+            Priority = $ruleToTransform.Properties.Priority
+            Name = $ruleToTransform.Name
         }
 
-        if ($ruleToTransfom.Properties.RuleCollection.Count) {
-            $ruleCollectionGroup["RuleCollection"] = $ruleToTransfom.Properties.RuleCollection
+        if ($ruleToTransform.Properties.RuleCollection.Count) {
+            $ruleCollectionGroup["RuleCollection"] = $ruleToTransform.Properties.RuleCollection
         }
 
         Set-AzFirewallPolicyRuleCollectionGroup @ruleCollectionGroup