Apply review suggestions

Author: akukanov

source/elements/oneTBB/source/named_requirements.rst

@@ -62,7 +62,7 @@ because C++ does not permit implicit removal of the ``const`` qualifier from a t
 would not compile if the implementation attempts to pass a constant object to the function.
 
 Besides pseudo-signatures, semantic requirements also need to be met by real types and functions.
-For example, while ``std::pair<U,U> swap(U x, U y)`` fits the pseudo-signature for *Sortable*
+For example, while ``std::pair<U, U> swap(U x, U y)`` fits the pseudo-signature for *Sortable*
 via implicit conversion of references to values and implicit drop of the returned value
 (ignored by a library implementation), it is unable to swap the actual variables passed to the function
 and therefore does not meet the semantic requirements of *Sortable*.

source/elements/oneTBB/source/named_requirements/algorithms/par_for_each_body.rst

@@ -15,15 +15,15 @@ as well as it meets exactly one of the following two requirements for ``operator
 
 **ParallelForEachBody Requirements: Pseudo-Signature, Semantics**
 
-Variant 1:
+Alternative 1:
 
 .. cpp:function:: void Body::operator()( ReferenceType item ) const
 
     Process the received item.
 
 ----------------------------------------------------------------
 
-Variant 2:
+Alternative 2:
 
 .. cpp:function:: void Body::operator()( ReferenceType item, oneapi::tbb::feeder<ItemType>& feeder ) const
                   void Body::operator()( ItemType&& item, oneapi::tbb::feeder<ItemType>& feeder ) const
@@ -44,8 +44,7 @@ where
 .. note::
 
     The usual rules for :ref:`pseudo-signatures <pseudo_signatures>` apply.
-    Therefore, ``Body::operator()`` may optionally take items by value.
-    ``const`` and ``volatile`` type qualifiers are also applicable.
+    Therefore, ``Body::operator()`` may optionally take items by value or by ``const`` reference.
 
 See also: