Changes to allow listing pre-requisites

Author: shriram-muthukrishnan

articles/postgresql/migrate/concepts-single-to-flexible.md

@@ -214,21 +214,16 @@ The following table summarizes the list of networking scenarios supported by the
 
 ##### Allow list required extensions
 
-Use the following select command in the Single Server databases to list all the extensions that are being used.
+The migration tool automatically allow lists all extensions used by your single server databases on your flexible server except for the ones whose libraries need to be loaded at the server start. 
+
+Use the following select command on your Single Server databases to list all the extensions that are being used.
 
 ```sql
     select * from pg_extension;
 ```
 
-Search for the **azure.extensions** parameter on the Server Parameters blade on your Flexible server. Select the list of extensions obtained by running the above query on your Single server database to this server parameter and select Save. You should wait for the deployment to complete before proceeding further.
-
-:::image type="content" source="./media/concepts-single-to-flexible/allowlist-extensions.png" alt-text="Diagram that shows allow listing of extensions on Flexible Server." lightbox="./media/concepts-single-to-flexible/allowlist-extensions.png":::
-
-> [!NOTE]  
-> If TIMESCALEDB, POSTGIS_TOPOLOGY, POSTGIS_TIGER_GEOCODER or PG_PARTMAN extensions are used in your single server database, please raise a support request since the Single to Flex migration tool will not handle these extensions.
-
 Check if the list contains any of the following extensions:
-- PG_CRON65
+- PG_CRON
 - PG_HINT_PLAN
 - PG_PARTMAN_BGW
 - PG_PREWARM
@@ -239,16 +234,18 @@ Check if the list contains any of the following extensions:
 
 If yes, then follow the below steps.
 
-Go to the server parameters blade and search for **shared_preload_libraries** parameter. This parameter indicates the set of extension libraries that are preloaded at the server restart. Pg_cron and pg_stat_statements extensions are selected by default. Select the list of above extensions used by the single server database to this parameter and select on Save.
+Go to the server parameters blade and search for **shared_preload_libraries** parameter. Pg_cron and pg_stat_statements extensions are selected by default. Select the list of above extensions used by the single server database to this parameter and select Save.
 
 :::image type="content" source="./media/concepts-single-to-flexible/shared-preload-libraries.png" alt-text="Diagram that shows allow listing of shared preload libraries on Flexible Server." lightbox="./media/concepts-single-to-flexible/shared-preload-libraries.png":::
 
-The changes to this server parameter would require a server restart to come into effect.
+For the changes to take effect, server restart would be required.
 
 :::image type="content" source="./media/concepts-single-to-flexible/save-and-restart.png" alt-text="Diagram that shows save and restart option on Flexible Server." lightbox="./media/concepts-single-to-flexible/save-and-restart.png":::
 
-Use the **Save and Restart** option and wait for the postgresql server to restart.
+Use the **Save and Restart** option and wait for the flexible server to restart.
 
+> [!NOTE]  
+> If TIMESCALEDB, POSTGIS_TOPOLOGY, POSTGIS_TIGER_GEOCODER, POSTGRES_FDW or PG_PARTMAN extensions are used in your single server database, please raise a support request since the migration tool will not be able to migrate these extensions.
 
 ##### Create AAD users on target server
 > [!NOTE]