Final updates for first publish docs

Author: schaffererin

articles/aks/best-practices-performance-scale-large.md

@@ -85,7 +85,7 @@ Always upgrade your Kubernetes clusters to the latest version. Newer versions co
 As you scale your AKS clusters to larger scale points, keep the following feature limitations in mind:
 
 * AKS supports up to a 1,000 node scale in an AKS cluster by default. While AKS doesn't prevent you from scaling further, doing so might result in degraded performance. If you want to scale beyond 1,000 nodes, you can request a limit increase. For more information, see [Best practices for creating and running AKS clusters at scale][run-aks-at-scale].
-* [Azure Network Policy Manager (Azure NPM)][azure-npm] only supports up to 250 nodes.
+* [Azure Network Policy Manager (Azure npm)][azure-npm] only supports up to 250 nodes.
 * You can't use the Stop and Start feature with clusters that have more than 100 nodes. For more information, see [Stop and start an AKS cluster](./start-stop-cluster.md).
 
 ## Networking
@@ -96,7 +96,7 @@ As you scale your AKS clusters to larger scale points, keep the following networ
 * Use Azure CNI Overlay to scale up to 200,000 pods and 5,000 nodes per cluster. For more information, see [Configure Azure CNI Overlay networking in AKS][azure-cni-overlay].
 * If your application needs direct pod-to-pod communication across clusters, use Azure CNI with dynamic IP allocation and scale up to 50,000 application pods per cluster with one routable IP per pod. For more information, see [Configure Azure CNI networking for dynamic IP allocation in AKS][azure-cni-dynamic-ip].
 * When using internal Kubernetes services behind an internal load balancer, we recommend creating an internal load balancer or service below a 750 node scale for optimal scaling performance and load balancer elasticity.
-* Azure NPM only supports up to 250 nodes. If you want to enforce network policies for larger clusters, consider using [Azure CNI powered by Cilium](./azure-cni-powered-by-cilium.md), which combines the robust control plane of Azure CNI with the Cilium data plane to provide high performance networking and security.
+* Azure npm only supports up to 250 nodes. If you want to enforce network policies for larger clusters, consider using [Azure CNI powered by Cilium](./azure-cni-powered-by-cilium.md), which combines the robust control plane of Azure CNI with the Cilium data plane to provide high performance networking and security.
 
 ## Node pool scaling
 

articles/aks/best-practices-performance-scale.md

@@ -177,22 +177,22 @@ Be mindful of the fact that watching too many mutable resources or making too ma
 
 To avoid potential issues and ensure the stability of the Kubernetes control plane, you can use the following strategies:
 
-**1. Resource quotas**
+**Resource quotas**
 
 Implement resource quotas to limit the number of resources that can be listed or watched by a particular user or namespace to prevent excessive calls.
 
-**2. API Priority and Fairness**
+**API Priority and Fairness**
 
 Kubernetes introduced the concept of API Priority and Fairness (APF) to prioritize and manage API requests. You can use APF in Kubernetes to protect the cluster's API server and reduce the number of `HTTP 429 Too Many Requests` responses seen by client applications.
 
 | Custom resource | Key features |
 | -------------------- | ------------ |
 | PriorityLevelConfigurations | • Define different priority levels for API requests.<br/> • Specifies a unique name and assigns an integer value representing the priority level. Higher priority levels have lower integer values, indicating they're more critical.<br/> • Can use multiple to categorize requests into different priority levels based on their importance.<br/> • Allow you to specify whether requests at a particular priority level should be subject to rate limits. |
-| FlowSchemas | • Define how API requests should be routed to different priority levels based on request attributes.<br/> • Specify rules that match requests based on criteria like API groups, versions, and resources.<br/> • When a requests matches a given rule, the request is directed to the priority level specified in the associated PriorityLevelConfiguration.<br/> • Can use to set the order of evaluation when multiple FlowSchemas match a request to ensure that certain rules take precedence. |
+| FlowSchemas | • Define how API requests should be routed to different priority levels based on request attributes.<br/> • Specify rules that match requests based on criteria like API groups, versions, and resources.<br/> • When a request matches a given rule, the request is directed to the priority level specified in the associated PriorityLevelConfiguration.<br/> • Can use to set the order of evaluation when multiple FlowSchemas match a request to ensure that certain rules take precedence. |
 
 Configuring API with PriorityLevelConfigurations and FlowSchemas enables the prioritization of critical API requests over less important requests. This ensures that essential operations don't starve or experience delays because of lower priority requests.
 
-**3. Optimize labeling and selectors**
+**Optimize labeling and selectors**
 
 When using LIST operations, optimize label selectors to narrow down the scope of the resources you want to query to reduce the amount of data returned and the load on the API server.