updating

Author: billmath

articles/active-directory/hybrid/how-to-connect-sso.md

@@ -1,6 +1,6 @@
 ---
-title: 'Azure AD Connect: Seamless Single Sign-On | Microsoft Docs'
-description: This topic describes Azure Active Directory (Azure AD) Seamless Single Sign-On and how it allows you to provide true single sign-on for corporate desktop users inside your corporate network.
+title: 'Azure AD Connect: Seamless single sign-on | Microsoft Docs'
+description: This topic describes Azure Active Directory (Azure AD) Seamless single sign-on and how it allows you to provide true single sign-on for corporate desktop users inside your corporate network.
 services: active-directory
 keywords: what is Azure AD Connect, install Active Directory, required components for Azure AD, SSO, Single Sign-on
 documentationcenter: ''
@@ -16,17 +16,17 @@ ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
 ---
-# Azure Active Directory Seamless Single Sign-On
+# Azure Active Directory Seamless single sign-on
 
-## What is Azure Active Directory Seamless Single Sign-On?
+## What is Azure Active Directory Seamless single sign-on?
 
-Azure Active Directory Seamless Single Sign-On (Azure AD Seamless SSO) automatically signs users in when they are on their corporate devices connected to your corporate network. When enabled, users don't need to type in their passwords to sign in to Azure AD, and usually, even type in their usernames. This feature provides your users easy access to your cloud-based applications without needing any additional on-premises components.
+Azure Active Directory Seamless single sign-on (Azure AD Seamless SSO) automatically signs users in when they are on their corporate devices connected to your corporate network. When enabled, users don't need to type in their passwords to sign in to Azure AD, and usually, even type in their usernames. This feature provides your users easy access to your cloud-based applications without needing any additional on-premises components.
 
 >[!VIDEO https://www.youtube.com/embed/PyeAC85Gm7w]
 
 Seamless SSO can be combined with either the [Password Hash Synchronization](how-to-connect-password-hash-synchronization.md) or [Pass-through Authentication](how-to-connect-pta.md) sign-in methods. Seamless SSO is _not_ applicable to Active Directory Federation Services (ADFS).
 
-![Seamless Single Sign-On](./media/how-to-connect-sso/sso1.png)
+![Seamless single sign-on](./media/how-to-connect-sso/sso1.png)
 
 ## SSO via primary refresh token vs. Seamless SSO
 

articles/active-directory/hybrid/how-to-connect-sync-technical-concepts.md

@@ -55,7 +55,7 @@ Attribute flow occurs between the connector space and the metaverse bi-direction
 Attribute flow only occurs when these synchronizations are run. Attribute flows are defined in Synchronization Rules. These can be inbound (ISR in the picture above) or outbound (OSR in the picture above).
 
 ## Connected system
-Connected system (aka connected directory) is referring to the remote system Azure AD Connect sync has connected to and reading and writing identity data to and from.
+Connected system is referring to the remote system Azure AD Connect sync has connected to and reading and writing identity data to and from.
 
 ## Connector space
 Each connected data source is represented as a filtered subset of the objects and attributes in the connector space.

articles/active-directory/hybrid/plan-connect-design-concepts.md

@@ -175,7 +175,7 @@ While integrating your on-premises directory with Azure AD, it's important to un
 ### Choosing the attribute for userPrincipalName
 When you're selecting the attribute for providing the value of UPN to be used in Azure one should ensure
 
-* The attribute values conform to the UPN syntax (RFC 822), that is it should be of the format username\@domain
+* The attribute values conform to the UPN syntax (RFC 822), it should be in the format of username\@domain
 * The suffix in the values matches to one of the verified custom domains in Azure AD
 
 In express settings, the assumed choice for the attribute is userPrincipalName. If the userPrincipalName attribute doesn't contain the value you want your users to sign in to Azure, then you must choose **Custom Installation**.

articles/active-directory/hybrid/plan-hybrid-identity-design-considerations-identity-adoption-strategy.md

@@ -103,7 +103,7 @@ Over the years, several synchronization tools have existed and used for various
 
 ### Supported topologies
 When defining a synchronization strategy, the topology that is used must be determined. Depending on the information that was determined in step 2 you can determine which topology is the proper one to use. 
-The single forest, single Azure AD topology is the most common and consists of a single Active Directory forest and a single instance of Azure AD.  This topology is going to be used in a most scenarios and is the expected topology when using Azure AD Connect Express installation as shown in the figure below.
+The single forest, single Azure AD topology is the most common and consists of a single Active Directory forest and a single instance of Azure AD.  This topology is going to be used in most scenarios and is the expected topology when using Azure AD Connect Express installation as shown in the figure below.
 
 ![Supported topologies](./media/plan-hybrid-identity-design-considerations/single-forest.png)
 Single Forest Scenario

articles/active-directory/hybrid/plan-hybrid-identity-design-considerations-incident-response-requirements.md

@@ -1,6 +1,6 @@
 ---
 title: Hybrid identity design - incident response requirements Azure | Microsoft Docs
-description: Determine monitoring and reporting capabilities for the hybrid identity solution that can be leveraged by IT to take actions to identify and mitigate a potential threats
+description: Determine monitoring and reporting capabilities for the hybrid identity solution that can be leveraged by IT to take actions to identify and mitigate a potential threat.
 documentationcenter: ''
 services: active-directory
 author: billmath
@@ -39,7 +39,7 @@ Many times the identity system can also help in initial assessment phase mainly
 
 The identity management system should assist IT admins to identify and report those suspicious activities. Usually these technical requirements can be fulfilled by monitoring all systems and having a reporting capability that can highlight potential threats. Use the questions below to help you design your hybrid identity solution while taking into consideration incident response requirements:
 
-* Does your company has a security incident response in place?
+* Does your company have a security incident response in place?
   * If yes, is the current identity management system used as part of the process?
 * Does your company need to identify suspicious sign-on attempts from users across different devices?
 * Does your company need to detect potential compromised user’s credentials?

articles/active-directory/hybrid/tshoot-connect-attribute-not-syncing.md

@@ -29,19 +29,19 @@ Before investigating attribute syncing issues, let’s understand the **Azure AD
 * **CS:** Connector Space, a table in database.
 * **MV:** Metaverse, a table in database.
 * **AD:** Active Directory
-* **AAD:** Azure Active Directory
+* **Azure AD:** Azure Active Directory
 
 ### **Synchronization Steps**
 
 * Import from AD: Active Directory objects are brought into AD CS.
 
-* Import from AAD: Azure Active Directory objects are brought into AAD CS.
+* Import from Azure AD: Azure Active Directory objects are brought into Azure AD CS.
 
 * Synchronization: **Inbound Synchronization Rules** and **Outbound Synchronization Rules** are run in the order of precedence number from lower to higher. To view the Synchronization Rules, you can go to **Synchronization Rules Editor** from the desktop applications. The **Inbound Synchronization Rules** brings in data from CS to MV. The **Outbound Synchronization Rules** moves data from MV to CS.
 
 * Export to AD: After running Synchronization, objects are exported from AD CS to **Active Directory**.
 
-* Export to AAD: After running Synchronization, objects are exported from AAD CS to **Azure Active Directory**.
+* Export to Azure AD: After running Synchronization, objects are exported from Azure AD CS to **Azure Active Directory**.
 
 ### **Step by Step Investigation**