Minor edits for PostgreSQL file

kummanish · kummanish · commit 8f7e444825d5 · 2020-03-12T16:29:16.000-07:00
diff --git a/articles/postgresql/concepts-data-access-and-security-private-link.md b/articles/postgresql/concepts-data-access-and-security-private-link.md
@@ -106,7 +106,7 @@ The following situations and outcomes are possible when you use Private Link in
 
 If you want to rely only on private endpoints for accessing their Azure Database for PostgreSQL Single server, you can disable setting all public endpoints([firewall rules](concepts-firewall-rules.md) and [VNet service endpoints](concepts-data-access-and-security-vnet.md)) by setting the **Deny Public Network Access** configuration on the database server. 
 
-When this setting is set to *YES* only connections via private endpoints are allowed to your Azure Database for PostgreSQL. When this setting is set to *NO* clients can connect to your Azure Database for MariaDB based on your firewall or VNet service endpoint setting.￼ Additionally, once the value of the Private network access is set to  customers cannot add ￼and/or update ￼existing ‘Firewall rules’ and ‘VNet service endpoint rule
+When this setting is set to *YES* only connections via private endpoints are allowed to your Azure Database for PostgreSQL. When this setting is set to *NO* clients can connect to your Azure Database for PostgreSQL based on your firewall or VNet service endpoint setting.￼ Additionally, once the value of the Private network access is set to  customers cannot add ￼and/or update ￼existing ‘Firewall rules’ and ‘VNet service endpoint rule
 
 > [!Note]
 > This setting does not have any impact on the SSL and TLS configurations for your Azure Database for PostgreSQL Single server.

-Original file line number
+Diff line change
 If you want to rely only on private endpoints for accessing their Azure Database for PostgreSQL Single server, you can disable setting all public endpoints([firewall rules](concepts-firewall-rules.md) and [VNet service endpoints](concepts-data-access-and-security-vnet.md)) by setting the **Deny Public Network Access** configuration on the database server.
 -When this setting is set to *YES* only connections via private endpoints are allowed to your Azure Database for PostgreSQL. When this setting is set to *NO* clients can connect to your Azure Database for MariaDB based on your firewall or VNet service endpoint setting. Additionally, once the value of the Private network access is set to  customers cannot add and/or update existing ‘Firewall rules’ and ‘VNet service endpoint rule
 +When this setting is set to *YES* only connections via private endpoints are allowed to your Azure Database for PostgreSQL. When this setting is set to *NO* clients can connect to your Azure Database for PostgreSQL based on your firewall or VNet service endpoint setting. Additionally, once the value of the Private network access is set to  customers cannot add and/or update existing ‘Firewall rules’ and ‘VNet service endpoint rule
 > [!Note]
 > This setting does not have any impact on the SSL and TLS configurations for your Azure Database for PostgreSQL Single server.