Merge pull request #302298 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/api-management/api-management-get-started-publish-versions.md

@@ -9,7 +9,7 @@ ms.topic: tutorial
 ms.date: 03/26/2025
 ms.author: danlep
 
-#customer intent: As a developer, I want to publish mutliple versions of an API so that all callers to the API don't need to use the same version.
+#customer intent: As a developer, I want to publish multiple versions of an API so that all callers to the API don't need to use the same version.
 ---
 
 # Tutorial: Publish multiple versions of your API

articles/api-management/mock-api-responses.md

@@ -60,7 +60,7 @@ The steps in this section show how to create an HTTP API with no backend.
 1. In the **Create an HTTP API** window, select **Full**.
 1. In **Display name**, enter *Test API*.
 1. In **Products**, select *Unlimited*, if that value is available. This value is available only in some tiers. You can leave the value blank for this tutorial, but you need to associate the API with a product to publish it. For more information, see [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api). 
-1. In **Gateways**, select **Managed** if this option is available. (This option is avaiable only in certain service tiers.)
+1. In **Gateways**, select **Managed** if this option is available. (This option is available only in certain service tiers.)
 1. Select **Create**.
 
     :::image type="content" source="media/mock-api-responses/create-http-api.png" alt-text="Screenshot that shows the Create an HTTP API window." lightbox="media/mock-api-responses/create-http-api.png":::

articles/azure-maps/zoom-levels-and-tile-grid.md

@@ -430,7 +430,7 @@ namespace AzureMaps
             var tl = GlobalPixelToPosition(new double[] { left, top }, zoom, tileSize);
             var br = GlobalPixelToPosition(new double[] { right, bottom }, zoom, tileSize);
 
-            //Boudning box in the format: [west, south, east, north];
+            //Bounding box in the format: [west, south, east, north];
             var bounds = new double[] { tl[0], br[1], br[0], tl[1] };
 
             return GetQuadkeysInBoundingBox(bounds, zoom, tileSize);
@@ -838,7 +838,7 @@ module AzureMaps {
             var tl = this.GlobalPixelToPosition([left, top], zoom, tileSize);
             var br = this.GlobalPixelToPosition([right, bottom], zoom, tileSize);
 
-            //Boudning box in the format: [west, south, east, north];
+            //Bounding box in the format: [west, south, east, north];
             var bounds = [tl[0], br[1], br[0], tl[1]];
 
             return this.GetQuadkeysInBoundingBox(bounds, zoom, tileSize);

articles/azure-vmware/azure-vmware-solution-known-issues.md

@@ -15,6 +15,7 @@ Refer to the table to find details about resolution dates or possible workaround
 
 |Issue | Date discovered | Workaround | Date resolved |
 | :------------------------------------- | :------------ | :------------- | :------------- |
+| Changing the default NSX Tier-1 name may cause some NSX features added through the Azure portal, such as DNS Zone and the Segment page, to not function as expected. | June 2025 | Azure VMware Solution uses the NSX Tier-1 name "TNTxx-T1" (where xx is the internal tenant ID) for these features. Therefore, please do not change the default Tier-1 name. | N/A
 | Creating stateful gateway firewall rules associated with Azure VMware Solution default NSX-T tier-0 router causes unwanted/unexpected behavior. | May 2025 | Azure VMware Solution deploys with a stateless NSX-T tier-0 router.  As such, stateful firewall rules are incompatible even though the NSX-T UI may allow it.  Apply stateful services and/or firewall rules at the tier-1 router. | N/A
 | AV64 hosts running vSAN Express Storage Architecture (ESA), may see a High pNIC errors due to buffer overflows. [Getting alarm in relation to "High pNic error rate detected" on hosts in vSAN clusters when using Mellanox NICs](https://knowledge.broadcom.com/external/article/392333/getting-alarm-in-relation-to-high-pnic-e.html) | June 2025 |  The alert should be considered an informational message, since Microsoft manages the service. Select the **Reset to Green** link to clear it. |
 |[VMSA-2025-0012](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25738) Multiple vulnerabilities (CVE-2025-22243, CVE-2025-22244, CVE-2025-22245) have been identified in VMware NSX. | May 2025 | The vulnerability described in the Broadcom document does not apply to Azure VMware Solution due to existing compensating controls mitigate the risk of exploitation. | The upcoming version of NSX will include a patch to address this vulnerability. |

articles/event-hubs/event-hubs-capture-python.md

@@ -62,7 +62,7 @@ In this section, you create a Python script that sends 200 events (10 devices *
         devices.append(str(uuid.uuid4()))
 
     # Create a producer client to produce and publish events to the event hub.
-    producer = EventHubProducerClient.from_connection_string(conn_str="EVENT HUBS NAMESAPCE CONNECTION STRING", eventhub_name="EVENT HUB NAME")
+    producer = EventHubProducerClient.from_connection_string(conn_str="EVENT HUBS NAMESPACE CONNECTION STRING", eventhub_name="EVENT HUB NAME")
 
     for y in range(0,20):    # For each device, produce 20 events. 
         event_data_batch = producer.create_batch() # Create a batch. You will add events to the batch later. 

articles/event-hubs/sdks.md

@@ -35,8 +35,8 @@ The following table lists older Azure Event Hubs runtime clients. While these pa
 
 | Language | Package | Reference | 
 | -------- | ------- | --------------- | 
-| . NET Standard  | [Microsoft.Azure.EventHubs](https://www.nuget.org/packages/Microsoft.Azure.EventHubs/) (**legacy**) | <ul><li>[GitHub location](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/eventhub/Microsoft.Azure.EventHubs)</li><li>[Tutorial](event-hubs-dotnet-standard-getstarted-send.md)</li></ul> | 
-|       | [Microsoft.Azure.EventHubs.Processor](https://www.nuget.org/packages/Microsoft.Azure.EventHubs.Processor) (**legacy**) | <ul><li>[GitHub location](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/eventhub/Microsoft.Azure.EventHubs.Processor)</li><li>[Tutorial](event-hubs-dotnet-standard-getstarted-send.md)</li></ul> |
+| . NET Standard  | [Microsoft.Azure.EventHubs](https://www.nuget.org/packages/Microsoft.Azure.EventHubs/) (**legacy**) | <ul><li>[GitHub location](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/eventhub/Azure.Messaging.EventHubs)</li><li>[Tutorial](event-hubs-dotnet-standard-getstarted-send.md)</li></ul> | 
+|       | [Microsoft.Azure.EventHubs.Processor](https://www.nuget.org/packages/Microsoft.Azure.EventHubs.Processor) (**legacy**) | <ul><li>[GitHub location](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/eventhub/Azure.Messaging.EventHubs.Processor)</li><li>[Tutorial](event-hubs-dotnet-standard-getstarted-send.md)</li></ul> |
 | . NET Framework | [WindowsAzure.Messaging](https://www.nuget.org/packages/WindowsAzure.ServiceBus/) (**legacy**) | |
 |   Java   | [azure-eventhubs](https://search.maven.org/search?q=a:azure-eventhubs) **(legacy)** | <ul><li>[GitHub location](https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/eventhubs/microsoft-azure-eventhubs)</li><li>[Tutorial](event-hubs-java-get-started-send.md)</li></ul> |
 

articles/expressroute/designing-for-disaster-recovery-with-expressroute-privatepeering.md

@@ -105,7 +105,7 @@ The following diagram illustrates influencing ExpressRoute path selection using
 
 :::image type="content" source="./media/designing-for-disaster-recovery-with-expressroute-pvt/aspath.png" alt-text="Diagram of influencing path selection using AS path prepend.":::
 
-If both the connections of ExpressRoute 1 go down, then the virtual network would see the 10.1.11.0/24 route advertisement only via ExpressRoute 2. Consequentially, the longer AS path would become irrelevant. Therefore, the standby circuit would be used in this failure state.
+If both the connections of ExpressRoute 1 go down, then the virtual network would see the 10.1.11.0/24 route advertisement only via ExpressRoute 2. Consequently, the longer AS path would become irrelevant. Therefore, the standby circuit would be used in this failure state.
 
 Using any of the techniques, if you influence Azure to prefer one of your ExpressRoute over others, you also need to ensure the on-premises network also prefer the same ExpressRoute path for Azure bound traffic to avoid asymmetric flows. Typically, local preference value is used to influence on-premises network to prefer one ExpressRoute circuit over others. Local preference is an internal BGP (iBGP) metric. The BGP route with the highest local preference value is preferred.
 

articles/high-performance-computing/lift-and-shift-step-1-networking.md

@@ -12,7 +12,7 @@ ms.subservice: hpc
 
 # Network access configuration
 
-A key aspect of your high performance computing migration is the configuration of network access. Proper network access configration ensures secure, efficient, and uninterrupted communication between computational resources. This part of the guide covers the needs, tools, services, and best practices associated with your network access configuration.
+A key aspect of your high performance computing migration is the configuration of network access. Proper network access configuration ensures secure, efficient, and uninterrupted communication between computational resources. This part of the guide covers the needs, tools, services, and best practices associated with your network access configuration.
 
 It's a common practice in production environments to have resources with private IP addresses, and with rules to define how resources should be accessed.
 

articles/high-performance-computing/lift-and-shift-step-2-identity.md

@@ -12,7 +12,7 @@ ms.subservice: hpc
 
 # Identity management configuration
 
-A key aspect of your high performance computing migration is identity management configuration. Your identity management system ensures secure access to resources, seamless integration, and compliance with organizational policies. It should allow the creation and deltion of users and groups, allow updating and resetting of passwords, and support single sign-on. This part of the guide covers the needs, tools, services, and best practices associated with identity management.
+A key aspect of your high performance computing migration is identity management configuration. Your identity management system ensures secure access to resources, seamless integration, and compliance with organizational policies. It should allow the creation and deletion of users and groups, allow updating and resetting of passwords, and support single sign-on. This part of the guide covers the needs, tools, services, and best practices associated with identity management.
 
 ## Define identity management needs
 

articles/high-performance-computing/lift-and-shift-step-2-job-scheduler.md

@@ -12,7 +12,7 @@ ms.subservice: hpc
 
 # Job scheduler configuration
 
-A key aspect of your high performance computing migration is the configration of job schedulers. Job schedulers are responsible for scheduling user jobs, that is, determining where and when jobs should be executed. In the context of the cloud, job schedulers interact with resource orchestrators to acquire/release resources on-demand, which is different from an on-premises environment where resources are fixed and fully available all the time. This part of the guide covers the needs, tools, services, and best practices associated with your job schedulers.
+A key aspect of your high performance computing migration is the configuration of job schedulers. Job schedulers are responsible for scheduling user jobs, that is, determining where and when jobs should be executed. In the context of the cloud, job schedulers interact with resource orchestrators to acquire/release resources on-demand, which is different from an on-premises environment where resources are fixed and fully available all the time. This part of the guide covers the needs, tools, services, and best practices associated with your job schedulers.
 
 The most common HPC job schedulers are Slurm, OpenPBS, PBSPro, and LSF.