Spelling Fixes

ArieHein · ArieHein · commit bd3536d6903d · 2024-12-08T19:26:04.000+01:00
diff --git a/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-portal.md b/articles/load-balancer/basic/quickstart-basic-internal-load-balancer-portal.md
@@ -235,7 +235,7 @@ These VMs are added to the backend pool of the load balancer that was created ea
     | Setting | VM 2 |
     | ------- | ----- |
     | Name | **myVM2** |
-    | Availability set | Select the existing **myAvailabiltySet** |
+    | Availability set | Select the existing **myAvailabilitySet** |
     | Network security group | Select the existing **myNSG** |
 
 [!INCLUDE [ephemeral-ip-note.md](~/reusable-content/ce-skilling/azure/includes/ephemeral-ip-note.md)]
diff --git a/articles/load-balancer/create-custom-http-health-probe-howto.md b/articles/load-balancer/create-custom-http-health-probe-howto.md
@@ -134,7 +134,7 @@ In this section, you create the load balancer rule that uses the HTTP health pro
     | **Protocol** | Select **TCP** |
     | **Port** | Enter **5000** |
     | **Backend port** | Enter **5000** |
-    | **Health probe** | Select **HTTP_Health (HTTP:5000/health_checkk/)** |
+    | **Health probe** | Select **HTTP_Health (HTTP:5000/health_check/)** |
     | **Session persistence** | Select **None** |
     | **Idle timeout (minutes)** | Enter **5** |
 
diff --git a/articles/load-balancer/inbound-nat-rules.md b/articles/load-balancer/inbound-nat-rules.md
@@ -27,7 +27,7 @@ There are two types of inbound NAT rule available for Azure Load Balancer, versi
 
 ### Inbound NAT rule V1
 
-Inbound NAT rule V1 is defined for a single target virtual machine. Inbound NAT pools are feature of Inbound NAT rules V1 and automatically creates Inbound NAT rules per VMSS intance. The load balancer's frontend IP address and the selected frontend port are used for connections to the virtual machine.
+Inbound NAT rule V1 is defined for a single target virtual machine. Inbound NAT pools are feature of Inbound NAT rules V1 and automatically creates Inbound NAT rules per VMSS instance. The load balancer's frontend IP address and the selected frontend port are used for connections to the virtual machine.
 
 >[!Important]
 > On September 30, 2027, Inbound NAT rules v1 will be retired. If you are currently using Inbound NAT rules v1, make sure to upgrade to  Inbound NAT rules v2 prior to the retirement date.
diff --git a/articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md b/articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md
@@ -105,7 +105,7 @@ Add IPv6 address ranges to the virtual network and subnet hosting the VMs as fol
 
 ```azurepowershell-interactive
 #Add IPv6 ranges to the VNET and subnet
-#Retreive the VNET object
+#Retrieve the VNET object
 $vnet = Get-AzVirtualNetwork  -ResourceGroupName $rg.ResourceGroupName -Name "myVnet" 
 
 #Add IPv6 prefix to the VNET
diff --git a/articles/load-balancer/load-balancer-common-deployment-errors.md b/articles/load-balancer/load-balancer-common-deployment-errors.md
@@ -36,7 +36,7 @@ This article describes some common Azure Load Balancer deployment errors and pro
 | LoadBalancerInUseByVirtualMachineScaleSet | The Load Balancer resource is in use by a Virtual Machine Scale Set and can't be deleted. Use the Azure Resource Manager ID provided in the error message to search for the Virtual Machine Scale Set in order to delete it. | 
 | SpecifiedAllocatedOutboundPortsForOutboundRuleIsNotAMultipleOfEight | The number of specified [SNAT](outbound-rules.md) ports is not a multiply of 8.
 | SpecifiedAllocatedOutboundPortsForOutboundRuleExceedsTotalNumberOfAllowedPortsPerRule | The number of specified [SNAT](outbound-rules.md) ports is greater than 64000.
-| SpecifiedAllocatedOutboundPortsForOutboundRuleExceedsTotalNumberOfAvailablePorts | The number of specified [SNAT](outbound-rules.md) ports is greater than currently avaliable.
+| SpecifiedAllocatedOutboundPortsForOutboundRuleExceedsTotalNumberOfAvailablePorts | The number of specified [SNAT](outbound-rules.md) ports is greater than currently available.
 
 ## Next steps
 
diff --git a/articles/load-balancer/load-balancer-manage-health-status.md b/articles/load-balancer/load-balancer-manage-health-status.md
@@ -37,7 +37,7 @@ The following table describes the success reason codes where the backend state i
 
 | **Reason Code** | **Portal displayed reason** | **Description** |
 |-------------|-------------------------|-------------|
-| **Up_Probe_Succes**s | The backend instance is responding to health probe successfully. | Your backend instance is responding to the health probe successfully. |
+| **Up_Probe_Success** | The backend instance is responding to health probe successfully. | Your backend instance is responding to the health probe successfully. |
 | **Up_Probe_AllDownIsUp** | The backend instance is considered healthy due to enablement of *NoHealthyBackendsBehavior*. | Health probe state of the backend instance is ignored because *NoHealthyBackendsBehavior* is enabled. The backend instance is considered healthy and can receive traffic. |
 | **Up_Probe_ApproachingUnhealthyThreshold** | Health probe is approaching an unhealthy threshold but backend instance remains healthy based on last response. | The most recent probe has failed to respond but the backend instance remains healthy enough based on earlier responses. |
 | **Up_Admin**| The backend instance is healthy due to Admin State set to *Up*. | Health probe state of the backend instance is ignored because the Admin State is set to *UP*. The backend instance is considered healthy and can receive traffic. |
@@ -97,7 +97,7 @@ Health status can be retrieved on a per load balancing rule basis. This is suppo
 To retrieve the health status information via REST API, you need to do a two request process.
 
 > [!NOTE]
-> Using the REST API method requres that you have a **Bearer access token** for autorization. For assistance retrieving the access token, see [Get-AzAccessToken](/powershell/module/az.accounts/get-azaccesstoken) for details.
+> Using the REST API method requires that you have a **Bearer access token** for authorization. For assistance retrieving the access token, see [Get-AzAccessToken](/powershell/module/az.accounts/get-azaccesstoken) for details.
 
 1. Use the following POST request to obtain the Location URI from the Response Headers.
 
diff --git a/articles/load-balancer/load-balancer-monitor-metrics-cli.md b/articles/load-balancer/load-balancer-monitor-metrics-cli.md
@@ -19,7 +19,7 @@ Complete reference documentation and other samples for retrieving metrics using
 
 ## Table of metric names via CLI
 
-When you use CLI, Load Balancer metrics may use a different metric name for the CLI parameter value. When specifying the metric name via the `--metric dimension` parameter, use the CLI metric name instead. For example, the metric Data path availability would be used by specifying a parameter of `--metric VipAvaialbility`.
+When you use CLI, Load Balancer metrics may use a different metric name for the CLI parameter value. When specifying the metric name via the `--metric dimension` parameter, use the CLI metric name instead. For example, the metric Data path availability would be used by specifying a parameter of `--metric VipAvailability`.
 
 Here's a table of common Load Balancer metrics, the CLI metric name, and recommend aggregation values for queries:
 
diff --git a/articles/load-balancer/load-balancer-nat-pool-migration.md b/articles/load-balancer/load-balancer-nat-pool-migration.md
@@ -18,7 +18,7 @@ An [inbound NAT rule](inbound-nat-rules.md) is used to forward traffic from a lo
 
 ## NAT rule version 1 
 
-[Version 1](inbound-nat-rules.md) is the legacy approach for assigning an Azure Load Balancer’s frontend port to each backend instance. Rules are applied to the backend instance’s network interface card (NIC). For Azure Virtual Machine Scale Sets (VMSS) instances, inbound NAT rules are automatically created/deleted as new instances are scaled up/down. For VMSS instanes use the `Inbound NAT Pools` property to manage Inbound NAT rules version 1. 
+[Version 1](inbound-nat-rules.md) is the legacy approach for assigning an Azure Load Balancer’s frontend port to each backend instance. Rules are applied to the backend instance’s network interface card (NIC). For Azure Virtual Machine Scale Sets (VMSS) instances, inbound NAT rules are automatically created/deleted as new instances are scaled up/down. For VMSS instances use the `Inbound NAT Pools` property to manage Inbound NAT rules version 1. 
 
 ## NAT rule version 2 
 
diff --git a/articles/load-balancer/load-balancer-outbound-connections.md b/articles/load-balancer/load-balancer-outbound-connections.md
@@ -89,7 +89,7 @@ A public IP assigned to a VM is a 1:1 relationship (rather than 1: many) and imp
 In Azure, virtual machines created in a virtual network without explicit outbound connectivity defined are assigned a default outbound public IP address. This IP address enables outbound connectivity from the resources to the Internet. This access is referred to as [default outbound access](../virtual-network/ip-services/default-outbound-access.md).  This method of access is **not recommended** as it's insecure and the IP addresses are subject to change.
 
 >[!Important]
->On September 30, 2025, default outbound access for new deployments will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired/).  It is recommended to use one the explict forms of connectivity as shown in options 1-3 above.
+>On September 30, 2025, default outbound access for new deployments will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired/).  It is recommended to use one the explicit forms of connectivity as shown in options 1-3 above.
 
 ### What are SNAT ports?
 
diff --git a/articles/load-balancer/manage-admin-state-how-to.md b/articles/load-balancer/manage-admin-state-how-to.md
@@ -367,7 +367,7 @@ In this section, you learn how to remove an existing admin state from an existin
 # [Azure PowerShell](#tab/azurepowershell)
 
 1. Connect to your Azure subscription with Azure PowerShell.
-2. Remove an existing backend pool instance. This is done by setting the admin state value to **NONE** with [New-AzLoadBlancerBackendAddressConfig](/powershell/module/az.network/new-azloadbalancerbackendaddressconfig). Replace the values in brackets with the names of the resources in your configuration.
+2. Remove an existing backend pool instance. This is done by setting the admin state value to **NONE** with [New-AzLoadBalancerBackendAddressConfig](/powershell/module/az.network/new-azloadbalancerbackendaddressconfig). Replace the values in brackets with the names of the resources in your configuration.
 
     ```azurepowershell
     
diff --git a/articles/load-balancer/manage.md b/articles/load-balancer/manage.md
@@ -361,7 +361,7 @@ If you want to add an outbound rule to your load balancer, go to your load balan
 | Available Frontend ports | Displayed value of total available frontend ports based on selected port allocation. |
 | Maximum number of backend instances | Enter the maximum number of back end instances. This entry is only available when choosing **Maximum number of backend instances** for outbound ports above. </br> You can't scale your backend pool above this number of instances. Increasing the number of instances decreases the number of ports per instance unless you also add more frontend IP addresses. |
 
-:::image type="content" source="./media/manage/outbound-rule.png" alt-text="Screehshot of add outbound rule." border="true":::
+:::image type="content" source="./media/manage/outbound-rule.png" alt-text="Screenshot of add outbound rule." border="true":::
 
 ## Next Steps
 
diff --git a/articles/load-balancer/quickstart-load-balancer-standard-internal-terraform.md b/articles/load-balancer/quickstart-load-balancer-standard-internal-terraform.md
@@ -322,7 +322,7 @@ This quickstart shows you how to deploy a standard internal load balancer and tw
    variable "password" {
      type = string
      default = "Microsoft@123"
-     description = "The passoword for the local account that will be created on the new VM."
+     description = "The password for the local account that will be created on the new VM."
    }
    
    variable "virtual_network_name" {
diff --git a/articles/load-balancer/quickstart-load-balancer-standard-public-terraform.md b/articles/load-balancer/quickstart-load-balancer-standard-public-terraform.md
@@ -270,7 +270,7 @@ This quickstart shows you how to deploy a standard load balancer to load balance
     variable "password" {
       type        = string
       default     = "Microsoft@123"
-      description = "The passoword for the local account that will be created on the new VM."
+      description = "The password for the local account that will be created on the new VM."
     }
     
     variable "virtual_network_name" {
diff --git a/articles/load-balancer/tutorial-load-balancer-ip-backend-portal.md b/articles/load-balancer/tutorial-load-balancer-ip-backend-portal.md
@@ -252,7 +252,7 @@ These VMs are added to the backend pool of the load balancer that was created ea
     | Availability zone | Select **Zone 1** |
     | Image | Select **Windows Server 2022 Datacenter: Azure Edition - x64 Gen2** |
     | Azure Spot instance | Leave the default |
-    | Size | Select **Standar_DS1_v2** or another image size. |
+    | Size | Select **Standard_DS1_v2** or another image size. |
     | **Administrator account** |  |
     | Username | Enter a username |
     | Password | Enter a password |
