Cosmetic changes

Author: kummanish

articles/mariadb/TOC.yml

@@ -138,6 +138,14 @@
       href: howto-auto-grow-storage-portal.md
     - name: Azure CLI
       href: howto-auto-grow-storage-cli.md  
+  - name: Deny Public Network Access
+    items:
+    - name: Azure portal
+      href: howto-deny-public-network-access.md
+  - name: Minimum TLS configuration
+    items:
+    - name: Azure portal
+      href: howto-tls-configurations.md
   - name: Access server logs
     items:
     - name: Slow query logs

articles/mariadb/concepts-data-access-security-private-link.md

@@ -107,7 +107,7 @@ The following situations and outcomes are possible when you use Private Link in
 
 If you want to rely completely only on private endpoints for accessing their Azure Database for MariaDB, you can disable setting all public endpoints ([firewall rules](concepts-firewall-rules.md) and [VNet service endpoints](concepts-data-access-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 MariaDB. When this setting is set to *NO*, clients can connect to your Azure Database for MariaDB based on your firewall or VNet service endpoint settings. Additionally, once the value of the Private network access is set, you cannot add and/or update existing firewall and VNet service endpoint rules.
+When this setting is set to *YES*, only connections via private endpoints are allowed to your Azure Database for MariaDB. When this setting is set to *NO*, clients can connect to your Azure Database for MariaDB based on your firewall or VNet service endpoint settings. Additionally, once the value of the Private network access is set, you cannot add and/or update existing firewall and VNet service endpoint rules.
 
 > [!Note]
 > This feature is available in all Azure regions where Azure Database for PostgreSQL - Single server supports General Purpose and Memory Optimized pricing tiers.

articles/mariadb/howto-deny-public-network-access.md

@@ -22,17 +22,17 @@ To complete this how-to guide, you need:
 
 Follow these steps to set MariaDB server Deny Public Network Access:
 
-* In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MariaDB server.
+1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MariaDB server.
 
-* On the MariaDB server page, under **Settings**, click **Connection security** to open the connection security configuration page.
+1. On the MariaDB server page, under **Settings**, click **Connection security** to open the connection security configuration page.
 
-* In Deny Public Network Access, select **Yes** to enable deny public access for your MariaDB server.
+1. In Deny Public Network Access, select **Yes** to enable deny public access for your MariaDB server.
 
     ![Azure Database for MariaDB Deny network access](./media/howto-deny-public-network-access/deny-public-network-access.PNG)
 
-* Click **Save** to save the changes.
+1. Click **Save** to save the changes.
 
-* A notification will confirm that connection security setting was successfully enabled.
+1. A notification will confirm that connection security setting was successfully enabled.
 
     ![Azure Database for MariaDB Deny network access success](./media/howto-deny-public-network-access/deny-public-network-access-success.png)
 

articles/mariadb/howto-tls-configurations.md

@@ -24,17 +24,17 @@ To complete this how-to guide, you need:
 
 Follow these steps to set MariaDB server minimum TLS version:
 
-* In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MariaDB server.
+1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MariaDB server.
 
-* On the MariaDB server page, under **Settings**, click **Connection security** to open the connection security configuration page.
+1. On the MariaDB server page, under **Settings**, click **Connection security** to open the connection security configuration page.
 
-* In **Minimum TLS version**, select **1.2** to deny connections with TLS version less than TLS 1.2 for your MariaDB server.
+1. In **Minimum TLS version**, select **1.2** to deny connections with TLS version less than TLS 1.2 for your MariaDB server.
 
     ![Azure Database for MariaDB TLS configuration](./media/howto-tls-configurations/tls-configurations.png)
 
-* Click **Save** to save the changes.
+1. Click **Save** to save the changes.
 
-* A notification will confirm that connection security setting was successfully enabled.
+1. A notification will confirm that connection security setting was successfully enabled.
 
     ![Azure Database for MariaDB TLS configuration success](./media/howto-tls-configurations/tls-configurations-success.png)
 

articles/mysql/TOC.yml

@@ -246,6 +246,14 @@
     items:
     - name: Configure Azure AD integration
       href: howto-configure-sign-in-azure-ad-authentication.md
+  - name: Deny Public Network Access
+    items:
+    - name: Azure portal
+      href: howto-deny-public-network-access.md
+  - name: Minimum TLS configuration
+    items:
+    - name: Azure portal
+      href: howto-tls-configurations.md
   - name: Restart server
     items:
     - name: Azure portal

articles/mysql/concepts-data-access-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 MySQL, you can disable setting all public endpoints (i.e. [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 MySQL. When this setting is set to *NO*, clients can connect to your Azure Database for MySQL based on your firewall or VNet service endpoint settings. Additionally, once the value of the Private network access is set, you cannot add and/or update existing firewall and VNet service endpoint rules.
+When this setting is set to *YES*, only connections via private endpoints are allowed to your Azure Database for MySQL. When this setting is set to *NO*, clients can connect to your Azure Database for MySQL based on your firewall or VNet service endpoint settings. Additionally, once the value of the Private network access is set, you cannot add and/or update existing firewall and VNet service endpoint rules.
 
 > [!Note]
 > This feature is available in all Azure regions where Azure Database for PostgreSQL - Single server supports General Purpose and Memory Optimized pricing tiers.

articles/mysql/howto-deny-public-network-access.md

@@ -22,17 +22,17 @@ To complete this how-to guide, you need:
 
 Follow these steps to set MySQL server Deny Public Network Access:
 
-* In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MySQL server.
+1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MySQL server.
 
-* On the MySQL server page, under **Settings**, click **Connection security** to open the connection security configuration page.
+1. On the MySQL server page, under **Settings**, click **Connection security** to open the connection security configuration page.
 
-* In **Deny Public Network Access**, select **Yes** to enable deny public access for your MySQL server.
+1. In **Deny Public Network Access**, select **Yes** to enable deny public access for your MySQL server.
 
     ![Azure Database for MySQL Deny network access](./media/howto-deny-public-network-access/setting-deny-public-network-access.PNG)
 
-* Click **Save** to save the changes.
+1. Click **Save** to save the changes.
 
-* A notification will confirm that connection security setting was successfully enabled.
+1. A notification will confirm that connection security setting was successfully enabled.
 
     ![Azure Database for MySQL Deny network access success](./media/howto-deny-public-network-access/setting-deny-public-network-access-success.png)
 

articles/mysql/howto-tls-configurations.md

@@ -24,17 +24,17 @@ To complete this how-to guide, you need:
 
 Follow these steps to set MySQL server minimum TLS version:
 
-* In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MySQL server.
+1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MySQL server.
 
-* On the MySQL server page, under **Settings**, click **Connection security** to open the connection security configuration page.
+1. On the MySQL server page, under **Settings**, click **Connection security** to open the connection security configuration page.
 
-* In **Minimum TLS version**, select **1.2** to deny connections with TLS version less than TLS 1.2 for your MySQL server.
+1. In **Minimum TLS version**, select **1.2** to deny connections with TLS version less than TLS 1.2 for your MySQL server.
 
     ![Azure Database for MySQL TLS configuration](./media/howto-tls-configurations/setting-tls-value.png)
 
-* Click **Save** to save the changes.
+1. Click **Save** to save the changes.
 
-* A notification will confirm that connection security setting was successfully enabled.
+1. A notification will confirm that connection security setting was successfully enabled.
 
     ![Azure Database for MySQL TLS configuration success](./media/howto-tls-configurations/setting-tls-value-success.png)
 

articles/postgresql/TOC.yml

@@ -273,6 +273,14 @@
         href: howto-restart-server-portal.md
       - name: Azure CLI
         href: howto-restart-server-cli.md
+    - name: Deny Public Network Access
+      items:
+      - name: Azure portal
+        href: howto-deny-public-network-access.md
+    - name: Minimum TLS configuration
+      items:
+      - name: Azure portal
+        href: howto-tls-configurations.md
     - name: Replication
       items:
       - name: Manage read replicas Azure portal

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 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
+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 feature is available in all Azure regions where Azure Database for PostgreSQL - Single server supports General Purpose and Memory Optimized pricing tiers.