Fixed link for server parameters

Author: gkasar

articles/reliability/reliability-postgresql-flexible-server.md

@@ -73,7 +73,7 @@ The **zonal** deployment option is available in all [Azure regions](/azure/postg
 - Periodic maintenance activities such as minor version upgrades happen at the standby first and, to reduce downtime, the standby is promoted to primary so that workloads can keep on, while the maintenance tasks are applied on the remaining node.
 
 > [!NOTE]
-> To ensure High-Availability (HA) functions properly, you should configure the `max_replication_slots` and `max_wal_senders` server parameter values. High-Availability requires 4 of each to handle failovers and seamless upgrades. For a HA setup with 5 read replicas and 12 logical replication slots, you should set `max_replication_slots` and `max_wal_senders` both parameter values to 21. This is because each read replica and logical replication slot requires 1 of each, plus the 4 needed for High-Availability to function properly. To learn more about `max_replication_slots` and `max_wal_senders` parameters refer to this [documentation](azure/postgresql/flexible-server/server-parameters-table-replication-sending-servers).
+> To ensure High-Availability (HA) functions properly, you should configure the `max_replication_slots` and `max_wal_senders` server parameter values. High-Availability requires 4 of each to handle failovers and seamless upgrades. For a HA setup with 5 read replicas and 12 logical replication slots, you should set `max_replication_slots` and `max_wal_senders` both parameter values to 21. This is because each read replica and logical replication slot requires 1 of each, plus the 4 needed for High-Availability to function properly. To learn more about `max_replication_slots` and `max_wal_senders` parameters refer to the [documentation](/azure/postgresql/flexible-server/server-parameters-table-replication-sending-servers).
 
 ### Monitor High-Availability Health