Minor corrections/improvements

Author: qahmed1998

_includes/configuration-db-external.md

@@ -1,7 +1,7 @@
 #### Configuring an External Database
 
-Based on your setup, you will choose to configure the appliance to use
-an external PostgreSQL database. For example, we can only have one
+Based on your setup, you need to configure the appliance to use
+an external PostgreSQL database. For example, you can only have one
 database in a single region. However, a region can be segmented into
 multiple zones, such as database zone, user interface zone, and
 reporting zone, where each zone provides a specific function. The
@@ -19,7 +19,7 @@ Ensure you configure the settings in the `postgresql.conf` to suit your
 system. For example, customize the `shared_buffers` setting according to
 the amount of real storage available in the external system hosting the
 PostgreSQL instance. In addition, depending on the aggregate number of
-appliances expected to connect to the PostgreSQL instance, it may be
+appliances that are expected to connect to the PostgreSQL instance, it might be
 necessary to alter the `max_connections` setting.
 
 **Note:**
@@ -32,7 +32,7 @@ Use the following steps to configure an external PostgreSQL database:
 
 1.  Start the appliance and open a terminal console.
 
-2.  Enter the `appliance_console` command. The appliance console summary screen will be displayed.
+2.  Enter the `appliance_console` command. The appliance console summary screen is displayed.
 
 3.  Press **Enter** to manually configure settings.
 
@@ -51,4 +51,4 @@ Use the following steps to configure an external PostgreSQL database:
 
 10. Confirm the configuration if prompted.
 
-{{ site.data.product.title_short }} will then configure the external database.
+{{ site.data.product.title_short }} configures an external database.

_includes/configuration.md

@@ -20,7 +20,7 @@ Configure the appliance by using the internal appliance console.
 
 3.  Press `Enter` to manually configure settings.
 
-4.  Press the number for the item you want to change, and press `Enter`.
+4.  Press the number for the item that you want to change, and press `Enter`.
     The options for your selection are displayed.
 
 5.  Follow the prompts to make the changes.
@@ -35,23 +35,24 @@ Configure the appliance by using the internal appliance console.
 
 ### Configure Messaging
 
-Configuring messaging is required for appliance setup. It is recommended to configure the broker on the same appliance where your database is configured
+Configuring messaging is required for the appliance setup. It is recommended to configure the broker on the same appliance where your database is configured
 
-**Note:** You can only have one kafka broker per region.
+**Note:** You can only have one Kafka broker per region.
 
-1. You can either configure the current appliance as a kafka broker, or point the
-   appliance to an existing external kafka broker.
+1. You can either configure the current appliance as a Kafka broker, or point the
+   appliance to an existing external Kafka broker.
 
    Select the appropriate option either
    **Configure this appliance as a messaging server** or
    **Connect to an external messaging system**
-   to connect to an external kafka broker.  You will be asked to fill in the
-   required **Message Client Parameters** like IP address and username/password.
+   to connect to an external Kafka broker. Fill in the
+   required **Message Client Parameters**, such as IP address, username and password.
 
-2. Select **Proceed** and appliance_console will apply the configuration that you have
-   requested then restart evmserverd to pick up the changes.
+2. Select **Proceed**. `appliance_console` applies the configuration that you requested.
 
-**Note:** It is recommended to use your Fully Qualified Domain Name (FQDN) as the messaging hostname rather than `localhost`, ensure that a resolvable and reachable non-localhost name entry is present in `/etc/hosts`.
+3. Restart `evmserverd` to pick up the changes.
+
+**Note:** Use your Fully Qualified Domain Name (FQDN) as the messaging hostname rather than `localhost`, ensure that a resolvable and reachable non-localhost name entry is present in `/etc/hosts`.
 
 ### Configuring a Worker Appliance