Standardize capitalization in headings

Author: v-dirichards

articles/load-balancer/load-balancer-best-practices.md

@@ -25,11 +25,11 @@ For each best practice, this article explains:
 
 These best practices are based on a consensus opinion, and Azure platform capability and features sets, as they exist at the time this article was written. 
 
-## Architectural Best Practices
+## Architectural best practices
 
 The following architectural guidance helps ensure the reliability of your Azure Load Balancer deployment. It includes best practices for deploying with zone-redundancy, redundancy in your backend pool, and deploying a global load balancer. Along with reliability for Gateway Load Balancer, which is recommended when using NVAs instead of a dual load balancer set-up.
 
-### Reliability Best Practices
+### Reliability best practices
 
 The following best practices are recommended to ensure the reliability of your Azure Load Balancer deployment.
 
@@ -64,7 +64,7 @@ Chaining your Gateway Load Balancer to a Standard Public Load Balancer is recomm
 
 We recommend using a Gateway load balancer in north-south traffic scenarios with partner Network Virtual Appliances (NVAs). It's easier to deploy because Gateway load balancers don’t require extra configuration such as user-defined routes (UDRs) because it maintains flow stickiness and flow symmetry. It's also easier to manage because NVAs can be easily added and removed. For more information, see the [Gateway Load Balancer documentation](gateway-overview.md).
 
-## Configuration Guidance
+## Configuration guidance
 
 The following configuration guidance are best practices for configuring your Azure Load Balancer deployments. 
 
@@ -101,11 +101,11 @@ Separate your trusted and untrusted traffic on two different tunnel interfaces;
 
 Ensure your NVAs MTU limit is increased to at least 1550, or up to the recommended limit of 4000 for scenarios where jumbo frames are used. Without increasing the MTU limit, you can experience packet drops due to the larger packet size from other packets generated by the VXLAN headers.
 
-## Retirement Announcements
+## Retirement announcements
 
 Along with new improvements and updates to Azure Load Balancer, there are also deprecations to functionalities. It's critical to stay updated and ensure you're making the necessary changes to avoid any potential service disruptions. For a complete list of retirement announcements, see the [Azure Updates page](https://azure.microsoft.com/updates?filters=%5B%22Load+Balancer%22%2C%22Retirements%22%5D) and filter for “Load Balancer” under “Products” and “Retirements” under “Update Type”.
 
-### Use or upgrade to Standard Load Balancer.
+### Use or upgrade to Standard Load Balancer
 
 [Basic Load Balancer will be retired September 30, 2025](https://azure.microsoft.com/updates?id=azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer) and customers should upgrade from Basic Load Balancer to Standard Load Balancer by then. Standard Load Balancer provides significant improvements including high performance, ultra-low latency, security by default, and SLA of 99.99% availability.