issue #321: docs fixes

docs/ansible.rst

@@ -412,7 +412,7 @@ operating mode.
 In the best case when pipelining is enabled and no temporary uploads are
 required, for each task Ansible will create one directory below a
 system-supplied temporary directory returned by :func:`tempfile.mkdtemp`, owned
-by the target user account a new-style module intends to execute in.
+by the target account a new-style module will execute in.
 
 In other cases depending on the task type, whether become is active, whether
 the target become user is privileged, whether the associated action plugin
@@ -449,8 +449,8 @@ however only one directory exists for the lifetime of each interpreter, its
 location is consistent for each target account, and it is always privately
 owned by that account.
 
-The paths below are tried until one is found that is writeable and appears live
+The paths below are tried until one is found that is writeable and lives on a
-on a filesystem with ``noexec`` disabled:
+filesystem with ``noexec`` disabled:
 
 1. ``$variable`` and tilde-expanded ``remote_tmp`` setting from
    ``ansible.cfg``

docs/changelog.rst

@@ -46,9 +46,9 @@ Mitogen for Ansible
 
 * `#321 <https://github.com/dw/mitogen/issues/321>`_: temporary file handling
   has been simplified and additional network roundtrips have been removed,
-  undoing earlier damage caused by compatibility bug fixes. A single directory
+  undoing earlier damage caused by compatibility fixes, and improving 2.6
-  is created once at startup for each persistent interpreter. See
+  compatibility. One directory is created at startup for each persistent
-  :ref:`ansible_tempfiles` for a complete description.
+  interpreter. See :ref:`ansible_tempfiles` for a complete description.
 
 * `#324 <https://github.com/dw/mitogen/issues/324>`_: plays with a custom
   ``module_utils`` would fail due to fallout from the Python 3 port and related