Merge pull request #102300 from rachel-msft/edit124

Update concepts-read-replicas.md

Author: PRMerger15

articles/postgresql/concepts-read-replicas.md

@@ -5,7 +5,7 @@ author: rachel-msft
 ms.author: raagyema
 ms.service: postgresql
 ms.topic: conceptual
-ms.date: 12/03/2019
+ms.date: 01/23/2020
 ---
 
 # Read replicas in Azure Database for PostgreSQL - Single Server
@@ -54,8 +54,6 @@ There are limitations to consider:
 
 
 ## Create a replica
-The master server must have the `azure.replication_support` parameter set to **REPLICA**. When this parameter is changed, a server restart is required for the change to take effect. (The `azure.replication_support` parameter applies to the General Purpose and Memory Optimized tiers only).
-
 When you start the create replica workflow, a blank Azure Database for PostgreSQL server is created. The new server is filled with the data that was on the master server. The creation time depends on the amount of data on the master and the time since the last weekly full backup. The time can range from a few minutes to several hours.
 
 Every replica is enabled for storage [auto-grow](concepts-pricing-tiers.md#storage-auto-grow). The auto-grow feature allows the replica to keep up with the data replicated to it, and prevent a break in replication caused by out of storage errors.

articles/postgresql/howto-read-replicas-cli.md

@@ -33,8 +33,8 @@ The `azure.replication_support` parameter must be set to **REPLICA** on the mast
    ```
 
 > [!NOTE]
-> If you get the error "Invalid value given" while trying to set azure.replication_support from the Azure CLI, it is likely your server already has REPLICA set by default. A bug is preventing this setting from being correctly reflected on newer servers where REPLICA is the internal default.
-> You can skip the prepare master steps and go to create the replica.
+> If you get the error "Invalid value given" while trying to set azure.replication_support from the Azure CLI, it is likely your server already has REPLICA set by default. A bug is preventing this setting from being correctly reflected on newer servers where REPLICA is the internal default. <br><br>
+> You can skip the prepare master steps and go to create the replica. <br><br>
 > If you would like to confirm your server is in this category, visit the server's replication page in the Azure portal. "Disable replication" will be grayed out and "Add Replica" will be active in the toolbar.
 
 2. Restart the server to apply the change.

articles/postgresql/howto-read-replicas-portal.md

@@ -5,7 +5,7 @@ author: rachel-msft
 ms.author: raagyema
 ms.service: postgresql
 ms.topic: conceptual
-ms.date: 09/04/2019
+ms.date: 01/24/2020
 ---
 
 # Create and manage read replicas in Azure Database for PostgreSQL - Single Server from the Azure portal
@@ -23,6 +23,9 @@ These steps must be used to prepare a master server in the General Purpose or Me
 
 2. On the server sidebar, under **SETTINGS**, select **Replication**.
 
+> [!NOTE] 
+> If you see **Disable replication support** grayed out, the replication settings are already set on your server by default. You can skip the following steps and go to create a read replica. 
+
 3. Select **Enable Replication Support**. 
 
    ![Enable replication support](./media/howto-read-replicas-portal/enable-replication-support.png)