Fix some typos (#4401)

Author: andreyaksenov

doc/admin/monitoring/alerting.rst

@@ -226,7 +226,7 @@ Configuration status
 """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 
 :ref:`Configuration status <config_api_reference_info>` displays
-Tarantool 3 configuration apply state. Additional metrics desplay the count
+Tarantool 3 configuration apply state. Additional metrics display the count
 of apply warnings and errors.
 
 ..  code-block:: yaml

doc/code_snippets/test/constraints/constraint_test.lua

@@ -50,7 +50,7 @@ g.test_constraints = function(cg)
         t.assert_equals(customers:count(), 1)
         t.assert_equals(customers:get(1), {1, "Alice", 30})
 
-        -- Failed contstraint --
+        -- Failed constraint --
         t.assert_error_msg_contains("Check constraint 'check_person' failed for a tuple",
                 function() customers:insert{2, "Bob", 230} end)
 

doc/contributing/docs/api.rst

@@ -93,7 +93,7 @@ Function and method parameters
 
 If the parameter is optional, make sure it is enclosed in square brackets
 in the function declaration (in the "heading").
-Do not mark parameters additionaly as "optional" or "required":
+Do not mark parameters additionally as "optional" or "required":
 
 ..  code-block:: rst
 

doc/reference/internals/msgpack_extensions.rst

@@ -239,7 +239,7 @@ the server response will look like this:
             04                              MP_ERROR_ERRNO
             00                              MP_UINT = error number
             05                              MP_ERROR_ERRCODE
-            0a                              MP_UINT = eror code ER_SPACE_EXISTS
+            0a                              MP_UINT = error code ER_SPACE_EXISTS
 
 
 ..  _msgpack_ext-datetime:

doc/reference/reference_lua/box_schema/downgrade.rst

@@ -20,7 +20,7 @@ box.schema.downgrade()
     .. NOTE::
 
         The Tarantool's downgrade procedure is similar to the upgrade process that is described in the :ref:`Upgrades <admin-upgrades>` topic.
-        You need to run ``box.schema.downgrade()`` only on master and execute `box.shapshot()` on every instance in a replica set before restart to an older version.
+        You need to run ``box.schema.downgrade()`` only on master and execute `box.snapshot()` on every instance in a replica set before restart to an older version.
 
     To see Tarantool versions available for downgrade, call :ref:`box.schema.downgrade_versions() <box_schema-downgrade_versions>`. The oldest release available for downgrade is ``2.8.2``.
 

doc/reference/reference_lua/datetime/datetime_object.rst

@@ -24,7 +24,7 @@ datetime_object
                     -   Description
 
                 *   -   nsec
-                    -   Nanosecods
+                    -   Nanoseconds
 
                 *   -   sec
                     -   Seconds

doc/reference/reference_lua/datetime/interval_object.rst

@@ -24,7 +24,7 @@ interval_object
                     -   Description
 
                 *   -   nsec
-                    -   Nanosecods
+                    -   Nanoseconds
 
                 *   -   sec
                     -   Seconds

doc/reference/reference_sql/sql_user_guide.rst

@@ -641,7 +641,7 @@ A datetime table field can be created by using this type, which is semantically
 There is no implicit cast available from a string expression to a datetime expression (unlike convention used by majority of SQL vendors).
 In such cases, you need to use explicit cast from a string value to a datetime value (see the example above).
 
-You can subtract datetime and datetime, datetime and interval, or add datetime and interval in any order (see examples of such arithmetics in the description of the :ref:`INTERVAL type <sql_data_type_interval>`).
+You can subtract datetime and datetime, datetime and interval, or add datetime and interval in any order (see examples of such arithmetic in the description of the :ref:`INTERVAL type <sql_data_type_interval>`).
 
 The built-in functions related to the DATETIME type are :ref:`DATE_PART() <sql_function_datepart>` and :ref:`NOW() <sql_function_now>`
 

doc/tooling/tcm/tcm_cluster_monitoring.rst

@@ -44,8 +44,8 @@ Graph view
 
 The graph view of the cluster topology is shown in a tree-like structure where
 leafs are the cluster's instances. Each instance's state is shown by its color.
-You can move the graph vertexes to arrange them as you like, and zoom in and out,
-which is helpful for bigger clusters.
+You can move the graph vertices to arrange them as you like, and zoom in and out,
+which is helpful for larger clusters.
 
 To switch to the graph view, click the graph button on the right of the search bar on the **Stateboard** page.
 

locale/en/dev_guide/internals/msgpack_extensions.pot

@@ -298,7 +298,7 @@ msgid "ce 00 00 00 88                  MP_UINT = HEADER + BODY SIZE\n"
 "        04                              MP_ERROR_ERRNO\n"
 "        00                              MP_UINT = error number\n"
 "        05                              MP_ERROR_ERRCODE\n"
-"        0a                              MP_UINT = eror code ER_SPACE_EXISTS"
+"        0a                              MP_UINT = error code ER_SPACE_EXISTS"
 msgstr ""
 
 #: ../../doc/dev_guide/internals/msgpack_extensions.rst:249

locale/ru/LC_MESSAGES/dev_guide/internals/msgpack_extensions.po

@@ -414,5 +414,5 @@ msgid ""
 "        04                              MP_ERROR_ERRNO\n"
 "        00                              MP_UINT = error number\n"
 "        05                              MP_ERROR_ERRCODE\n"
-"        0a                              MP_UINT = eror code ER_SPACE_EXISTS"
+"        0a                              MP_UINT = error code ER_SPACE_EXISTS"
 msgstr ""