Fixes rst issue

Changelog

@@ -13,33 +13,33 @@ new in Celery 3.1.
 3.1.17
 ======
 
-.. admonition:: CELERYD_FORCE_EXECV should not be used.
+.. admonition:: Do not enable the :setting:`CELERYD_FORCE_EXECV` setting!
 
     Please disable this option if you're using the RabbitMQ or Redis
-    transports.
+    transport.
 
-    Keeping this option enabled in 3.1 means the async based worker will
-    be disabled, so using is more likely to lead to trouble than doing
-    anything good.
+    Keeping this option enabled after 3.1 means the async based worker will
+    be disabled, which is more likely to lead to trouble than doing good.
 
 - **Requirements**
 
     - Now depends on :ref:`Kombu 3.0.24 <kombu:version-3.0.24>`.
 
-        Includes new Qpid transport.
+        Includes new Qpid transport backported from the future 3.2 version
+        for Python 2.6 compatibility.
 
     - Now depends on :mod:`billiard` 3.3.0.19.
 
     - ``celery[librabbitmq]`` now depends on librabbitmq 1.6.1.
 
-- **Task**: The timing for ETA/countdown tasks were off after the example ``LocalTimezone``
+- **Task**: The timing of ETA/countdown tasks were off after the example ``LocalTimezone``
   implementation in the Python documentation no longer works in Python 3.4.
   (Issue #2306).
 
 - **Task**: Raising :exc:`~celery.exceptions.Ignore` no longer sends
   ``task-failed`` event (Issue #2365).
 
-- **Redis result backend**: Fixed errors about unbound local ``self``.
+- **Redis result backend**: Fixed unbound local errors.
 
     Fix contributed by Thomas French.
 
@@ -53,7 +53,8 @@ new in Celery 3.1.
   state as being ready (Issue #2326).
 
     This could lead to the chord callback being called with invalid arguments
-    if using chords with the :setting:`CELERY_TRACK_STARTED` setting.
+    when using chords with the :setting:`CELERY_TRACK_STARTED` setting
+    enabled.
 
 - **Canvas**: The ``chord_size`` attribute is now set for all canvas primitives,
   making sure more combinations will work with the ``new_join`` optimization
@@ -83,8 +84,8 @@ new in Celery 3.1.
 - **Task**: Exception info was not properly set for tasks raising
   :exc:`~celery.exceptions.Reject` (Issue #2043).
 
-- **Worker**: The set of revokes tasks are now deduplicated when loading from
-  the worker state database (Issue #2336).
+- **Worker**: Duplicates are now removed when loading the set of revoked tasks
+  from the worker state database (Issue #2336).
 
 - **celery.contrib.rdb**: Fixed problems with ``rdb.set_trace`` calling stop
   from the wrong frame.
@@ -145,11 +146,11 @@ new in Celery 3.1.
 :release-by: Ask Solem
 
 - **Django**: Now makes sure ``django.setup()`` is called
-  before importing any task modules (Django 1.7 compatibility, Issue #2227) 
+  before importing any task modules (Django 1.7 compatibility, Issue #2227)
 
 - **Results**: ``result.get()`` was misbehaving by calling
- ``backend.get_task_meta`` in a finally call leading to
- AMQP result backend queues not being properly cleaned up (Issue #2245).
+  ``backend.get_task_meta`` in a finally call leading to
+  AMQP result backend queues not being properly cleaned up (Issue #2245).
 
 .. _version-3.1.14: