Addressing the review comments

Author: shriram-muthukrishnan

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

@@ -184,7 +184,7 @@ The following table summarizes the list of networking scenarios supported by the
 * If your single server is public access (case #1 and case #2 in the above table), there's nothing needed from your end. The single to flex migration tool automatically establishes connection between single and flexible server and the migration will go through.
 * If your single server is in private access, then the only supported scenario is when your Flexible server is inside a VNet. If your flexible server is deployed in the same VNet as the private end point of your Single server, connections between single server and flexible server should automatically work provided there is no network security group(NSGs) blocking the connectivity between subnets. If flexible server is deployed in another VNet, [peering should be established between the VNets](../../virtual-network/tutorial-connect-virtual-networks-portal.md) for the connection to work between Single and Flexible server.  
 
-##### Allowlist required extensions
+##### Allow list required extensions
 Use the following select command in the Single Server databases to list all the extensions that are being used.
 
 ```