Merge pull request #270213 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/aks/best-practices-cost.md

@@ -12,7 +12,7 @@ Cost optimization is about maximizing the value of resources while minimizing un
 
 In this article, you learn about:
 > [!div class="checklist"]
-> * Strategic infrastucture selection
+> * Strategic infrastructure selection
 > * Dynamic rightsizing and autoscaling
 > * Leveraging Azure discounts for substantial savings
 > * Holistic monitoring and FinOps practices 

articles/aks/use-network-policies.md

@@ -96,7 +96,7 @@ To use Azure Network Policy Manager, you must use the Azure CNI plug-in. Calico
 
 The following example script creates an AKS cluster with system-assigned identity and enables network policy by using Azure Network Policy Manager.
 
->[!Note}
+>[!NOTE]
 > Calico can be used with either the `--network-plugin azure` or `--network-plugin kubenet` parameters.
 
 Instead of using a system-assigned identity, you can also use a user-assigned identity. For more information, see [Use managed identities](use-managed-identity.md).

articles/azure-vmware/vulnerability-management.md

@@ -7,7 +7,6 @@ ms.date: 3/22/2024
 ms.custom: engagement-fy24
 ---
 
-
 # How Azure VMware Solution Addresses Vulnerabilities in the Infrastructure
 
 At a high level, Azure VMware Solution is a Microsoft Azure service and therefore must follow all the same policies and requirements that Azure follows. Azure policies and procedures dictate that Azure VMware Solution must follow the [SDL](https://www.microsoft.com/securityengineering/sdl) and must meet several regulatory requirements as promised by Microsoft Azure. 
@@ -22,16 +21,17 @@ Azure VMware Solution takes a defense in depth approach to vulnerability and ris
 - Details within the signal are adjudicated and assigned a CVSS score and risk rating according to compensating controls within the service.
 - The risk rating is used against internal bug bars, internal policies and regulations to establish a timeline for implementing a fix.
 - Internal engineering teams partner with appropriate parties to qualify and roll out any fixes, patches and other configuration updates necessary.
-- Communications are drafted when necassary and published according to the risk rating assigned.
->[!tip]
->Communications are surfaced through [Azure Service Health Portal](/azure/service-health/service-health-portal-update), [Known Issues](/azure/azure-vmware/azure-vmware-solution-known-issues) or Email. 
+- Communications are drafted when necessary and published according to the risk rating assigned.
+
+> [!TIP]
+> Communications are surfaced through [Azure Service Health Portal](/azure/service-health/service-health-portal-update), [Known Issues](/azure/azure-vmware/azure-vmware-solution-known-issues) or Email. 
 
 ### Subset of regulations governing vulnerability and risk management
 
 Azure VMware Solution is in scope for the following certifications and regulatory requirements. The regulations listed aren't a complete list of certifications Azure VMware Solution holds, rather it's a list with specific requirements around vulnerability management. These regulations don't rely on other regulations for the same purpose. IE, certain regional certifications may point to ISO requirements for vulnerability management.
 
->[!NOTE]
->To access the following audit reports hosted in the Service Trust Portal, you must be an active Microsoft customer.
+> [!NOTE]
+> To access the following audit reports hosted in the Service Trust Portal, you must be an active Microsoft customer.
 
 - [ISO](https://servicetrust.microsoft.com/DocumentPage/38a05a38-6181-432e-a5ec-aa86008c56c9)
 - [PCI](https://servicetrust.microsoft.com/viewpage/PCI) \- See the packages for DSS and 3DS for Audit Information.

articles/baremetal-infrastructure/workloads/nc2-on-azure/solution-design.md

@@ -19,7 +19,7 @@ The following table describes the network topologies supported by each network f
 
 |Topology |Supported |
 | :------------------- |:---------------:|
-|Connectivity to BareMetal Infrasturcture (BMI) in a local VNet| Yes |
+|Connectivity to BareMetal Infrastructure (BMI) in a local VNet| Yes |
 |Connectivity to BMI in a peered VNet (Same region)|Yes |
 |Connectivity to BMI in a peered VNet\* (Cross region or global peering) with VWAN\*|Yes |
 |Connectivity to BM in a peered VNet* (Cross region or global peering)* without VWAN| No|

articles/frontdoor/standard-premium/how-to-add-custom-domain.md

@@ -100,7 +100,7 @@ After you validate your custom domain, you can associate it to your Azure Front
 
     > [!NOTE]
     > * If HTTPS is enabled, certificate provisioning and propagation may take a few minutes because propagation is being done to all edge locations.
-    > * If your domain CNAME is indirectly pointed to a Front Door endpoint, for example, using Azure Traffic Manager for multi-CDN failover, the **DNS state** column shows as **CNAME/Alias record currently not detected**. Azure Front Door can't guarantee 100% detection of the CNAME record in this case. If you've configured an Azure Front Door endpoint to Azure Traffic Manager and still see this message, it doesn’t mean you didn't set up correctly, therefore further no action is neccessary from your side.
+    > * If your domain CNAME is indirectly pointed to a Front Door endpoint, for example, using Azure Traffic Manager for multi-CDN failover, the **DNS state** column shows as **CNAME/Alias record currently not detected**. Azure Front Door can't guarantee 100% detection of the CNAME record in this case. If you've configured an Azure Front Door endpoint to Azure Traffic Manager and still see this message, it doesn’t mean you didn't set up correctly, therefore further no action is necessary from your side.
 
 ## Verify the custom domain
 

articles/service-fabric/service-fabric-best-practices-capacity-scaling.md

@@ -31,7 +31,7 @@ Using automatic scaling through virtual machine scale sets will make your versio
    The minimum capacity for autoscaling rules must be equal to or greater than five virtual machine instances. It must also be equal to or greater than your Reliability Tier minimum for your primary node type.
 
 > [!NOTE]
-> The Service Fabric stateful service fabric:/System/InfastructureService/<NODE_TYPE_NAME> runs on every node type that has Silver or higher durability. It's the only system service that is supported to run in Azure on any of your clusters node types.
+> The Service Fabric stateful service fabric:/System/InfrastructureService/<NODE_TYPE_NAME> runs on every node type that has Silver or higher durability. It's the only system service that is supported to run in Azure on any of your clusters node types.
 
 > [!IMPORTANT]
 > Service Fabric autoscaling supports `Default` and `NewestVM` virtual machine scale set [scale-in configurations](../virtual-machine-scale-sets/virtual-machine-scale-sets-scale-in-policy.md).

articles/virtual-machines/TOC.yml

@@ -2108,7 +2108,7 @@
 - name: Infrastructure automation
   items:
   - name: Overview
-    displayName: Infrastrucure automation overview
+    displayName: Infrastructure automation overview
     href: infrastructure-automation.md
   - name: User data
     href: user-data.md

articles/virtual-machines/nva10v5-series.md

@@ -43,7 +43,7 @@ Each virtual machine instance in NVadsA10v5-series comes with a GRID license. Th
 
 <sup>1</sup> NVadsA10v5-series VMs feature AMD Simultaneous multithreading Technology
 
-<sup>2</sup> The actual GPU VRAM reported in the operating system will be little less due to Error Correcting Code (ECC) support.
+<sup>2</sup> The actual GPU VRAM reported in the operating system will be a little less due to Error Correcting Code (ECC) support.