Update to Redirect connection policy

The first bullet point for redirect connection policy is missing `SQL` so that it should read `Azure SQL IP addresses` as pointed out by a customer raised issue: https://github.com/MicrosoftDocs/azure-docs/issues/52386

Author: Mike-Ubezzi

articles/sql-database/sql-database-connectivity-architecture.md

@@ -39,7 +39,7 @@ The following steps describe how a connection is established to an Azure SQL dat
 Azure SQL Database supports the following three options for the connection policy setting of a SQL Database server:
 
 - **Redirect (recommended):** Clients establish connections directly to the node hosting the database, leading to reduced latency and improved throughput. For connections to use this mode, clients need to:
-   - Allow outbound communication from the client to all Azure IP addresses in the region on ports in the range of 11000 11999. Use the Service Tags for SQL to make this easier to manage.  
+   - Allow outbound communication from the client to all Azure SQL IP addresses in the region on ports in the range of 11000 11999. Use the Service Tags for SQL to make this easier to manage.  
    - Allow outbound communication from the client to Azure SQL Database gateway IP addresses on port 1433.
 
 - **Proxy:** In this mode, all connections are proxied via the Azure SQL Database gateways,leading to increased latency and reduced throughput. For connections to use this mode, clients need to allow outbound communication from the client to Azure SQL Database gateway IP addresses on port 1433.