Proofread the Release Notes for April release

Author: NickVolynkin

conf.py

@@ -37,9 +37,9 @@
 ]
 
 extlinks = {
-    'tarantool-issue': ('https://github.com/tarantool/tarantool/issues/%s', 'tarantool/tarantool#'),
-    'tarantool-release': ('https://github.com/tarantool/tarantool/releases/%s', 'tarantool/tarantool/releases/'),
-    'doc-issue': ('https://github.com/tarantool/doc/issues/%s', 'tarantool/doc#'),
+    'tarantool-issue': ('https://github.com/tarantool/tarantool/issues/%s', 'gh-'),
+    'tarantool-release': ('https://github.com/tarantool/tarantool/releases/%s', 'v. '),
+    'doc-issue': ('https://github.com/tarantool/doc/issues/%s', 'doc-'),
 }
 
 imgmath_image_format = 'svg'

doc/release/1.10.10.rst

@@ -12,7 +12,7 @@ Overview
 :doc:`long-term support (LTS) version </release/policy>`
 1.10.x release series.
 
-The label “stable” means there are 1.10.x-based applications running in
+The label "stable" means there are 1.10.x-based applications running in
 production for quite a while without known crashes, incorrect results or
 other showstopper bugs.
 
@@ -36,32 +36,30 @@ Functionality added or changed
 Build
 ~~~~~
 
--   Updated CMake minimum required version in Tarantool build
-    infrastructure to 3.1.
--   Stop publishing new binary packages for CentOS 6.
--   Stop publishing new binary packages for Debian Jessie.
--   Publish binary packages for Fedora 33 (:tarantool-issue:`5502`).
--   Backported ``-DENABLE_LTO=ON/OFF`` cmake option (:tarantool-issue:`3117`,
+-   Tarantool build infrastructure now requires CMake version 3.1 or later.
+-   Binary packages for CentOS 6 and Debian Jessie won't be published since this version.
+-   Binary packages for Fedora 33 (:tarantool-issue:`5502`) are now available.
+-   Backported ``-DENABLE_LTO=ON/OFF`` CMake option (:tarantool-issue:`3117`,
     :tarantool-issue:`3743`).
     It is useful for building packages for Fedora 33 (:tarantool-issue:`5502`).
--   Bump built-in zstd version from v1.3.3 to v1.4.8
+-   The built-in zstd is upgraded from v1.3.3 to v1.4.8
     (part of :tarantool-issue:`5502`).
 -   libcurl symbols in the case of bundled libcurl are now exported
     (:tarantool-issue:`5223`, :tarantool-issue:`5542`).
--   Enable smtp and smtps protocols in bundled libcurl (:tarantool-issue:`4559`).
--   Ship libcurl headers to system path “${PREFIX}/include/tarantool” in
-    the case of libcurl included as bundled library or static build
+-   SMTP and SMTPS protocols are now enabled in the bundled libcurl (:tarantool-issue:`4559`).
+-   The libcurl headers are now shipped to system path ``${PREFIX}/include/tarantool``
+    when libcurl is included as a bundled library or in a static build
     (:tarantool-issue:`4559`).
 
 Testing
 ~~~~~~~
 
--   We’re moving to GitHub Actions (:tarantool-issue:`5662`).
--   Implemented self-sufficient LuaJIT testing environment. As a result
-    LuaJIT build system is partially ported to CMake and all testing
-    machinery is enclosed within tarantool/luajit repository
-    (:tarantool-issue:`4862`, :tarantool-issue:`5470`).
--   Switch to Python 3 by default in a test infrastructure (:tarantool-issue:`5652`)
+-   Tarantool is moving to GitHub Actions (:tarantool-issue:`5662`).
+-   Implemented a self-sufficient LuaJIT testing environment. As a result,
+    LuaJIT build system is now partially ported to CMake and all testing
+    machinery is enclosed within the `tarantool/luajit <https://github.com/tarantool/luajit/>`__
+    repository (:tarantool-issue:`4862`, :tarantool-issue:`5470`).
+-   Python 3 is now the default in the test infrastructure (:tarantool-issue:`5652`).
 
 Bugs fixed
 ----------
@@ -70,25 +68,24 @@ Core
 ~~~~
 
 -   Extensive usage of ``uri`` and ``uuid`` modules with debug log level
-    could lead to a crash or corrupted result of the functions from these
-    modules. Also their usage from the callbacks passed to ``ffi.gc()``
-    could lead to the same but much easier. The same could happen with
-    some functions from the modules ``fio``, ``box.tuple``, ``iconv``
+    no longer leads to crashes or corrupted results of the functions from these
+    modules.
+    Same problem is resolved for using these modules from the callbacks passed to ``ffi.gc()``,
+    and for some functions from the modules ``fio``, ``box.tuple``, and ``iconv``
     (:tarantool-issue:`5632`).
 
 Lua
 ~~~
 
--   Fixed -e option, when tarantool always entered interactive mode when
-    stdin is a tty. Now, ``tarantool -e 'print"Hello"'`` doesn’t enter
-    interactive mode as it was before, just prints ‘Hello’ and exits
+-   Fixed the `-e` option, when ``tarantool`` used to enter the interactive mode when
+    stdin is a TTY. Now, ``tarantool -e 'print"Hello"'`` doesn't enter the
+    interactive mode, but just prints "Hello" and exits
     (:tarantool-issue:`5040`).
 
 ..  _build-1:
 
 Build
 ~~~~~
 
--   Make recovering with force_recovery option delete newer than snapshot
-    vylog files. So that instance can recover after incidents during
-    checkpoint (:tarantool-issue:`5823`).
+-   Recovering with ``force_recovery`` option now deletes vylog files newer than the snapshot.
+    It helps an instance recover after incidents during a checkpoint (:tarantool-issue:`5823`).

doc/release/1.10.9.rst

@@ -38,11 +38,11 @@ Build
 Misc
 ~~~~
 
--   Don’t start an ‘example’ instance after installing tarantool
+-   Don’t start an ‘example’ instance after installing Tarantool
     (:tarantool-issue:`4507`).
 
-    Before this release tarantool package for Debian and Ubuntu used to
-    automatically enable and start an ‘example’ instance, which would
+    Before this release the ``tarantool`` package for Debian and Ubuntu used to
+    automatically enable and start an 'example' instance, which would
     listen on the TCP port ``3301``. Since this release the instance file
     is installed to ``/etc/tarantool/instances.available/example.lua``,
     but isn’t enabled by default and not started anymore. You can enable
@@ -92,6 +92,6 @@ Lua
 
 -   An attempt to use a ``net.box`` connection which is not established
     yet now results in a correctly reported error (:tarantool-issue:`4787`).
--   Fixed a hang which occured when ``tarantool`` ran a user script with
+-   Fixed a hang which occurred when ``tarantool`` ran a user script with
     the ``-e`` option and this script exited with an error (like with
     ``tarantool -e 'assert(false)'``) (:tarantool-issue:`4983`).

doc/release/2.8.1.rst

@@ -11,17 +11,17 @@ Overview
 2.8.1 is the :doc:`beta </release/policy>`
 version of the 2.8 release series.
 
-This release introduces 28 new features and resolves 31 bugs since the
-2.7.2 version. There can be bugs in less common areas. If you find any,
-feel free to `report an
+This release introduces 28 new features and resolves 31 bug since version :doc:`2.7.2`.
+There can be bugs in less common areas.
+If you find any, feel free to `report an
 issue <https://github.com/tarantool/tarantool/issues>`__ on GitHub.
 
 Notable changes are:
 
--  Implement ability to run multiple iproto threads.
--  Set box.cfg options with environment variables.
--  Introduce box.ctl.promote() and the concept of manual elections.
--  Lua memory profiler enhancements.
+-  Tarantool is now able to set multiple iproto threads.
+-  Setting ``box.cfg`` options with environment variables.
+-  The new ``box.ctl.promote()`` function and the concept of manual elections.
+-  Enhancements in the Lua memory profiler.
 
 Compatibility
 -------------
@@ -40,37 +40,46 @@ Functionality added or changed
 Core
 ~~~~
 
--   Introduce exclude_null option to index part definition. When it is
-    on, index filters and doesn’t store tuples with “null” value of this
-    part (:tarantool-issue:`4480`).
-
--   Added slab_alloc_granularity option to box.cfg{}. This option allows
-    user to set multiplicity of memory allocation in small allocator.
-    slab_alloc_granularity must be exponent of two and >= 4 (:tarantool-issue:`5518`).
-
--   Previously lua on_shutdown triggers were started sequentially, now
-    each of triggers starts in a separate fiber. Tarantool waits for 3.0
-    seconds to their completion by default. User has the option to change
-    this value using new implemented box.ctl.set_on_shutdown_timeout
-    function. If timeout has expired, tarantool immediately stops,
-    without waiting for other triggers completion.
-
--   Implemented on_shutdown API, which allows tarantool module developer
-    to register functions that will be called when tarantool stopped
-    (:tarantool-issue:`5723`).
-
--   Introduce the concept of WAL queue and a new configuration option:
-    ``wal_queue_max_size``, measured in bytes, with 16 Mb default. The
-    option helps limit the pace at which replica submits new transactions
-    to WAL: the limit is checked every time a transaction from master is
-    submitted to replica’s WAL, and the space taken by a transaction is
-    considered empty once it’s successfully written (:tarantool-issue:`5536`).
-
--   Provide information about state of synchronous replication via
+-   The ``exclude_null`` option can now be used in the index part definition.
+    With this option, the index filters and doesn't store tuples with "null" value
+    of the corresponding part part (:tarantool-issue:`4480`).
+
+    For example, an index created with
+    ``s:create_index('sk', {parts={{2, 'number', exclude_null=true}}})``
+    will ignore tuples ``{1, null}`` and ``{2, null}``,
+    but will not ignore ``{null, 1}`` or ``{1, 1}``.
+
+-   Added a ``slab_alloc_granularity`` option to ``box.cfg{}``. This option allows
+    user to set multiplicity of memory allocation in a small allocator.
+    The value of ``slab_alloc_granularity`` must be exponent of two and >= 4
+    (:tarantool-issue:`5518`).
+
+-   Previously, Lua `on_shutdown` triggers started sequentially.
+    Now each trigger starts in a separate fiber.
+    By default, Tarantool waits for the triggers to finish for 3.0 seconds.
+    User has the option to change this value using the new
+    ``box.ctl.set_on_shutdown_timeout`` function.
+
+    When the timeout expires, Tarantool stops immediately
+    without waiting for the other triggers to finish.
+
+-   Tarantool module developers can now register functions to call when Tarantool stops
+    with the new ``on_shutdown`` API, (:tarantool-issue:`5723`).
+
+-   Introduced the concept of WAL queue and the new configuration option
+    ``wal_queue_max_size``, measured in bytes.
+    The default value is 16 Mb.
+    The option helps limit the pace at which replica submits new transactions to the WAL.
+    The limit is checked every time a transaction from the master is
+    submitted to the replica’s WAL.
+    The space taken by the transaction is considered empty once it’s successfully written
+    (:tarantool-issue:`5536`).
+
+-   The information about the state of synchronous replication is now available via the
     ``box.info.synchro`` interface (:tarantool-issue:`5191`).
 
--   Implement ability to run multiple iproto threads, which is useful in
-    some specific workloads where iproto thread is the bottleneck of
+-   Tarantool can now run multiple iproto threads.
+    It iss useful in some specific workloads where iproto thread is the bottleneck of
     throughput (:tarantool-issue:`5645`).
 
 -   Update operations can’t insert with gaps. This patch changes the