Merge pull request #125093 from ArieHein/Spelling-Wave-22

ttorble · web-flow · commit d3d5e17d33a2 · 2024-12-09T15:10:29.000Z
Spelling Fixes
diff --git a/articles/event-hubs/event-hubs-data-explorer.md b/articles/event-hubs/event-hubs-data-explorer.md
@@ -22,7 +22,7 @@ Operations run on an Azure Event Hubs namespace are of two kinds.
 >  * The Event Hubs Data Explorer doesn't support **management operations**. The event hub must be created before the data explorer can send or view events from that event hub.
 >  * While events payloads (known as **values** in Kafka) sent using the **Kafka protocol** will be visible via the data explorer, the **key** for the specific event will not be visible.
 >  * We advise against using the Event Hubs Data Explorer for larger messages, as this may result in timeouts, depending on the message size, network latency between client and Service Bus service etc. Instead, we recommend that you use your own client to work with larger messages, where you can specify your own timeout values.
->  * The operations that a user can perform using Event Hubs Data Exploerer is determined by the [role-based access control (RBAC)](authorize-access-azure-active-directory.md#azure-built-in-roles-for-azure-event-hubs) role that the user is assigned to. 
+>  * The operations that a user can perform using Event Hubs Data Explorer is determined by the [role-based access control (RBAC)](authorize-access-azure-active-directory.md#azure-built-in-roles-for-azure-event-hubs) role that the user is assigned to. 
 
 ## Prerequisites
 
diff --git a/articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md b/articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
@@ -276,7 +276,7 @@ Replace the contents of **Program.cs** with the following code:
     using System.Text;
     
     // Create a blob container client that the event processor will use
-    // TODO: Replace <STORAGE_ACCOUNT_NAME> and <BLOB_CONTATINAER_NAME> with actual names
+    // TODO: Replace <STORAGE_ACCOUNT_NAME> and <BLOB_CONTAINER_NAME> with actual names
     BlobContainerClient storageClient = new BlobContainerClient(
         new Uri("https://<STORAGE_ACCOUNT_NAME>.blob.core.windows.net/<BLOB_CONTAINER_NAME>"),
         new DefaultAzureCredential());
diff --git a/articles/event-hubs/event-hubs-kafka-connect-debezium.md b/articles/event-hubs/event-hubs-kafka-connect-debezium.md
@@ -220,7 +220,7 @@ You should see the JSON payloads representing the change data events generated i
         "source": {
             "version": "1.2.0.Final",
             "connector": "postgresql",
-            "name": "fullfillment",
+            "name": "fulfillment",
             "ts_ms": 1593018069944,
             "snapshot": "last",
             "db": "postgres",
diff --git a/articles/event-hubs/event-hubs-resource-manager-namespace-event-hub-enable-capture.md b/articles/event-hubs/event-hubs-resource-manager-namespace-event-hub-enable-capture.md
@@ -174,7 +174,7 @@ The name format used by Event Hubs Capture to write the Avro files. The capture
       "type": "string",
       "defaultValue": "{Namespace}/{EventHub}/{PartitionId}/{Year}/{Month}/{Day}/{Hour}/{Minute}/{Second}",
       "metadata": {
-        "description": "A Capture Name Format must contain {Namespace}, {EventHub}, {PartitionId}, {Year}, {Month}, {Day}, {Hour}, {Minute} and {Second} fields. These can be arranged in any order with or without delimeters. E.g.  Prod_{EventHub}/{Namespace}\\{PartitionId}_{Year}_{Month}/{Day}/{Hour}/{Minute}/{Second}"
+        "description": "A Capture Name Format must contain {Namespace}, {EventHub}, {PartitionId}, {Year}, {Month}, {Day}, {Hour}, {Minute} and {Second} fields. These can be arranged in any order with or without delimiters. E.g.  Prod_{EventHub}/{Namespace}\\{PartitionId}_{Year}_{Month}/{Day}/{Hour}/{Minute}/{Second}"
       }
     }
 
diff --git a/articles/event-hubs/geo-replication.md b/articles/event-hubs/geo-replication.md
@@ -48,7 +48,7 @@ The Metadata DR feature replicates configuration information for a namespace fro
 
 The newer Geo-replication feature replicates configuration information and all of the data from a primary namespace to one, or more secondary namespaces. When a failover is performed, the selected secondary becomes the primary and the previous primary becomes a secondary. Users can perform a failover back to the original primary when desired. 
 
-This rest of this article focuses on the Geo-replication feature. For details on the metadata DR feature, see [Event Hubs Geo-disater recovery for metadata](./event-hubs-geo-dr.md).
+This rest of this article focuses on the Geo-replication feature. For details on the metadata DR feature, see [Event Hubs Geo-disaster recovery for metadata](./event-hubs-geo-dr.md).
 
 ## Geo-replication 
 The public preview of the Geo-replication feature is supported for namespaces in Event Hubs self-serve scaling dedicated clusters. You can use the feature with new, or existing namespaces in dedicated self-serve clusters. The following features aren't supported with Geo-replication:
diff --git a/articles/event-hubs/resource-governance-with-app-groups.md b/articles/event-hubs/resource-governance-with-app-groups.md
@@ -266,7 +266,7 @@ az eventhubs namespace application-group policy add --namespace-name mynamespace
 ```
 
 ### [Azure PowerShell](#tab/powershell)
-Use the [Set-AzEventHubApplicationGroup](/powershell/module/az.eventhub/set-azeventhubapplicationgroup) command with `-ThrottingPolicyConfig` set to appropriate values. 
+Use the [Set-AzEventHubApplicationGroup](/powershell/module/az.eventhub/set-azeventhubapplicationgroup) command with `-ThrottlingPolicyConfig` set to appropriate values. 
 
 **Example:**
 ```azurepowershell-interactive
diff --git a/articles/event-hubs/test-locally-with-event-hub-emulator.md b/articles/event-hubs/test-locally-with-event-hub-emulator.md
@@ -79,7 +79,7 @@ To run the Event Hubs emulator locally on Linux or macOS:
 
    ```
 
-2. To sping up containers for Event Hubs emulator, Save the following .yaml file as *docker-compose.yaml*.
+2. To spin up containers for Event Hubs emulator, Save the following .yaml file as *docker-compose.yaml*.
 
    ```
    name: microsoft-azure-eventhubs
diff --git a/articles/event-hubs/use-geo-replication.md b/articles/event-hubs/use-geo-replication.md
@@ -68,7 +68,7 @@ In the case where your primary region goes down completely, you can still perfor
 ## Remove a secondary
 To remove a Geo-replication pairing with a secondary, select **Geo-replication** on the left menu, select the secondary region, and then select **Remove**. At the prompt, enter the word **delete**, and then you can delete the secondary. 
 
-:::image type="content" source="./media/use-geo-replication/remove-secondary.png" alt-text="Screenshot of the Remove secondary function in the geo-replcation UI.":::
+:::image type="content" source="./media/use-geo-replication/remove-secondary.png" alt-text="Screenshot of the Remove secondary function in the geo-replication UI.":::
 
 When a secondary region is removed, all of the data that it held is also removed. If you wish to re-enable Geo-replication with that region and cluster, it has to replicate the primary region data all over again. 
 
diff --git a/articles/expressroute/circuit-placement-api.md b/articles/expressroute/circuit-placement-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'Azure ExpressRoute CrossConnnections circuit placement API'
+title: 'Azure ExpressRoute CrossConnections circuit placement API'
 description: This article provides a detailed overview for ExpressRoute partners about the ExpressRoute CrossConnections circuit placement API.
 services: expressroute
 author: mialdrid
diff --git a/articles/expressroute/cross-connections-api-development.md b/articles/expressroute/cross-connections-api-development.md
@@ -1,5 +1,5 @@
 ---
-title: 'Azure ExpressRoute CrossConnnections API development and integration'
+title: 'Azure ExpressRoute CrossConnections API development and integration'
 description: This article provides a detailed overview for ExpressRoute partners about the expressRouteCrossConnections resource type.
 services: expressroute
 author: duongau
@@ -12,13 +12,13 @@ ms.author: duau
 ---
 
 
-# ExpressRoute CrossConnnections API development and integration
+# ExpressRoute CrossConnections API development and integration
 
 The ExpressRoute Partner Resource Manager API allows ExpressRoute partners to manage the layer-2 and layer-3 configuration of customer ExpressRoute circuits. The ExpressRoute Partner Resource Manager API introduces a new resource type, **expressRouteCrossConnections**. Partners use this resource to manage customer ExpressRoute circuits.
 
 ## Workflow
 
-The expressRouteCrossConnections resource is a shadow resource to the ExpressRoute circuit. When an Azure customer creates an ExpressRoute circuit and selects a specific ExpressRoute partner, Microsoft creates an expressRouteCrossConnections resource in the partner's Azure ExpressRoute management subscription. In doing so, Microsoft defines a resource group to create the expressRouteCrossConnections resource in. The naming standard for the resource group is **CrossConnection-*PeeringLocation***; where PeeringLocation = the ExpressRoute Location. For example, if a customer creates an ExpressRoute circuit in Denver, the CrossConnection will be created in the partner's Azure subscription in the following resource group: **CrossConnnection-Denver**.
+The expressRouteCrossConnections resource is a shadow resource to the ExpressRoute circuit. When an Azure customer creates an ExpressRoute circuit and selects a specific ExpressRoute partner, Microsoft creates an expressRouteCrossConnections resource in the partner's Azure ExpressRoute management subscription. In doing so, Microsoft defines a resource group to create the expressRouteCrossConnections resource in. The naming standard for the resource group is **CrossConnection-*PeeringLocation***; where PeeringLocation = the ExpressRoute Location. For example, if a customer creates an ExpressRoute circuit in Denver, the CrossConnection will be created in the partner's Azure subscription in the following resource group: **CrossConnection-Denver**.
 
 ExpressRoute partners manage layer-2 and layer-3 configuration by issuing REST operations against the expressRouteCrossConnections resource.
 
diff --git a/articles/expressroute/expressroute-faqs.md b/articles/expressroute/expressroute-faqs.md
@@ -454,9 +454,9 @@ See the recommendation for [High availability and failover with Azure ExpressRou
 
 Yes. Office 365 GCC service endpoints are reachable through the Azure US Government ExpressRoute. However, you first need to open a support ticket on the Azure portal to provide the prefixes you intend to advertise to Microsoft. Your connectivity to Office 365 GCC services will be established after the support ticket is resolved. 
 
-### Can I have ExpressRoute Private Peering in an Azure Goverment environment with Virtual Network Gateways in Azure commercial cloud? 
+### Can I have ExpressRoute Private Peering in an Azure Government environment with Virtual Network Gateways in Azure commercial cloud? 
 
-No, it's not possible to establish ExpressRoute Private peering in an Azure Goverment environment with a virtual network gateway in Azure commercial cloud environments. Furthermore, the scope of the ExpressRoute Government Microsoft Peering is limited to only public IPs within Azure government regions and doesn't extend to the broader ranges of commercial public IPs. 
+No, it's not possible to establish ExpressRoute Private peering in an Azure Government environment with a virtual network gateway in Azure commercial cloud environments. Furthermore, the scope of the ExpressRoute Government Microsoft Peering is limited to only public IPs within Azure government regions and doesn't extend to the broader ranges of commercial public IPs. 
 
 ## Route filters for Microsoft peering
 
diff --git a/articles/expressroute/expressroute-troubleshooting-expressroute-overview.md b/articles/expressroute/expressroute-troubleshooting-expressroute-overview.md
@@ -342,7 +342,7 @@ When your results are ready, you have two sets of them for the primary and secon
 
 * **One MSEE shows no matches, but the other shows good matches**: This result indicates that one MSEE isn't receiving or passing any traffic. It might be offline (for example, BGP/ARP is down).
   * You can run additional testing to confirm the unhealthy path by advertising a unique /32 on-premises route over the BGP session on this path. 
-  * Run "Test your private peering connectivity" using the unique /32 advertised as the on-premise destination address and reveiw the results to confirm the path health. 
+  * Run "Test your private peering connectivity" using the unique /32 advertised as the on-premise destination address and review the results to confirm the path health. 
 
 Your test results for each MSEE device look like the following example:
 
diff --git a/articles/expressroute/site-to-site-vpn-over-microsoft-peering.md b/articles/expressroute/site-to-site-vpn-over-microsoft-peering.md
@@ -156,7 +156,7 @@ In this example, the variable declarations correspond to the example network. Wh
   "vpnType": "RouteBased",                // type of VPN gateway
   "sharedKey": "string",                  // shared secret needs to match with on-premises configuration
   "asnVpnGateway": 65000,                 // BGP Autonomous System number assigned to the VPN Gateway 
-  "asnRemote": 65010,                     // BGP Autonmous Syste number assigned to the on-premises device
+  "asnRemote": 65010,                     // BGP Autonomous System number assigned to the on-premises device
   "bgpPeeringAddress": "172.16.0.3",      // IP address of the remote BGP peer on-premises
   "connectionName": "vpn2local1",
   "vnetID": "[resourceId('Microsoft.Network/virtualNetworks', variables('virtualNetworkName'))]",
diff --git a/articles/external-attack-surface-management/understanding-dashboards.md b/articles/external-attack-surface-management/understanding-dashboards.md
@@ -257,7 +257,7 @@ This chart displays live PII sites by their usage of SSL certificates. By refere
 
 A login page is a page on a website where a user has the option to enter a username and password to gain access to services hosted on that site. Login pages have specific requirements under GDPR, so Defender EASM references the DOM of all scanned pages to search for code that correlates to a login. For instance, login pages must be secure to be compliant. This first chart displays Login websites by protocol (HTTP or HTTPS) and the second by certificate posture. 
 
-![Screenshot of Login websites by protcol chart.](media/Dashboards-25.png)
+![Screenshot of Login websites by protocol chart.](media/Dashboards-25.png)
 
 ![Screenshot of Login websites by certificate posture chart.](media/Dashboards-26.png)
 
diff --git a/articles/firewall-manager/secure-cloud-network-powershell.md b/articles/firewall-manager/secure-cloud-network-powershell.md
@@ -91,7 +91,7 @@ $AzFW = New-AzFirewall -Name "azfw1" -ResourceGroupName $RG -Location $Location
 Enabling logging from the Azure Firewall to Azure Monitor is optional, but in this example you use the Firewall logs to prove that traffic is traversing the firewall:
 
 ```azurepowershell
-# Optionally, enable looging of Azure Firewall to Azure Monitor
+# Optionally, enable logging of Azure Firewall to Azure Monitor
 $LogWSName = "vwan-" + (Get-Random -Maximum 99999) + "-" + $RG
 $LogWS = New-AzOperationalInsightsWorkspace -Location $Location -Name $LogWSName -Sku Standard -ResourceGroupName $RG
 Set-AzDiagnosticSetting -ResourceId $AzFW.Id -Enabled $True -Category AzureFirewallApplicationRule, AzureFirewallNetworkRule -WorkspaceId $LogWS.ResourceId
diff --git a/articles/firewall/deploy-rules-powershell.md b/articles/firewall/deploy-rules-powershell.md
@@ -29,7 +29,7 @@ Carefully review the following steps. You should first try it on a test policy t
 
 ```azurepowershell
 Connect-AzAccount
-Set-AzContext -Subscription "<Subscritpion ID>"
+Set-AzContext -Subscription "<Subscription ID>"
 
 ```
 
diff --git a/articles/firewall/firewall-copilot.md b/articles/firewall/firewall-copilot.md
@@ -80,7 +80,7 @@ To view the list of built-in system capabilities for Azure Firewall, use the fol
 
     > [!IMPORTANT]
     > Use of Copilot in Azure to query Azure Firewall is included with Security Copilot and requires [security compute units (SCUs)](/security-copilot/get-started-security-copilot#security-compute-units). You can provision SCUs and increase or decrease them at any time. For more information on SCUs, see [Get started with Microsoft Security Copilot](/security-copilot/get-started-security-copilot).
-    > If you do not have Security Copilot properly configured but ask a question relavent to the Azure Firewall capabilities via the Copilot in Azure experience then you will see an error message.
+    > If you do not have Security Copilot properly configured but ask a question relevant to the Azure Firewall capabilities via the Copilot in Azure experience then you will see an error message.
    
 ## Sample Azure Firewall prompts
 
diff --git a/articles/firewall/monitor-firewall-reference.md b/articles/firewall/monitor-firewall-reference.md
@@ -56,7 +56,7 @@ The *AZFW Latency Probe* metric measures the overall or average latency of Azure
 **What the AZFW Latency Probe Metric Measures (and Doesn't):**
 
 - What it measures: The latency of the Azure Firewall within the Azure platform
-- What it doesn't meaure: The metric does not capture end-to-end latency for the entire network path. Instead, it reflects the performance within the firewall, rather than how much latency Azure Firewall introduces into the network. 
+- What it doesn't measure: The metric does not capture end-to-end latency for the entire network path. Instead, it reflects the performance within the firewall, rather than how much latency Azure Firewall introduces into the network. 
 - Error reporting: If the latency metric isn't functioning correct, it reports a value of 0 in the metrics dashboard, indicating a probe failure or interruption.
 
 **Factors that impact latency:**
@@ -65,10 +65,10 @@ The *AZFW Latency Probe* metric measures the overall or average latency of Azure
 - Networking issues within the Azure platform
 
 **Latency Probes: From ICMP to TCP**
-The latency probe currently uses Microsoft's Ping Mesh technology, which is based on ICMP (Internet Control Message Protcol). ICMP is suitable for quick health checks, like ping requests, but it may not accurately represent real-world application traffic, which typically relis on TCP.However, ICMP probes prioritize differently across the Azure platform, which can result in variation across SKUs. To reduce these discrepancies, Azure Firewall plans to transition to TCP-based probes. 
+The latency probe currently uses Microsoft's Ping Mesh technology, which is based on ICMP (Internet Control Message Protocol). ICMP is suitable for quick health checks, like ping requests, but it may not accurately represent real-world application traffic, which typically relis on TCP.However, ICMP probes prioritize differently across the Azure platform, which can result in variation across SKUs. To reduce these discrepancies, Azure Firewall plans to transition to TCP-based probes. 
 
 - Latency spikes: With ICMP probes, intermittent spikes are normal and are part of the host network's standard behavior. These should not be misinterpreted as firewall issues unless they are persistent.
-- Average latency: On average, the latency of Azure Firewall is expected to range from 1ms to 10 ms, dpending on the Firewall SKU and deployment size.
+- Average latency: On average, the latency of Azure Firewall is expected to range from 1ms to 10 ms, depending on the Firewall SKU and deployment size.
 
 **Best Practices for Monitoring Latency**
 - Set a baseline: Establish a latency baseline under light traffic conditions for accurate comparisons during normal or peak usage.
diff --git a/articles/firewall/premium-deploy.md b/articles/firewall/premium-deploy.md
@@ -85,7 +85,7 @@ You can use `curl` to control various HTTP headers and simulate malicious traffi
 
    ```
    { “msg” : “TCP request from 10.0.100.5:16036 to 10.0.20.10:80. Action: Alert. Rule: 2032081. IDS: 
-   USER_AGENTS Suspicious User Agent (HaxerMen). Priority: 1. Classification: A Network Tojan was 
+   USER_AGENTS Suspicious User Agent (HaxerMen). Priority: 1. Classification: A Network Trojan was 
    detected”}
    ```
 
diff --git a/articles/firewall/snat-private-range.md b/articles/firewall/snat-private-range.md
@@ -180,7 +180,7 @@ You can use the Azure portal to specify private IP address ranges for the firewa
 You can configure Azure Firewall to auto-learn both registered and private ranges every 30 minutes. These learned address ranges are considered to be internal to the network, so traffic to destinations in the learned ranges aren't SNATed. Auto-learn SNAT ranges requires Azure Route Server to be deployed in the same VNet as the Azure Firewall. The firewall must be associated with the Azure Route Server and configured to auto-learn SNAT ranges in the Azure Firewall Policy. You can currently use an ARM template, Azure PowerShell, or the Azure portal to configure auto-learn SNAT routes.
 
 > [!NOTE]
-> Auto-learn SNAT routes is availalable only on VNet deployments (hub virtual network). It isn't availble on VWAN deployments (secured virtual hub). For more information about Azure Firewall architecture options, see [What are the Azure Firewall Manager architecture options?](../firewall-manager/vhubs-and-vnets.md)
+> Auto-learn SNAT routes is available only on VNet deployments (hub virtual network). It isn't available on VWAN deployments (secured virtual hub). For more information about Azure Firewall architecture options, see [What are the Azure Firewall Manager architecture options?](../firewall-manager/vhubs-and-vnets.md)
 
 ### Configure using an ARM template
 

Original file line number	Diff line number	Diff line change
`@@ -174,7 +174,7 @@ The name format used by Event Hubs Capture to write the Avro files. The capture`
`174`	`174`	`"type": "string",`
`175`	`175`	`"defaultValue": "{Namespace}/{EventHub}/{PartitionId}/{Year}/{Month}/{Day}/{Hour}/{Minute}/{Second}",`
`176`	`176`	`"metadata": {`
`177`		`- "description": "A Capture Name Format must contain {Namespace}, {EventHub}, {PartitionId}, {Year}, {Month}, {Day}, {Hour}, {Minute} and {Second} fields. These can be arranged in any order with or without delimeters. E.g. Prod_{EventHub}/{Namespace}\\{PartitionId}_{Year}_{Month}/{Day}/{Hour}/{Minute}/{Second}"`
	`177`	`+ "description": "A Capture Name Format must contain {Namespace}, {EventHub}, {PartitionId}, {Year}, {Month}, {Day}, {Hour}, {Minute} and {Second} fields. These can be arranged in any order with or without delimiters. E.g. Prod_{EventHub}/{Namespace}\\{PartitionId}_{Year}_{Month}/{Day}/{Hour}/{Minute}/{Second}"`
`178`	`178`	`}`
`179`	`179`	`}`
`180`	`180`