Updates per Review - Increased acrlinx and fixed

Author: mbender-ms

articles/load-balancer/components.md

@@ -49,9 +49,9 @@ A health probe is used to determine the health status of the instances in the ba
 
 You can define the unhealthy threshold for your health probes. When a probe fails to respond, the load balancer stops sending new connections to the unhealthy instances. A probe failure doesn't affect existing connections. The connection continues until the application:
 
-1. Ends the flow
-1. Idle timeout occurs
-1. The VM shuts down
+- Ends the flow
+- Idle timeout occurs
+- The VM shuts down
 
 Load balancer provides different health probe types for endpoints: TCP, HTTP, and HTTPS. [Learn more about Load Balancer Health probes](load-balancer-custom-probe-overview.md).
 
@@ -73,11 +73,11 @@ A load balancer rule configured with **'protocol - all and port - 0'** is known
 
 The load-balancing decision is made per flow. This action is based on the following five-tuple connection: 
 
-1. source IP address
-1. source port
-1. destination IP address
-1. destination port
-1. protocol
+- source IP address
+- source port
+- destination IP address
+- destination port
+- protocol
 
 The HA ports load-balancing rules help you with critical scenarios, such as high availability and scale for network virtual appliances (NVAs) inside virtual networks. The feature can help when a large number of ports must be load-balanced.
 
@@ -109,13 +109,13 @@ Basic load balancer doesn't support outbound rules.
 
 ## Limitations
 
-1. Learn about load balancer [limits](../azure-resource-manager/management/azure-subscription-service-limits.md) 
-1. Load balancer provides load balancing and port forwarding for specific TCP or UDP protocols. Load-balancing rules and inbound NAT rules support TCP and UDP, but not other IP protocols including ICMP.
-1. Load Balancer backend pool can't consist of a [Private Endpoint](../private-link/private-endpoint-overview.md).
-1. Outbound flow from a backend VM to a frontend of an internal Load Balancer will fail.
-1. A load balancer rule can't span two virtual networks. All load balancer frontends and their backend instances must be in a single virtual network. 
-1. Forwarding IP fragments isn't supported on load-balancing rules. IP fragmentation of UDP and TCP packets isn't supported on load-balancing rules. 
-1. You can only have one Public Load Balancer (NIC based) and one internal Load Balancer (NIC based) per availability set. However, this constraint doesn't apply to IP-based load balancers. 
+- Learn about load balancer [limits](../azure-resource-manager/management/azure-subscription-service-limits.md) 
+- Load balancer provides load balancing and port forwarding for specific TCP or UDP protocols. Load-balancing rules and inbound NAT rules support TCP and UDP, but not other IP protocols including ICMP.
+- Load Balancer backend pool can't consist of a [Private Endpoint](../private-link/private-endpoint-overview.md).
+- Outbound flow from a backend VM to a frontend of an internal Load Balancer will fail.
+- A load balancer rule can't span two virtual networks. All load balancer frontends and their backend instances must be in a single virtual network. 
+- Forwarding IP fragments isn't supported on load-balancing rules. IP fragmentation of UDP and TCP packets isn't supported on load-balancing rules. 
+- You can only have one Public Load Balancer (NIC based) and one internal Load Balancer (NIC based) per availability set. However, this constraint doesn't apply to IP-based load balancers. 
 
 ## Next step
 

articles/load-balancer/concepts.md

@@ -25,11 +25,11 @@ By default, Azure Load Balancer uses a five-tuple hash.
 
 The five-tuple includes:
 
-1. **Source IP address**
-1. **Source port**
-1. **Destination IP address**
-1. **Destination port**
-1. **IP protocol number to map flows to available servers**
+- **Source IP address**
+- **Source port**
+- **Destination IP address**
+- **Destination port**
+- **IP protocol number to map flows to available servers**
 
 You can also use session affinity [distribution mode](distribution-mode-concepts.md) which uses two-tuple or three-tuple based load balancing.
 
@@ -42,9 +42,9 @@ A response to an inbound flow is always a response from a virtual machine. When
 
 ## Next steps
 
-1. Learn more about [Azure Load Balancer](load-balancer-overview.md).
-1. Learn about the [components](components.md) that make up Azure Load Balancer.
-1. Learn about [Health Probes](load-balancer-custom-probe-overview.md).
-1. Learn about Azure Load Balancer's traffic [distribution modes](distribution-mode-concepts.md)
-1. See [Create a public Standard Load Balancer](quickstart-load-balancer-standard-public-portal.md) to get started with using a Load Balancer: create one, create VMs with a custom IIS extension installed, and load balance the web app between the VMs.
-1. Learn about [Azure Load Balancer outbound connections](load-balancer-outbound-connections.md).
+- Learn more about [Azure Load Balancer](load-balancer-overview.md).
+- Learn about the [components](components.md) that make up Azure Load Balancer.
+- Learn about [Health Probes](load-balancer-custom-probe-overview.md).
+- Learn about Azure Load Balancer's traffic [distribution modes](distribution-mode-concepts.md)
+- See [Create a public Standard Load Balancer](quickstart-load-balancer-standard-public-portal.md) to get started with using a Load Balancer: create one, create VMs with a custom IIS extension installed, and load balance the web app between the VMs.
+- Learn about [Azure Load Balancer outbound connections](load-balancer-outbound-connections.md).

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

@@ -28,11 +28,11 @@ There's no downtime when switching from one distribution mode to another on a lo
 Azure Load Balancer uses a five-tuple hash based distribution mode by default.  
 
 The five-tuple consists of:
-1. **Source IP**
-1. **Source port**
-1. **Destination IP**
-1. **Destination port**
-1. **Protocol type**
+- **Source IP**
+- **Source port**
+- **Destination IP**
+- **Destination port**
+- **Protocol type**
 
 The hash is used to route traffic to healthy backend instances within the backend pool. The algorithm provides stickiness only within a transport session. When the client starts a new session from the same source IP, the source port changes and causes the traffic to go to a different backend instance.
 
@@ -47,21 +47,21 @@ Session persistence is also known session affinity, source IP affinity, or clien
 
 Session persistence mode has two configuration types:
 
-* **Client IP (2-tuple)** - Specifies that successive requests from the same client IP address are handled by the same backend instance.
-* **Client IP and protocol (3-tuple)** - Specifies that successive requests from the same client IP address and protocol combination are handled by the same backend instance.
+- **Client IP (2-tuple)** - Specifies that successive requests from the same client IP address are handled by the same backend instance.
 
-The following figure illustrates a two-tuple configuration. Notice how the two-tuple runs through the load balancer to virtual machine 1 (VM1). VM1 is backed up by VM2 and VM3.
+- **Client IP and protocol (3-tuple)** - Specifies that successive requests from the same client IP address and protocol combination are handled by the same backend instance.
 
-:::image type="content" source="./media/load-balancer-distribution-mode/load-balancer-session-affinity.png" alt-text="Screenshot of two-tuple session affinity distribution mode diagram showing traffic routing through load balancer to virtual machines.":::
+The following figure illustrates a two-tuple configuration. Notice how the two-tuple runs through the load balancer to virtual machine 1 (VM1). VM1 is backed up by VM2 and VM3.
 
+:::image type="content" source="./media/load-balancer-distribution-mode/load-balancer-session-affinity.png" alt-text="Screenshot of two-tuple session affinity distribution mode diagram showing traffic routing through load balancer to virtual machines.">:::
 ## Use cases
 
 Source IP affinity with client IP and protocol (source IP affinity three-tuple), solves an incompatibility between Azure Load Balancer and Remote Desktop Gateway (RD Gateway). 
 
 Another use case scenario is media upload. The data upload happens through UDP, but the control plane is achieved through TCP:
 
-1. A client starts a TCP session to the load-balanced public address and is directed to a specific DIP. The channel is left active to monitor the connection health.
-1. A new UDP session from the same client computer is started to the same load-balanced public endpoint. The connection is directed to the same DIP endpoint as the previous TCP connection. The media upload can be executed at high throughput while maintaining a control channel through TCP.
+- A client starts a TCP session to the load-balanced public address and is directed to a specific DIP. The channel is left active to monitor the connection health.
+- A new UDP session from the same client computer is started to the same load-balanced public endpoint. The connection is directed to the same DIP endpoint as the previous TCP connection. The media upload can be executed at high throughput while maintaining a control channel through TCP.
 
 > [!NOTE]
 > When Load Balancer backend pool members change either by removing or adding a virtual machine, the distribution of client requests is recomputed. You can't depend on new connections from existing clients to end up at the same server. Additionally, using source IP affinity distribution mode can cause an uneven distribution of traffic. Clients that run behind proxies might be seen as one unique client application.