Add clarification about read replicas of source server not being created on restored server

Author: nachoalonsoportillo

articles/postgresql/flexible-server/concepts-backup-restore.md

@@ -161,15 +161,17 @@ After you restore the database, you can perform the following tasks to get your
 
 - If the new server is meant to replace the original server, redirect clients and client applications to the new server. Change the server name of your connection string to point to the new server.
 
-- Ensure that appropriate server-level firewall, private endpoints and virtual network rules are in place for user connections. In *public access* network, rules are copied over from the original server, but those might not ne the ones required in the restored environment. So, adjust them as per your requirements. Private endpoints are not carried over. Create any private endpoints you may need in the restored server. In *private access* virtual network, the restore doesn't copy over any network infrastructure artifacts from source to restored server networks. Anything related to configuration of VNET, subnets, or Network Security Groups, must be taken care of as a post-restore task.
+- Ensure that appropriate server-level firewall, private endpoints and virtual network rules are in place for user connections. In *public access* network, rules are copied over from the original server, but those might not be the ones required in the restored environment. So, adjust them as per your requirements. Private endpoints are not carried over. Create any private endpoints you may need in the restored server. In *private access* virtual network, the restore doesn't copy over any network infrastructure artifacts from source to restored server networks. Anything related to configuration of VNET, subnets, or Network Security Groups, must be taken care of as a post-restore task.
 
 - Scale up or scale down the restored server's compute as needed.
 
 - Ensure that appropriate logins and database-level permissions are in place.
 
 - Configure alerts as appropriate.
 
-- If you restored the database configured with high availability, and if you want to configure the restored server with high availability, you can then follow [the steps](./how-to-manage-high-availability-portal.md).
+- If the source server from which you restored was configured with high availability, and you want to configure the restored server with high availability, you can then follow [these steps](./how-to-manage-high-availability-portal.md).
+
+- If the source server from which you restored was configured with read replicase, and you want to configure read replicas on the restored server, you can then follow [these steps](./how-to-read-replicas-portal.md).
 
 ## Long-term retention (preview)