fix backport

Author: kay-kim

source/faq/concurrency.txt

@@ -158,23 +158,18 @@ locks they use:
 
    * - :method:`db.eval()`
 
-     - Write lock. The :method:`db.eval()` method takes a global write
-       lock while evaluating the JavaScript function. 
-       To avoid taking this global write lock, you can
-       use the :dbcommand:`eval` command with ``nolock: true``.
+     - Write lock. :method:`db.eval()` blocks all other JavaScript
+       processes.
 
 
    * - :dbcommand:`eval`
 
-     - Write lock. By default, :dbcommand:`eval` command takes a global
-       write lock while evaluating the JavaScript function. If used
-       with ``nolock: true``, the :dbcommand:`eval`
-       command does *not* take a global write lock while evaluating
-       the JavaScript function. However, the logic within the
-       JavaScript function may take write locks for write operations.
+     - Write lock. If used with the ``nolock`` lock option, the
+       :dbcommand:`eval` option does not take a write lock and
+       cannot write data to the database.
 
 
-   * - :method:`~db.collection.aggregate()`
+   * - :method:`aggregate() <db.collection.aggregate()>`
 
      - Read lock
 

source/reference/sql-aggregation-comparison.txt

@@ -65,11 +65,10 @@ terms, functions, and concepts and the corresponding MongoDB
 
    * - join
 
-     - No direct corresponding operator; however, the
+     - No direct corresponding operator; *however*, the
        :pipeline:`$unwind` operator allows for somewhat similar
        functionality, but with fields embedded within the document.
 
-
 .. seealso:: :doc:`/reference/sql-comparison`
 
 Examples