apply changes from https://github.com/fila43/postgresql/pull/1/files

Author: fila43

Diff for: README.md

@@ -1,29 +1,30 @@
 # PostgreSQL system role
 ![CI Testing](https://github.com/linux-system-roles/postgresql/workflows/tox/badge.svg)
 
-This role installs, configures, and starts PostgreSQL Server.
+The PostgreSQL system installs, configures, and starts the PostgreSQL server.
 
 The role also optimizes the database server settings to improve performance.
 
 The role currently works with PostgreSQL server 10 12 and 13.
 ## Role Variables
 ### postgresql_verison
-Allow set up version of Postgresql server. This role supports Postgresql 10 12 and 13
+You can set the version of PostgreSQL server to 10, 12, or 13.
 ```yaml
 postgresql_version: "13"
 ```
 ### postgresql_password
-Optionally, you can set up password for database super user `postgres` by default
-there is not a password, datababase is accessible from `postgres` system account via UNIX socket.
-users are encouraged to use ansible vault
+Optionally, you can set a password for the `postgres` database superuser.
+By default, no password is set, and a datababase is accessible from
+the `postgres` system account through a UNIX socket.
+It is recommended to encrypt the password using Ansible Vault.
 ```yaml
 postgresql_password: !vault |
           $ANSIBLE_VAULT;1.2;AES256;dev
           ....
 ```
 ### postgresql_pg_hba_conf
-A description of input variables that are not reqiured. Upstream configuration is used by default.
-Usage of `postgresql_pg_hba_conf` causes replacement of default upstream configuration
+The content of the `postgresql_pg_hba_conf` variable replaces the default
+upstream configuration in the `/var/lib/pgsql/data/pg_hba.conf` file.
 ```yaml
 postgresql_pg_hba_conf:
   - type: local
@@ -42,23 +43,24 @@ postgresql_pg_hba_conf:
     auth_method: ident
 ```
 ### postgresql_server_conf
-Usage of `postgresql_server_conf` adds defined values at the end of postgresql.conf.
-So the default ones are overwritten.
+The content of the `postgresql_server_conf` variable is
+added to the end of the `/var/lib/pgsql/data/postgresql.conf` file.
+As a result, the default settings are overwritten.
 ```yaml
 postgresql_server_conf:
   ssl: on
   shared_buffers: 128 MB
   huge_pages: try
 ```
 ### postgresql_ssl_enable
-To set up ssl connection it's necessary to set up `postgresql_ssl_enable` variable and provide server certificate and key.
+To set up a SSL/TLS connection, set the `postgresql_ssl_enable` variable to `True`  and provide a server certificate and a private key.
 ```yaml
 postgresql_ssl_enable: true
 ```
 ### postgresql_cert_name
 In case you want to use own key and certificate. Use `postgresql_cert_name` variable. It's necessary to have both files in the same directory and with the same name with suffixes .crt and .key
 
-To specify certificate name use `postgresql_cert_name` variable.
+Use `postgresql_cert_name` variable to specify certificate name.
 For example your crt file is located in `/etc/certs/server.crt` and key in `/etc/certs/server.key`. So `postgresql_cert_name` value should be
 ```yaml
 postgresql_cert_name: /etc/certs/server
@@ -77,24 +79,24 @@ postgresql_certificates:
     ca: self-sign
 ```
 ### postgresql_input_file
-For running SQL script define path to your SQL file using `postgresql_input_file`:
+To run an SQL script, define a path to your SQL file using the `postgresql_input_file` variable:
 ```yaml
 postgresql_input_file: "/tmp/mypath/file.sql"
 ```
 ### postgresql_server_tuning
-By default the system role makes server settings tuning based on system resources,
-This functionality is enabled by default. For disabling it there is a possibility to
-set up the `postgresql_server_tuning` variable.
+By default, the PostgreSQL system role enables server settings optimization
+based on system resources. To disabe the tuning,
+set the `postgresql_server_tuning` variable to `False`.
 ```yaml
 postgresql_server_tuning: false
 ```
 
-More about usage could be found in [`examples/`](examples) directory
+See the [`examples/`](examples) for details.
 
 ## Idempotention
 This section should cover role behavior for repeated runs.
 ### Password change
-Once the password is set using `postgresql_password` variable it isn`t possible to
+Once the password is set using `postgresql_password` variable it isn't possible to
 change it by setting other value. Also for every database acces using superuser must
 be used `postgresql_password`. Including functionality of `postgresql_input_file`
 ### Config file redefinition