Merge pull request #224067 from schaffererin/aks-best-practices-doc-edits

Quick editing pass

Author: Court72

articles/aks/best-practices.md

@@ -9,19 +9,19 @@ ms.date: 03/09/2021
 
 # Cluster operator and developer best practices to build and manage applications on Azure Kubernetes Service (AKS)
 
-Building and running applications successfully in Azure Kubernetes Service (AKS) require understanding and implementation of some key considerations, including:
+Building and running applications successfully in Azure Kubernetes Service (AKS) requires understanding and implementation of some key concepts, including:
 
 * Multi-tenancy and scheduler features.
 * Cluster and pod security.
 * Business continuity and disaster recovery.
 
-The AKS product group, engineering teams, and field teams (including global black belts [GBBs]) contributed to, wrote, and grouped the following best practices and conceptual articles. Their purpose is to help cluster operators and developers understand the considerations above and implement the appropriate features.
+The AKS product group, engineering teams, and field teams (including global black belts [GBBs]) contributed to, wrote, and grouped the following best practices and conceptual articles. Their purpose is to help cluster operators and developers better understand the concepts above and implement the appropriate features.
 
 ## Cluster operator best practices
 
-As a cluster operator, work together with application owners and developers to understand their needs. You can then use the following best practices to configure your AKS clusters as needed.
+If you're a cluster operator, work with application owners and developers to understand their needs. Then, you can use the following best practices to configure your AKS clusters to fit your needs.
 
-**Multi-tenancy**
+### Multi-tenancy
 
 * [Best practices for cluster isolation](operator-best-practices-cluster-isolation.md)
     * Includes multi-tenancy core components and logical isolation with namespaces.
@@ -32,7 +32,7 @@ As a cluster operator, work together with application owners and developers to u
 * [Best practices for authentication and authorization](operator-best-practices-identity.md)
     * Includes integration with Azure Active Directory, using Kubernetes role-based access control (Kubernetes RBAC), using Azure RBAC, and pod identities.
 
-**Security**
+### Security
 
 * [Best practices for cluster security and upgrades](operator-best-practices-cluster-security.md)
     * Includes securing access to the API server, limiting container access, and managing upgrades and node reboots.
@@ -41,30 +41,30 @@ As a cluster operator, work together with application owners and developers to u
 * [Best practices for pod security](developer-best-practices-pod-security.md)
     * Includes securing access to resources, limiting credential exposure, and using pod identities and digital key vaults.
 
-**Network and storage**
+### Network and storage
 
 * [Best practices for network connectivity](operator-best-practices-network.md)
     * Includes different network models, using ingress and web application firewalls (WAF), and securing node SSH access.
 * [Best practices for storage and backups](operator-best-practices-storage.md)
     * Includes choosing the appropriate storage type and node size, dynamically provisioning volumes, and data backups.
 
-**Running enterprise-ready workloads**
+### Running enterprise-ready workloads
 
 * [Best practices for business continuity and disaster recovery](operator-best-practices-multi-region.md)
     * Includes using region pairs, multiple clusters with Azure Traffic Manager, and geo-replication of container images.
 
 ## Developer best practices
 
-As a developer or application owner, you can simplify your development experience and define require application performance needs.
+If you're a developer or application owner, you can simplify your development experience and define required application performance features.
 
 * [Best practices for application developers to manage resources](developer-best-practices-resource-management.md)
     * Includes defining pod resource requests and limits, configuring development tools, and checking for application issues.
 * [Best practices for pod security](developer-best-practices-pod-security.md)
     * Includes securing access to resources, limiting credential exposure, and using pod identities and digital key vaults.
 
-## Kubernetes / AKS concepts
+## Kubernetes and AKS concepts
 
-To help understand some of the features and components of these best practices, you can also see the following conceptual articles for clusters in Azure Kubernetes Service (AKS):
+The following conceptual articles cover some of the fundamental features and components for clusters in AKS:
 
 * [Kubernetes core concepts](concepts-clusters-workloads.md)
 * [Access and identity](concepts-identity.md)