Fix numbering in ResourceDeploymentFailure instructions (#23)

* Fix numbering in ResourceDeploymentFailure instructions

Corrected the numbering in the ResourceDeploymentFailure section for clarity.

* Update load balancer distribution mode documentation

Author: v-regandowner

articles/load-balancer/load-balancer-common-deployment-errors.md

@@ -31,7 +31,7 @@ This article describes some common Azure Load Balancer deployment errors and pro
 |VMScaleSetCannotUseMultipleLoadBalancersOfSameType| You can't have multiple Load Balancers of the same type (internal, public). You can have a maximum of one internal and one public Load Balancer. |
 |VMScaleSetCannotReferenceLoadbalancerWhenLargeScaleOrCrossAZ | Basic Load Balancer isn't supported for multiple-placement group Virtual Machine Scale Sets or cross-availability zone Virtual Machine Scale Set. Use Standard Load Balancer instead. |
 |MarketplacePurchaseEligibilityFailed | Switch to the correct Administrative account to enable purchases due to subscription being an EA Subscription. You can read more [here](../marketplace/marketplace-faq-publisher-guide.yml#what-could-block-a-customer-from-completing-a-purchase-). |
-|ResourceDeploymentFailure| If your load balancer is in a failed state, follow these steps to bring it back from the failed state:<br>1. Go to https://resources.azure.com, and sign in with your Azure portal credentials.<br>1. Select **Read/Write**.<br>1. On the left, expand **Subscriptions**, and then expand the Subscription with the Load Balancer to update.<br>1. Expand **ResourceGroups**, and then expand the resource group with the Load Balancer to update.<br>1. Select **Microsoft.Network** > **LoadBalancers**, and then select the Load Balancer to update, **LoadBalancer_1**.<br>1. On the display page for **LoadBalancer_1**, select **GET** > **Edit**.<br>1. Update the **ProvisioningState** value from **Failed** to **Succeeded**.<br>1. Select **PUT**.|
+|ResourceDeploymentFailure| If your load balancer is in a failed state, follow these steps to bring it back from the failed state:<br>1. Go to https://resources.azure.com, and sign in with your Azure portal credentials.<br>2. Select **Read/Write**.<br>3. On the left, expand **Subscriptions**, and then expand the Subscription with the Load Balancer to update.<br>4. Expand **ResourceGroups**, and then expand the resource group with the Load Balancer to update.<br>5. Select **Microsoft.Network** > **LoadBalancers**, and then select the Load Balancer to update, **LoadBalancer_1**.<br>6. On the display page for **LoadBalancer_1**, select **GET** > **Edit**.<br>7. Update the **ProvisioningState** value from **Failed** to **Succeeded**.<br>8. Select **PUT**.|
 |LoadBalancerWithoutFrontendIPCantHaveChildResources | A Load Balancer resource that has no frontend IP configurations, can't have associated child resources or components associated to it. In order to mitigate this error, add a frontend IP configuration and then add the resources you're trying to add. |
 | LoadBalancerRuleCountLimitReachedForNic | A backend pool member's network interface (virtual machine, Virtual Machine Scale Set) can't be associated to more than 300 rules. Reduce the number of rules or use another Load Balancer. This limit is documented on the [Load Balancer limits page](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer).
 | 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. | 
@@ -42,4 +42,4 @@ This article describes some common Azure Load Balancer deployment errors and pro
 ## Next steps
 
 * Look through the Azure Load Balancer [SKU comparison table](./skus.md)
-* Learn about [Azure Load Balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer)
+* Learn about [Azure Load Balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer)

articles/load-balancer/load-balancer-distribution-mode.md

@@ -40,11 +40,11 @@ You can change the configuration of the distribution mode by modifying the load-
 1. In the load-balancing rules screen, select the load-balancing rule that you wish to change the distribution mode.
 1. Under the rule, the distribution mode is changed by changing the **Session persistence** drop-down box. 
 
-The following options are available: 
-
-* **None (hash-based)** - Specifies that successive requests from the same client can be handled by any virtual machine.
-* **Client IP (two-tuple: source IP and destination IP)** - Specifies that successive requests from the same client IP address are handled by the same virtual machine.
-* **Client IP and protocol (three-tuple: source IP, destination IP, and protocol type)** - Specifies that successive requests from the same client IP address and protocol combination are handled by the same virtual machine.
+   The following options are available: 
+  
+   * **None (hash-based)** - Specifies that successive requests from the same client can be handled by any virtual machine.
+   * **Client IP (two-tuple: source IP and destination IP)** - Specifies that successive requests from the same client IP address are handled by the same virtual machine.
+   * **Client IP and protocol (three-tuple: source IP, destination IP, and protocol type)** - Specifies that successive requests from the same client IP address and protocol combination are handled by the same virtual machine.
 
 1. Choose the distribution mode and then select **Save**.
 
@@ -98,3 +98,4 @@ For more information on the command used in this article, see [az network lb rul
 * [Azure Load Balancer overview](load-balancer-overview.md)
 * [Get started with configuring an internet-facing load balancer](quickstart-load-balancer-standard-public-powershell.md)
 * [Configure idle TCP timeout settings for your load balancer](load-balancer-tcp-idle-timeout.md)
+