acrolinx improvement on 2 files

Author: markingmyname

articles/postgresql/flexible-server/concepts-server-parameters.md

@@ -17,7 +17,7 @@ Azure Database for PostgreSQL provides a subset of configurable parameters for e
 
 ## An overview of PostgreSQL parameters 
 
-Azure Database for PostgreSQL server is pre-configured with optimal default values for each parameter on creation. Static parameters require a server restart and parameters that require superuser access cannot be configured by the user. 
+Azure Database for PostgreSQL server is pre-configured with optimal default values for each parameter on creation. Static parameters require a server restart and parameters that require superuser access can't be configured by the user. 
 
 In order to review which parameters are available to view or to modify, we recommend going into the Azure portal, and to the Server Parameters page. You can also configure parameters on a per-user or per-database basis using `ALTER DATABASE` or `ALTER ROLE` commands.
 
@@ -26,20 +26,20 @@ In order to review which parameters are available to view or to modify, we recom
 
 :::image type="content" source="./media/concepts-server-parameters/server-parameters.png" alt-text="Server parameters - portal":::
 
-Here is the list of some of the parameters:
+Here's the list of some of the parameters:
 
 
    | Parameter Name             | Description |
 |----------------------|--------|
-| **max_connections** | You can tune max_connections on Postgres Flexible Server, where it can be set to 5,000 connections. Please see the [limits documentation](concepts-limits.md) for more details. | 
-| **shared_buffers**    | The 'shared_buffers' setting changes depending on the selected SKU (SKU determines the memory available). General Purpose servers have 2GB shared_buffers for 2 vCores; Memory Optimized servers have 4GB shared_buffers for 2 vCores. The shared_buffers setting scales linearly (approximately) as vCores increase in a tier. | 
-| **shared_preload_libraries** | This parameter is available for configuration with a predefined set of supported extensions. Note that we always load the `azure` extension (used for maintenance tasks), as well as the `pg_stat_statements` extension (you can use the pg_stat_statements.track parameter to control whether the extension is active). |
+| **max_connections** | You can tune max_connections on Postgres Flexible Server, where it can be set to 5,000 connections. See the [limits documentation](concepts-limits.md) for more details. | 
+| **shared_buffers**    | The 'shared_buffers' setting changes depending on the selected SKU (SKU determines the memory available). General Purpose servers have 2 GB shared_buffers for 2 vCores; Memory Optimized servers have 4 GB shared_buffers for 2 vCores. The shared_buffers setting scales linearly (approximately) as vCores increase in a tier. | 
+| **shared_preload_libraries** | This parameter is available for configuration with a predefined set of supported extensions. We always load the `azure` extension (used for maintenance tasks), and the `pg_stat_statements` extension (you can use the pg_stat_statements.track parameter to control whether the extension is active). |
 | **connection_throttling** | You can enable or disable temporary connection throttling per IP for too many invalid password login failures. |
- | **work_mem** | This parameter specifies the amount of memory to be used by internal sort operations and hash tables before writing to temporary disk files. If your workload has few queries with a lot of complex sorting and you have a lot of available memory, increasing this parameter may allow Postgres to do larger scans in-memory vs. spilling to disk, which will be faster.  Be careful however, as one complex query may have number of sort, hash operations running concurrently. Each one of those operations will use as much memory as it value allows before it starts writing to disk based temporary files. Therefore on a relatively busy system total memory usage will be many times of individual work_mem parameter. If you do decide to tune this value globally, you can use formula Total RAM * 0.25 / max_connections as initial value. Azure Database for PostgreSQL - Flexible Server supports range of 4096-2097152 kilobytes for this parameter.|
+ | **work_mem** | This parameter specifies the amount of memory to be used by internal sort operations and hash tables before writing to temporary disk files. If your workload has few queries with many complex sorting and you have a lot of available memories, increasing this parameter may allow Postgres to do larger scans in-memory vs. spilling to disk, which will be faster.  Be careful however, as one complex query may have number of sort, hash operations running concurrently. Each one of those operations will use as much memory as it value allows before it starts writing to disk based temporary files. Therefore on a relatively busy system total memory usage will be many times of individual work_mem parameter. If you do decide to tune this value globally, you can use formula Total RAM * 0.25 / max_connections as initial value. Azure Database for PostgreSQL - Flexible Server supports range of 4096-2097152 kilobytes for this parameter.|
 | **effective_cache_size** |The effective_cache_size parameter estimates how much memory is available for disk caching by the operating system and within the database itself. The PostgreSQL query planner decides whether it’s fixed in RAM or not. Index scans are most likely to be used against higher values; otherwise, sequential scans will be used if the value is low. Recommendations are to set Effective_cache_size at 50% of the machine’s total RAM. |
 | **maintenance_work_mem** | The maintenance_work_mem parameter basically provides the maximum amount of memory to be used by maintenance operations like vacuum, create index, and alter table add foreign key operations.  Default value for that parameter is 64 KB. It’s recommended to set this value higher than work_mem; this can improve performance for vacuuming. |
 | **effective_io_concurrency** | Sets the number of concurrent disk I/O operations that PostgreSQL expects can be executed simultaneously. Raising this value will increase the number of I/O operations that any individual PostgreSQL session attempts to initiate in parallel. The allowed range is 1 to 1000, or zero to disable issuance of asynchronous I/O requests. Currently, this setting only affects bitmap heap scans.. |
- |**require_secure_transport** | If your application does not support SSL connectivity to the server, you can optionally disable secured transport from your client by turning `OFF` this parameter value. |
+ |**require_secure_transport** | If your application doesn't support SSL connectivity to the server, you can optionally disable secured transport from your client by turning `OFF` this parameter value. |
  |**log_connections** | This parameter may be read-only, as on Azure Database for PostgreSQL - Flexible Server all connections are logged and intercepted to make sure connections are coming in from right sources for security reasons. |
 
 >[!NOTE]

articles/postgresql/flexible-server/connect-azure-cli.md

@@ -22,8 +22,8 @@ This quickstart demonstrates how to connect to an Azure Database for PostgreSQL
 ## Prerequisites
 - An Azure account. If you don't have one, [get a free trial](https://azure.microsoft.com/free/).
 - Install [Azure CLI](/cli/azure/install-azure-cli) latest version (2.20.0 or above)
-- Login using Azure CLI with ```az login``` command 
-- Turn on parameter persistence with ```az config param-persist on```. Parameter persistence will help you use local context without having to repeat a lot of arguments like resource group or location.
+- Log in using Azure CLI with ```az login``` command 
+- Turn on parameter persistence with ```az config param-persist on```. Parameter persistence will help you use local context without having to repeat numerous arguments like resource group or location.
 
 ## Create a PostgreSQL Flexible Server
 
@@ -32,7 +32,7 @@ The first thing we'll create is a managed PostgreSQL server. In [Azure Cloud She
 ```azurecli
 az postgres flexible-server create --public-access <your-ip-address>
 ```
-You can provide additional arguments for this command to customize it. See all arguments for [az postgres flexible-server create](/cli/azure/postgres/flexible-server#az-postgres-flexible-server-create).
+You can provide more arguments for this command to customize it. See all arguments for [az postgres flexible-server create](/cli/azure/postgres/flexible-server#az-postgres-flexible-server-create).
 
 ## View all the arguments
 You can view all the arguments for this command with ```--help``` argument. 
@@ -51,7 +51,7 @@ az postgres flexible-server connect -n <servername> -u <username> -p "<password>
 ```azurecli
 az postgres flexible-server connect -n postgresdemoserver -u dbuser -p "dbpassword" -d postgres
 ```
-You will see the output if the connection was successful.
+You'll see the output if the connection was successful.
 ```output
 Command group 'postgres flexible-server' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
 Successfully connected to postgresdemoserver.
@@ -63,10 +63,10 @@ If the connection failed, try these solutions:
 - Check if port 5432 is open on your client machine.
 - if your server administrator user name and password are correct
 - if you have configured firewall rule for your client machine
-- if you have configured your server with private access in virtual networking, make sure your client machine is in the same virtual network.
+- if you've configured your server with private access in virtual networking, make sure your client machine is in the same virtual network.
 
 ## Run multiple queries using interactive mode
-You can run multiple queries using the **interactive** mode . To enable interactive mode, run the following command
+You can run multiple queries using the **interactive** mode. To enable interactive mode, run the following command
 
 ```azurecli
 az postgres flexible-server connect -n <servername> -u <username> -p "<password>" -d <databasename>
@@ -78,7 +78,7 @@ az postgres flexible-server connect -n <servername> -u <username> -p "<password>
 az postgres flexible-server connect -n postgresdemoserver -u dbuser -p "dbpassword" -d flexibleserverdb --interactive
 ```
 
-You will see the **psql** shell experience as shown below:
+You'll see the **psql** shell experience as shown below:
 
 ```bash
 Command group 'postgres flexible-server' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
@@ -101,7 +101,7 @@ Your preference of  are now saved to local context. To learn more, type in `az l
 az postgres flexible-server execute -n postgresdemoserver -u dbuser -p "dbpassword" -d flexibleserverdb -q "select * from table1;" --output table
 ```
 
-You will see an output as shown below:
+You'll see an output as shown below:
 
 ```output
 Command group 'postgres flexible-server' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
@@ -134,7 +134,7 @@ az postgres flexible-server execute -n <server-name> -u <username> -p "<password
 az postgres flexible-server execute -n postgresdemoserver -u dbuser -p "dbpassword" -d flexibleserverdb -f "./test.sql"
 ```
 
-You will see an output as shown below:
+You'll see an output as shown below:
 
 ```output
 Command group 'postgres flexible-server' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus