Roles: cosmetics

Author: andreyaksenov

doc/concepts/configuration.rst

@@ -184,7 +184,7 @@ Enabling and configuring roles
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 An application role is a Lua module that implements specific functions or logic.
-You can enable or turn off a specific role for certain instances in a configuration without restarting these instances.
+You can enable or turn off a particular role for certain instances in a configuration without restarting these instances.
 
 This section describes how to enable and configure roles.
 To learn how to develop custom roles, see :ref:`application_roles`.
@@ -242,7 +242,7 @@ Roles and configuration scopes
 As the most of configuration options, roles and their configurations can be defined at :ref:`different levels <configuration_scopes>`.
 Given that the ``roles`` option has the ``array`` type and ``roles_cfg`` has the ``map`` type, there are some specifics when applying the configuration:
 
--   For ``roles``, an instance's role takes precedence over roles defined at another levels.
+-   For ``roles``, an instance's role takes precedence over roles defined at another level.
     In the example below, ``instance001`` has only ``role3``:
 
     ..  code-block:: yaml
@@ -258,7 +258,7 @@ Given that the ``roles`` option has the ``array`` type and ``roles_cfg`` has the
 
 -   For ``roles_cfg``, the following rules are applied:
 
-    -   If a configuration for the same role is provided at different levels, an instance configuration takes precedence over configuration defined at another levels.
+    -   If a configuration for the same role is provided at different levels, an instance configuration takes precedence over the configuration defined at another level.
         In the example below, ``role1.greeting`` is ``'Hi'``:
 
         ..  code-block:: yaml

doc/how-to/app/app_roles.rst

@@ -4,7 +4,7 @@ Application roles
 =================
 
 An application role is a Lua module that implements specific functions or logic.
-You can enable or turn off a specific role for certain instances in a :ref:`configuration <configuration>` without restarting these instances.
+You can enable or turn off a particular role for certain instances in a :ref:`configuration <configuration>` without restarting these instances.
 A role is run when a configuration is loaded or reloaded.
 
 Roles can be divided into the following groups:
@@ -104,7 +104,7 @@ In the example below, the ``validate()`` function is used to validate the ``gree
     :end-before: local function apply
     :dedent:
 
-If the configuration is not valid, ``validate`` reports an unrecoverable error by throwing an error object.
+If the configuration is not valid, ``validate()`` reports an unrecoverable error by throwing an error object.
 
 
 
@@ -268,7 +268,7 @@ Roles' life cycle includes the stages described below.
 All role's functions report an unrecoverable error by throwing an error object.
 If an error is thrown in any phase, applying a configuration is stopped.
 If starting or stopping a role throws an error, no roles are stopped or started afterward.
-An error is catched and shown in :ref:`config:info() <config_api_reference_info>` in the ``alerts`` section.
+An error is caught and shown in :ref:`config:info() <config_api_reference_info>` in the ``alerts`` section.
 
 
 .. _roles_life_cycle_dependencies_specifics:
@@ -285,7 +285,7 @@ Suppose, there are two independent roles (``role1``, ``role2``) and three roles
         └─── role4
                  └─── role5
 
-The roles are enable in a configuration as follows:
+The roles are enabled in a configuration as follows:
 
 ..  code-block:: yaml