Update secure-external-access-resources.md

Author: v-edmckillop

articles/active-directory/fundamentals/secure-external-access-resources.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: fundamentals
 ms.topic: conceptual
-ms.date: 12/16/2022
+ms.date: 12/21/2022
 ms.author: gasinh
 ms.reviewer: ajburnle
 ms.custom: "it-pro, seodec18"
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
 
 # Plan an Azure Active Directory B2B collaboration deployment
 
-Secure collaboration with your external partners ensures they have correct access to internal resources, and for the expected duration. This articles covers governance practices to reduce security risks, meet compliance goals, and ensure accurate access.
+Secure collaboration with your external partners ensures they have correct access to internal resources, and for the expected duration. Learn about governance practices to reduce security risks, meet compliance goals, and ensure accurate access.
 
 Governed collaboration improves clarity of ownership of access, reduces exposure of sensitive resources, and enables you to attest to access policy.
 
@@ -30,7 +30,7 @@ Traditionally, organizations use one of two methods to collaborate:
 * Create locally managed credentials for external users, or
 * Establish federations with partner identity providers (IdP)
 
-Both methods have drawbacks. See the following table for more information.
+Both methods have drawbacks. For more information, see the following table.
 
 | Area of concern | Local credentials | Federation |
 |----|---|---|
@@ -48,15 +48,15 @@ Azure AD B2B benefits:
 - Collaborate with users who have an email address, but no infrastructure
 - IT departments don't connect out-of-band to set up access or federation
 - Guest user access is protected by the same security processes as internal users
-- Clear end-user experience with no additional credentials required
-- User collaborate with partners without IT department involvement
-- Guest default permissions in the Azure AD directory are not limited or highly restricted
+- Clear end-user experience with no extra credentials required
+- Users collaborate with partners without IT department involvement
+- Guest default permissions in the Azure AD directory aren't limited or highly restricted
 
 ## Next steps
 
 * [Determine your security posture for external access](1-secure-access-posture.md)
 * [Discover the current state of external collaboration in your organization](2-secure-access-current-state.md)
-* [CCreate a security plan for external access](3-secure-access-plan.md)
+* [Create a security plan for external access](3-secure-access-plan.md)
 * [Securing external access with groups](4-secure-access-groups.md)
 * [Transition to governed collaboration with Azure Active Directory B2B collaboration](5-secure-access-b2b.md)
 * [Manage external access with entitlement management](6-secure-access-entitlement-managment.md)