Merge branch 'Fix-Vale-issues-for-(/administration/postgresql/standalone.md)-#332393' into 'master'

documentation: Fix vale issues for (/administration/postgresql/standalone.md) #332393

See merge request gitlab-org/gitlab!63072

doc/administration/postgresql/standalone.md

@@ -17,8 +17,8 @@ together with Omnibus GitLab. This is recommended as part of our
 1. [Download and install](https://about.gitlab.com/install/) the Omnibus GitLab
    package you want using *steps 1 and 2* from the GitLab downloads page.
    - Do not complete any other steps on the download page.
-1. Generate a password hash for PostgreSQL. This assumes you will use the default
-   username of `gitlab` (recommended). The command will request a password
+1. Generate a password hash for PostgreSQL. This assumes you are using the default
+   username of `gitlab` (recommended). The command requests a password
    and confirmation. Use the value that is output by this command in the next
    step as the value of `POSTGRESQL_PASSWORD_HASH`.
 
@@ -31,7 +31,7 @@ together with Omnibus GitLab. This is recommended as part of our
 
    - `POSTGRESQL_PASSWORD_HASH` - The value output from the previous step
    - `APPLICATION_SERVER_IP_BLOCKS` - A space delimited list of IP subnets or IP
-     addresses of the GitLab application servers that will connect to the
+     addresses of the GitLab application servers that connect to the
      database. Example: `%w(123.123.123.123/32 123.123.123.234/32)`
 
    ```ruby
@@ -64,7 +64,7 @@ together with Omnibus GitLab. This is recommended as part of our
 
 1. [Reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure) for the changes to take effect.
 1. Note the PostgreSQL node's IP address or hostname, port, and
-   plain text password. These will be necessary when configuring the GitLab
+   plain text password. These are necessary when configuring the GitLab
    application servers later.
 1. [Enable monitoring](replication_and_failover.md#enable-monitoring)