Fix acrolinx and link error

Author: jonels-msft

articles/postgresql/hyperscale/concepts-server-group.md

@@ -59,8 +59,8 @@ applications with the basic tier and later [graduate to the standard
 tier](howto-scale-grow.md#add-worker-nodes) with confidence that the
 interface remains the same.
 
-The basic tier is also appropriate for smaller workloads in production. There
-is room to scale vertically *within* the basic tier by increasing the number of
+The basic tier is also appropriate for smaller workloads in production. There’s
+room to scale vertically *within* the basic tier by increasing the number of
 server vCores.
 
 When greater scale is required right away, use the standard tier. Its smallest
@@ -72,19 +72,19 @@ sizing](howto-scale-initial.md) how-to.
 
 **Basic tier**
 
-* 2 to 8 vCores, 8 to 32 GiB memory.
-* Consists of a single database node which can be scaled vertically.
-* Supports sharding on a single node and can be easily upgraded to a Standard Tier.
+* 2 to 8 vCores, 8 to 32 gigabytes of memory.
+* Consists of a single database node, which can be scaled vertically.
+* Supports sharding on a single node and can be easily upgraded to a standard tier.
 * Economical deployment option for initial development, testing.
 
 **Standard tier**
 
 * 8 to 1000+ vCores, up to 8+ TiB memory
-* Distributed Postgres cluster which consists of a dedicated coordinator
+* Distributed Postgres cluster, which consists of a dedicated coordinator
   node and at least two worker nodes.
 * Supports Sharding on multiple worker nodes. The cluster can be scaled
-  horizontally by adding new worker nodes and scaled vertically by
-  increasing the vCores of the nodes.
+  horizontally by adding new worker nodes, and scaled vertically by
+  increasing the node vCores.
 * Best for performance and scale.
 
 ## Next steps

articles/postgresql/hyperscale/howto-create-users.md

@@ -24,15 +24,15 @@ comes with several roles pre-defined:
 * `citus`
 
 Since Hyperscale (Citus) is a managed PaaS service, only Microsoft can sign in with the
-`postgres` super user role. For limited administrative access, Hyperscale (Citus)
+`postgres` superuser role. For limited administrative access, Hyperscale (Citus)
 provides the `citus` role.
 
 Permissions for the `citus` role:
 
 * Read all configuration variables, even variables normally visible only to
   superusers.
-* Read all pg\_stat\_\* views and use various statistics-related extensions --
-  even views or extensions normally visible only to superusers.
+* Read all pg\_stat\_\* views and use various statistics-related
+  extensions--even views or extensions normally visible only to superusers.
 * Execute monitoring functions that may take ACCESS SHARE locks on tables,
   potentially for a long time.
 * [Create PostgreSQL extensions](concepts-extensions.md) (because
@@ -48,17 +48,18 @@ Notably, the `citus` role has some restrictions:
 As mentioned, the `citus` admin account lacks permission to create additional
 users. To add a user, use the Azure portal interface.
 
-1. Go to the **Roles** page for your Hyperscale (Citus) server group, and click **+ Add**:
+1. Go to the **Roles** page for your Hyperscale (Citus) server group, and
+   select **+ Add**:
 
    :::image type="content" source="../media/howto-hyperscale-create-users/1-role-page.png" alt-text="The roles page":::
 
-2. Enter the role name and password. Click **Save**.
+2. Enter the role name and password. Select **Save**.
 
    :::image type="content" source="../media/howto-hyperscale-create-users/2-add-user-fields.png" alt-text="Add role":::
 
 The user will be created on the coordinator node of the server group,
 and propagated to all the worker nodes. Roles created through the Azure
-portal have the `LOGIN` attribute, which means they are true users who
+portal have the `LOGIN` attribute, which means they’re true users who
 can sign in to the database.
 
 ## How to modify privileges for user role
@@ -76,7 +77,7 @@ GRANT SELECT ON mytable TO db_user;
 
 Hyperscale (Citus) propagates single-table GRANT statements through the entire
 cluster, applying them on all worker nodes. It also propagates GRANTs that are
-system-wide (e.g. for all tables in a schema):
+system-wide (for example, for all tables in a schema):
 
 ```sql
 -- applies to the coordinator node and propagates to workers
@@ -86,7 +87,7 @@ GRANT SELECT ON ALL TABLES IN SCHEMA public TO db_user;
 ## How to delete a user role or change their password
 
 To update a user, visit the **Roles** page for your Hyperscale (Citus) server group,
-and click the ellipses **...** next to the user. The ellipses will open a menu
+and select the ellipses **...** next to the user. The ellipses will open a menu
 to delete the user or reset their password.
 
    :::image type="content" source="../media/howto-hyperscale-create-users/edit-role.png" alt-text="Edit a role":::
@@ -99,7 +100,7 @@ Open the firewall for the IP addresses of the new users' machines to enable
 them to connect: [Create and manage Hyperscale (Citus) firewall rules using
 the Azure portal](howto-manage-firewall-using-portal.md).
 
-For more information about database user account management, see PostgreSQL
+For more information about database user management, see PostgreSQL
 product documentation:
 
 * [Database Roles and Privileges](https://www.postgresql.org/docs/current/static/user-manag.html)

articles/postgresql/hyperscale/quickstart-connect-psql.md

@@ -22,9 +22,9 @@ To follow this quickstart, you'll first need to:
 
 When you create your Azure Database for PostgreSQL server, a default database named **citus** is created. To connect to your database server, you need a connection string and the admin password.
 
-1. Obtain the connection string. In the server group page click the **Connection strings** menu item. (It's under **Settings**.) Find the string marked **psql**. It will be of the form, `psql "host=hostname.postgres.database.azure.com port=5432 dbname=citus user=citus password={your_password} sslmode=require"`
+1. Obtain the connection string. In the server group page, select the **Connection strings** menu item. (It's under **Settings**.) Find the string marked **psql**. It will be of the form, `psql "host=hostname.postgres.database.azure.com port=5432 dbname=citus user=citus password={your_password} sslmode=require"`
 
-   Copy the string. You will need to replace "{your\_password}" with the administrative password you chose earlier. The system doesn't store your plaintext password and so can't display it for you in the connection string.
+   Copy the string. You’ll need to replace "{your\_password}" with the administrative password you chose earlier. The system doesn't store your plaintext password and so can't display it for you in the connection string.
 
 2. Open a terminal window on your local computer.
 

articles/postgresql/hyperscale/quickstart-create-portal.md

@@ -18,11 +18,11 @@ Azure Database for PostgreSQL is a managed service that you use to run, manage,
 
 Azure Database for PostgreSQL - Hyperscale (Citus) is a managed service that
 you use to run, manage, and scale highly available PostgreSQL databases in the
-cloud. Its [basic tier](concepts-server-group.md#tiers) is a a convenient
+cloud. Its [basic tier](concepts-server-group.md#tiers) is a convenient
 deployment option for initial development and testing.
 
 This quickstart shows you how to create a Hyperscale (Citus) basic tier server
-group using the Azure portal. You'll provision the server group and verify that
+group using the Azure portal. You'll create the server group and verify that
 you can connect to it to run queries.
 
 [!INCLUDE [azure-postgresql-hyperscale-create-db](../../../includes/azure-postgresql-hyperscale-create-db.md)]

includes/azure-postgresql-hyperscale-create-db.md

@@ -31,20 +31,21 @@ Follow these steps to create an Azure Database for PostgreSQL server:
    |-------------------|-------------------|
    | Subscription      | The Azure subscription that you want to use for your server. If you have multiple subscriptions, choose the subscription in which you'd like to be billed for the resource. |
    | Resource group    | A new resource group name or an existing one from your subscription. |
-   | Server group name | A unique name that identifies your Hyperscale server group. The domain name postgres.database.azure.com is appended to the server group name you provide. The server can contain only lowercase letters, numbers, and the hyphen (-) character. It must contain less than 40 characters. |
+   | Server group name | A unique name that identifies your Hyperscale server group. The domain name postgres.database.azure.com is appended to the server group name you provide. The server can contain only lowercase letters, numbers, and the hyphen (-) character. It must contain fewer than 40 characters. |
    | Location          | The location that is closest to your users. |
-   | Admin username    | Currently required to be the value "citus", and can't be changed. |
+   | Admin username    | Currently required to be the value `citus`, and can't be changed. |
    | Password          | A new password for the server admin account. It must contain between 8 and 128 characters. Your password must contain characters from three of the following categories: English uppercase letters, English lowercase letters, numbers (0 through 9), and non-alphanumeric characters (!, $, #, %, etc.). |
    | Version           | The latest PostgreSQL major version, unless you have specific requirements. |
    | Compute + storage | The compute, storage, and Tier configurations for your new server. Select **Configure server group**. |
 
    ![compute and storage](./media/azure-postgresql-hyperscale-create-db/compute.png)
 
 5. For the purpose of this quickstart, you can accept the default value of
-   **Basic** for **Tiers**. The other option, standard tier, provisions worker
+   **Basic** for **Tiers**. The other option, standard tier, creates worker
    nodes for greater total data capacity and query parallelism. See
-   [tiers](concepts-server-group.md#tiers) for a more in-depth comparison.
-6. Click **Next : Networking >** at the bottom of the screen.
+   [tiers](../articles/postgresql/hyperscale/concepts-server-group.md#tiers)
+   for a more in-depth comparison.
+6. Select **Next : Networking >** at the bottom of the screen.
 7. In the **Networking** tab, select **Allow public access from Azure services
    and resources within Azure to this server group**. Then select **+ Add
    current client IP address**. 
@@ -58,11 +59,11 @@ Follow these steps to create an Azure Database for PostgreSQL server:
    > to your Hyperscale (Citus) cluster unless your IT department opens port
    > 5432.
 
-8. Select **Review + create** and then **Create** to provision the server.
+8. Select **Review + create** and then **Create** to create the server.
    Provisioning takes a few minutes.
 9. The page will redirect to monitor deployment. When the live status changes
    from **Your deployment is underway** to **Your deployment is complete**,
-   click the **Outputs** menu item on the left of the page.
+   select the **Outputs** menu item on the left of the page.
 10. The outputs page will contain a coordinator hostname with a button next to
    it to copy the value to the clipboard. Record this information for later
    use.