fix naming

Author: rachel-msft

articles/mariadb/concepts-firewall-rules.md

@@ -57,7 +57,7 @@ Consider the following points when access to the Microsoft Azure Database for Ma
    * Get static IP addressing instead for your client computers, and then add the IP addresses as firewall rules.
 
 * **Server's IP appears to be public:**
-Connections to the Azure Database for PostgreSQL server are routed through a publicly accessible Azure gateway. However, the actual server IP is not publicly accessible. For more information, visit the [connectivity architecture article](concepts-connectivity-architecture.md). 
+Connections to the Azure Database for MariaDB server are routed through a publicly accessible Azure gateway. However, the actual server IP is protected by the firewall. For more information, visit the [connectivity architecture article](concepts-connectivity-architecture.md). 
 
 ## Next steps
 - [Create and manage Azure Database for MariaDB firewall rules using the Azure portal](./howto-manage-firewall-portal.md)

articles/mysql/concepts-firewall-rules.md

@@ -55,7 +55,7 @@ Consider the following points when access to the Microsoft Azure Database for My
    * Get static IP addressing instead for your client computers, and then add the IP addresses as firewall rules.
 
 * **Server's IP appears to be public:**
-Connections to the Azure Database for PostgreSQL server are routed through a publicly accessible Azure gateway. However, the actual server IP is not publicly accessible. For more information, visit the [connectivity architecture article](concepts-connectivity-architecture.md). 
+Connections to the Azure Database for MySQL server are routed through a publicly accessible Azure gateway. However, the actual server IP is protected by the firewall. For more information, visit the [connectivity architecture article](concepts-connectivity-architecture.md). 
 
 ## Next steps
 

articles/postgresql/concepts-firewall-rules.md

@@ -57,7 +57,7 @@ Consider the following points when access to the Microsoft Azure Database for Po
    * Get static IP addressing instead for your client computers, and then add the static IP address as a firewall rule.
 
 * **Server's IP appears to be public:**
-Connections to the Azure Database for PostgreSQL server are routed through a publicly accessible Azure gateway. However, the actual server IP is not publicly accessible. For more information, visit the [connectivity architecture article](concepts-connectivity-architecture.md). 
+Connections to the Azure Database for PostgreSQL server are routed through a publicly accessible Azure gateway. However, the actual server IP is protected by the firewall. For more information, visit the [connectivity architecture article](concepts-connectivity-architecture.md). 
 
 ## Next steps
 For articles on creating server-level and database-level firewall rules, see: