Proofread the Contributing section

doc/contributing/docs/examples.rst

@@ -1,10 +1,8 @@
-
-================================================================================
 Examples and templates
-================================================================================
+======================
 
-In this document, we explain general guidelines for describing Tarantool API and
-give some examples and templates.
+This document contains general guidelines for describing the Tarantool API,
+as well as examples and templates.
 
 Use this checklist for documenting a function or a method:
 
@@ -14,39 +12,37 @@ Use this checklist for documenting a function or a method:
 * Return type (if exists)
 * Possible errors (if exist)
 * Complexity factors (if exist)
-* Note re storage engine (if exists)
+* Usage with memtx and vinyl (if differs)
 * Example(s)
 * Extra information (if needed)
 
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Documenting a function
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Documenting functions
+~~~~~~~~~~~~~~~~~~~~~
 
-We describe functions of Tarantool modules via Sphinx directives ``.. module::``
-and ``.. function::``:
+We use the Sphinx directives ``.. module::``
+and ``.. function::`` to describe functions of Tarantool modules:
 
 ..  literalinclude:: ./_includes/function_template.rst
     :language: rst
 
-And the resulting output looks like this:
+The resulting output looks like this:
 
 ..  include:: ./_includes/function_template.rst
 
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Documenting class method and data
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Documenting class methods and data
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Description of a method is similar to a function, but the ``.. class::``
+Methods are described similarly to functions, but the ``.. class::``
 directive, unlike ``.. module::``, requires nesting.
 
-As for documenting data, it will be enough to write a description,
-a return type, and an example.
+As for data, it's enough to write the description, the return type, and an example.
 
-Here is an example of documenting a method and data of a class ``index_object``:
+Here is the example documentation describing
+the method and data of the ``index_object`` class:
 
 ..  literalinclude:: ./_includes/class_template.rst
     :language: rst
 
 And the resulting output looks like this:
 
-..  include:: ./_includes/class_template.rst
+..  include:: ./_includes/class_template.rst

doc/contributing/docs/infra.rst

@@ -2,29 +2,33 @@
 Documentation infrastructure
 =============================
 
-In this section of the :doc:`documentation guidelines </contributing/docs>`,
-we deal with some support activities to ensure the correct building of
+This section of the :doc:`documentation guidelines </contributing/docs>`
+discusses some of the support activities that ensure the correct building of
 documentation.
 
 .. _guidelines_doc_submodules:
 
 Adding submodules
 -----------------
 
-The source files with the documentation content are mainly stored in the
+The documentation source files are mainly stored in the
 `documentation repository <https://github.com/tarantool/doc>`_.
-However, in some of the cases the content source files are stored in
-repositories of other Tarantool-related products and modules, for example,
-`Cartridge <https://github.com/tarantool/cartridge>`_,
+However, in some cases, they are stored in the
+repositories of other Tarantool-related products
+or modules---`Cartridge <https://github.com/tarantool/cartridge>`_,
 `Monitoring <https://github.com/tarantool/metrics/tree/master/doc/monitoring>`__,
-and some others.
+and others.
 
-In this case, we need to add such a repository containing the source files
-as a submodule to the `documentation repository <https://github.com/tarantool/doc>`_
-and set up other necessary settings to ensure the proper building of the entire
-body of Tarantool documentation presented at the `official web-site <http://www.tarantool.io/en/doc>`_.
+If you are working with source files from a product or module repository,
+add that repository as a submodule to the
+`documentation repository <https://github.com/tarantool/doc>`_
+and configure other necessary settings.
+This will ensure that the entire
+body of Tarantool documentation,
+presented on the `official website <http://www.tarantool.io/en/doc>`_,
+is built properly.
 
-The steps to do that are the following:
+Here is how to do that:
 
 .. contents::
    :local:
@@ -35,7 +39,7 @@ The steps to do that are the following:
 1. Add a submodule
 ~~~~~~~~~~~~~~~~~~
 
-First, we need to add a repository containing the content source files as
+First, we need to add the repository with content source files as
 a submodule.
 
 #.  Make sure you are in the root directory of the documentation repository.
@@ -49,7 +53,7 @@ a submodule.
         cd ..
 
 
-#.  Check that the new submodule appears in the ``.gitmodules`` file, for example:
+#.  Check that the new submodule is in the ``.gitmodules`` file, for example:
 
    ..   code-block:: ini
 
@@ -62,30 +66,30 @@ a submodule.
 2. Update build_submodules.sh
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Next, we should define what directories and files are to be copied from
-the submodule repository into the documentation one before building
+Now define what directories and files are to be copied from
+the submodule repository to the documentation repository before building
 documentation. These settings are defined in the ``build_submodules.sh`` file
-which is in the root directory of the documentation repository.
+in the root directory of the documentation repository.
 
-We can take examples of the already existing submodules to show the logic of
-the settings.
+Here are some real submodule examples
+that show the logic of the settings.
 
 metrics
 ^^^^^^^
 
-In case of the ``metrics`` submodule, the content source files are in the
+The content source files for the ``metrics`` submodule are in the
 ``./doc/monitoring`` directory of the submodule repository.
 In the final documentation view, the content should appear in the
 `Monitoring <https://www.tarantool.io/en/doc/latest/book/monitoring/>`__
 chapter (``https://www.tarantool.io/en/doc/latest/book/monitoring/``).
 
-So, we need to:
+To make this work:
 
-*   create a directory at ``./doc/book/monitoring/``.
-*   copy the entire content of the  ``./modules/metrics/doc/monitoring/`` directory to
+*   Create a directory at ``./doc/book/monitoring/``.
+*   Copy the entire content of the  ``./modules/metrics/doc/monitoring/`` directory to
     ``./doc/book/monitoring/``.
 
-The corresponding lines in the ``build_submodules.sh`` file are the following:
+Here are the corresponding lines in ``build_submodules.sh``:
 
 ..  code-block:: bash
 
@@ -95,25 +99,25 @@ The corresponding lines in the ``build_submodules.sh`` file are the following:
     mkdir -p "${monitoring_dest}"
     yes | cp -rf "${monitoring_root}" "${monitoring_dest}/"
 
-The ``${project_root}`` variable is defined earlier as ``project_root=$(pwd)``.
-We should start the documentation build from the documentation repository root
-directory so that will be the value of the variable.
+The ``${project_root}`` variable is defined earlier in the file as ``project_root=$(pwd)``.
+This is because the documentation build has to start from the documentation repository root
+directory.
 
 cartridge_cli
 ^^^^^^^^^^^^^
 
-In case of the ``cartridge_cli`` submodule, the content source is in
-the ``README.rst`` file located in the directory of the submodule repository.
+The content source file for the ``cartridge_cli`` submodule is
+``README.rst``, located in the directory of the submodule repository.
 In the final documentation view, the content should appear here:
 ``https://www.tarantool.io/en/doc/latest/book/cartridge/cartridge_cli/``.
 
-So, we need to:
+To make this work:
 
-*   create a directory at ``./doc/book/cartridge/cartridge_cli``
-*   copy ``./modules/cartridge_cli/README.rst`` to
+*   Create a directory at ``./doc/book/cartridge/cartridge_cli``.
+*   Copy ``./modules/cartridge_cli/README.rst`` to
     ``./doc/book/cartridge/cartridge_cli/index.rst``.
 
-The corresponding settings in the ``build_submodules.st`` file are the following:
+Here ar the corresponding settings in ``build_submodules.sh``:
 
 ..  code-block:: bash
 
@@ -130,5 +134,4 @@ The corresponding settings in the ``build_submodules.st`` file are the following
 3. Update .gitignore
 ~~~~~~~~~~~~~~~~~~~~
 
-Finaly, we should add paths to the copied directories and files to
-the ``.gitignore`` file.
+Finally, add paths to the copied directories and files to ``.gitignore``.

doc/contributing/docs/markup.rst

@@ -1,12 +1,11 @@
-================================================================================
+
 Markup reference
-================================================================================
+================
 
-Tarantool documentation is built via
+Tarantool documentation is built via the
 `Sphinx <https://www.sphinx-doc.org/en/master/index.html>`_ engine and is written in
-`reStructuredText <https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html>`_
-markup.
-This section will guide you through our typical cases while writing the docs.
+`reStructuredText <https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html>`_.
+This section will guide you through our typical documentation formatting cases.
 
 
 ..  toctree::

doc/contributing/docs/markup/links.rst

@@ -33,8 +33,8 @@ For this purpose, we add our own labels for linking to any place in this documen
 
 Our naming convention is as follows:
 
-* Character set: a through z, 0 through 9, dash, underscore.
-* Format: ``path dash filename dash tag``
+* Character set: a through z, 0 through 9, hyphen, underscore.
+* Format: ``path hyphen filename hyphen tag``
 
 **Example:**
 
@@ -48,13 +48,13 @@ where:
 *   ``box_index`` is the file name (without ".rst"), and
 *   ``iterator_type`` is the tag.
 
-Use a dash "-" to delimit the path and the file name. In the documentation
-source, we use only underscores "_" in paths and file names, reserving dash "-"
+Use a hyphen "-" to delimit the path and the file name. In the documentation
+source, we use only underscores "_" in paths and file names, reserving the hyphen "-"
 as the delimiter for local links.
 
 The tag can be anything meaningful. The only guideline is for Tarantool syntax
 items (such as members), where the preferred tag syntax is
-``module_or_object_name dash member_name``. For example, ``box_space-drop``.
+``module_or_object_name hyphen member_name``. For example, ``box_space-drop``.
 
 To add a link to an anchor, use the following syntax: