Merge pull request #187709 from msmimart/mm-capping

[EXID] Cross-tenant overview minor capping fix

Author: PRMerger20

articles/active-directory/external-identities/cross-tenant-access-overview.md

@@ -54,7 +54,7 @@ You can configure organization-specific settings by adding an organization and m
 ## Important considerations
 
 > [!CAUTION]
-> Changing the default inbound or outbound settings to Block access could block existing business-critical access to apps in your organization or partner organizations. Be sure to use the tools described in this article and consult with your business stakeholders to identify the required access.
+> Changing the default inbound or outbound settings to block access could block existing business-critical access to apps in your organization or partner organizations. Be sure to use the tools described in this article and consult with your business stakeholders to identify the required access.
 
 - Cross-tenant access settings are used to manage B2B collaboration with other Azure AD organizations. For non-Azure AD identities (for example, social identities or non-IT managed external accounts), use [external collaboration settings](external-collaboration-settings-configure.md). External collaboration settings include options for restricting guest user access, specifying who can invite guests, and allowing or blocking domains.