Merge pull request #229313 from vimalsmsft/master

Fixed the typo and corrected the information

Author: prmerger-automator[bot]

articles/purview/catalog-firewall.md

@@ -46,7 +46,7 @@ To configure Microsoft Purview firewall follow these steps:
   - Public network access is set to _All networks_ on your Microsoft Purview account's Managed Event Hubs, if it's used. 
 
   > [!NOTE]
-  > Even though the network access is enaled through public internet, to gain access to Microsoft Purview governance portal, users must be first authenticated and authorized. 
+  > Even though the network access is enabled through public internet, to gain access to Microsoft Purview governance portal, users must be first authenticated and authorized. 
 
 - **Disabled for ingestion only (Preview)**
 

articles/purview/catalog-private-link-end-to-end.md

@@ -16,7 +16,7 @@ In this guide, you will learn how to deploy _account_, _portal_ and _ingestion_
 
 The Microsoft Purview _account_ private endpoint is used to add another layer of security by enabling scenarios where only client calls that originate from within the virtual network are allowed to access the Microsoft Purview account. This private endpoint is also a prerequisite for the portal private endpoint.
 
-The Microsoft Purview _compliance portal_ private endpoint is required to enable connectivity to [Microsoft Purview governance portal](https://web.purview.azure.com/resource/) using a private network.
+The Microsoft Purview _portal_ private endpoint is required to enable connectivity to [Microsoft Purview governance portal](https://web.purview.azure.com/resource/) using a private network.
 
 Microsoft Purview can scan data sources in Azure or an on-premises environment by using _ingestion_ private endpoints. Three private endpoint resources are required to be deployed and linked to Microsoft Purview managed or configured resources when ingestion private endpoint is deployed: