consistency fixes

Author: ShawnJackson

articles/active-directory/standards/memo-22-09-enterprise-wide-identity-management-system.md

@@ -59,7 +59,7 @@ Classify assets in terms of:
 - The sensitivity of data that they contain.
 - Laws and regulations that establish specific requirements for confidentiality, integrity, or availability of data/information in each major system and that apply to the system's information protection requirements.
 
-As a part of your application inventory, you need to determine if your current applications use cloud-ready or [legacy authentication protocols](../fundamentals/auth-sync-overview.md):
+As a part of your application inventory, you need to determine if your current applications use cloud-ready protocols or [legacy authentication protocols](../fundamentals/auth-sync-overview.md):
 
 * Cloud-ready applications support modern protocols for authentication, such as SAML, WS-Federation/Trust, OpenID Connect (OIDC), and OAuth 2.0.
 
@@ -95,7 +95,7 @@ For apps that use legacy authentication protocols, consider the following:
 
    *  [Use Azure AD Application Proxy or secure hybrid partner access](../manage-apps/secure-hybrid-access.md) to provide secure access.
 
-*  Decommission access to apps that are no longer needed or that aren't supported (for example, apps added by shadow IT processes). 
+*  Decommission access to apps that are no longer needed or that aren't supported (for example, apps that shadow IT processes added). 
 
 ## Connecting devices
 
@@ -123,7 +123,7 @@ Devices integrated with Azure AD can be either [hybrid joined devices](../device
 
 ## Next steps
 
-The following articles are a part of this documentation set:
+The following articles are part of this documentation set:
 
 [Meet identity requirements of memorandum M-22-09](memo-22-09-meet-identity-requirements.md)
 

articles/active-directory/standards/memo-22-09-meet-identity-requirements.md

@@ -21,9 +21,9 @@ US executive order [14028, Improving the Nation's Cyber Security](https://www.wh
 
 This series of articles offers guidance for employing Azure Active Directory (Azure AD) as a centralized identity management system for implementing Zero Trust principles, as described in memorandum M-22-09. 
 
-The release of memorandum M-22-09 is designed to support Zero Trust initiatives within federal agencies. It also provides regulatory guidance in supporting federal cybersecurity and data privacy paws. The memo cites the [Department of Defense (DoD) Zero Trust Reference Architecture](https://dodcio.defense.gov/Portals/0/Documents/Library/(U)ZT_RA_v1.1(U)_Mar21.pdf), 
+The release of memorandum M-22-09 is designed to support Zero Trust initiatives within federal agencies. It also provides regulatory guidance in supporting federal cybersecurity and data privacy paws. The memo cites the [Department of Defense (DoD) Zero Trust Reference Architecture](https://dodcio.defense.gov/Portals/0/Documents/Library/(U)ZT_RA_v1.1(U)_Mar21.pdf): 
 
-"The foundational tenet of the Zero Trust Model is that no actor, system, network, or service operating outside or within the security perimeter is trusted. Instead, we must verify anything and everything attempting to establish access. It is a dramatic paradigm shift in philosophy of how we secure our infrastructure, networks, and data, from verify once at the perimeter to continual verification of each user, device, application, and transaction."
+>"The foundational tenet of the Zero Trust Model is that no actor, system, network, or service operating outside or within the security perimeter is trusted. Instead, we must verify anything and everything attempting to establish access. It is a dramatic paradigm shift in philosophy of how we secure our infrastructure, networks, and data, from verify once at the perimeter to continual verification of each user, device, application, and transaction."
 
 The memo identifies five core goals that federal agencies must reach. These goals are organized through the Cybersecurity Information Systems Architecture (CISA) Maturity Model. CISA's Zero Trust model describes five complementary areas of effort, or pillars: identity, devices, networks, applications and workloads, and data. These themes cut across these areas: visibility and analytics, automation and orchestration, and governance.
 
@@ -48,7 +48,7 @@ The article series features guidance that encompasses existing agency investment
 
 ## Next steps
 
-The following articles are a part of this documentation set:
+The following articles are part of this documentation set:
 
 [Enterprise-wide identity management systems](memo-22-09-enterprise-wide-identity-management-system.md)
 

articles/active-directory/standards/memo-22-09-multi-factor-authentication.md

@@ -106,7 +106,7 @@ While the memo isn't specific on which policies to use with passwords, consider
 
 ## Next steps
 
-The following articles are a part of this documentation set:
+The following articles are part of this documentation set:
 
 [Meet identity requirements of memorandum M-22-09](memo-22-09-meet-identity-requirements.md)
 

articles/active-directory/standards/memo-22-09-other-areas-zero-trust.md

@@ -90,7 +90,7 @@ After you understand operational governance, you can use [governance features](.
 
 ## Next steps
 
-The following articles are a part of this documentation set:
+The following articles are part of this documentation set:
 
 [Meet identity requirements of memorandum M-22-09](memo-22-09-meet-identity-requirements.md)