updates

Author: rwike77

articles/active-directory/develop/publisher-verification-overview.md

@@ -1,6 +1,6 @@
 ---
 title: Publisher verification overview
-description: An overview of publisher verification for Microsoft identity platform.
+description: Provides an overview of the publisher verification program for the Microsoft identity platform. Lists the benefits, program requirements, and frequently asked questions.
 services: active-directory
 author: rwike77
 manager: CelesteDG
@@ -16,26 +16,26 @@ ms.reviewer: jesakowi
 
 # Publisher verification
 
-Publisher verification allows developers with a verified (or “vetted”) Microsoft Partner Center (MPN) account to mark one or more app registrations as publisher verified.   
+Publisher verification allows developers to add a verified organizational identity to apps registered through Azure Active Directory (AAD). Verification is done by associating one or more apps with a Microsoft Partner Center (MPN) account.   
 
 This feature is primarily targeted at developers building multi-tenant apps that leverage [OAuth 2.0 and OpenID Connect](active-directory-v2-protocols.md) with the [Microsoft identity platform](v2-overview.md). These apps can sign users in using OpenID Connect, or they may use OAuth to request access to data using APIs like [Microsoft Graph](https://developer.microsoft.com/graph/).
 
 ## Benefits
 Publisher verification provides the following benefits:
-- Transparency and risk reduction for customers- this capability helps customers understand which apps being used in their organizations are published by developers they trust. 
+- **Increased transparency and risk reduction for customers**- this capability helps customers understand which apps being used in their organizations are published by developers they trust. 
 
-- UX differentiation- a “verified” badge will appear on the Azure AD [consent prompt](application-consent-experience.md), Enterprise Apps page, and additional UX surfaces used by end-users and admins. 
+- **Improved branding**- a “verified” badge appears on the Azure AD [consent prompt](application-consent-experience.md), Enterprise Apps page, and additional UX surfaces used by end-users and admins. 
 
-- Smoother enterprise adoption- admins will soon be able to configure new User Consent Policies, and publisher verification status will be one of the primary policy criteria. 
+- **Smoother enterprise adoption**- admins can configure new User Consent Policies, and publisher verification status will be one of the primary policy criteria. 
 
-- Risk evaluation- Microsoft’s detections for “risky” consent requests will include publisher verification as a signal. 
+- **Improved risk evaluation**- Microsoft’s detections for “risky” consent requests will include publisher verification as a signal. 
 
 ## Requirements
 There are a few pre-requisites for publisher verification, some of which will have already been completed by many Microsoft partners. They are: 
 
 1. An MPN ID for a valid [Microsoft Partner Network](https://partner.microsoft.com/membership) account that has completed the [verification](/partner-center/verification-responses) process. This MPN account must be the [Partner global account (PGA)](/partner-center/account-structure#the-top-level-is-the-partner-global-account-pga) for your organization. 
 
-1. An Azure AD tenant with a DNS-verified [custom domain](/azure/active-directory/fundamentals/add-custom-domain), which must match the domain of the email address used during verification in the previous step. 
+1. An Azure AD tenant with a DNS-verified [custom domain](/azure/active-directory/fundamentals/add-custom-domain). The custom domain must match the domain of the email address used during verification in the previous step. 
 
 1. An app registered in an Azure AD tenant, with a [Publisher Domain](howto-configure-publisher-domain.md) configured using the same domain as previously used. 
 
@@ -45,17 +45,17 @@ There are a few pre-requisites for publisher verification, some of which will ha
 
   1. In Partner Center this user must have of the following [roles](/partner-center/permissions-overview): MPN Admin, Accounts Admin, or a Global Admin (this is a shared role mastered in Azure AD). 
 
-Developers who have already met these pre-requisites can get verified in a matter of minutes. If they have not been met, getting set up is free. 
+Developers who have already met these pre-requisites can get verified in a matter of minutes. If the requiremets have not been met, getting set up is free. 
 
 If you cannot currently meet these requirements, or don’t know if you can, you can still participate in the private preview! We want to hear your feedback and help you understand how you can satisfy these requirements. 
 
 ## Frequently Asked Questions 
 
-- **When will the verified badge start showing up on the consent screen?** Admins and end-users will be able to see the badge even during the Private Preview phase. Users who get prompted to consent to your app will start seeing the badge soon after you have gone through the process successfully, although it may take some time for this to replicate throughout the system. This will generally be a few minutes but could be a few hours. 
+- **When will the verified badge start showing up on the consent screen?** Users who get prompted to consent to your app see the badge soon after you've gone through the process successfully, although it may take some time for this to replicate throughout the system. This will generally be a few minutes but could be a few hours. 
 
 - **When will other experiences start showing the badge or using verification status?**  
 
-  - The Enterprise Apps experience will start showing an indication of publisher verified apps by Public Preview in mid-May. Admins will be able to set policies using this information in a similar timeframe. 
+  - The Enterprise Apps experience will start showing an indication of publisher verified apps by public preview in mid-May. Admins will be able to set policies using this information in a similar timeframe. 
 
   - Dates on additional UI surfaces have not been announced. 
 
@@ -104,7 +104,7 @@ When an application is marked publisher verified this does not indicate whether
 
 Publisher verification is performed on an application-by- application basis so a publisher must verify each application where they would like a publisher verification badge to appear.   
 
-For a publisher to mark an app as publisher verified, the following requirements must be met: 
+The following requirements must be met for a publisher to mark an app as publisher verified: 
 
 1. The publisher must have a valid [Microsoft Partner Network account](https://partner.microsoft.com/membership).  
 
@@ -126,7 +126,7 @@ For a publisher to mark an app as publisher verified, the following requirements
 
   1. In Azure AD this user must either be the owner of the app or have one of the following [roles](/azure/active-directory/users-groups-roles/directory-assign-admin-roles): application admin, cloud application admin, global admin. 
 
-  1. In Partner Center this user must have one of the following [roles](/partner-center/permissions-overview): MPN admin, accounts admin, or a global admin (this is a shared role mastered in Azure AD). 
+  1. In Partner Center this user must have one of the following [roles](/partner-center/permissions-overview): MPN admin, accounts admin, or a global admin (a shared role mastered in Azure AD). 
 
 ## Additional resources
 Microsoft identity platform & Azure AD 

articles/active-directory/develop/troubleshoot-publisher-verification.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot publisher verification 
-description: Describles how to troubleshoot publisher verification for Microsoft identity platform.
+description: Describes how to troubleshoot publisher verification for Microsoft identity platform by calling Microsoft Graph APIs.
 services: active-directory
 author: rwike77
 manager: CelesteDG