General clarity improvements

Author: ZeroIntensity

peps/pep-0797.rst

@@ -15,7 +15,7 @@ Abstract
 This PEP introduces a new :func:`~concurrent.interpreters.share` function to
 the :mod:`concurrent.interpreters` module, which allows any arbitrary object
 to be shared across interpreters using an object proxy, at the cost of being
-less efficient under multithreaded code.
+less efficient to concurrently access across multiple interpreters.
 
 For example:
 
@@ -92,10 +92,9 @@ Interpreter Switching
 
 When interacting with the wrapped object, the proxy will switch to the
 interpreter in which the object was created. This must happen for any access
-to the object, such as accessing attributes or making modifications to the object's
-:term:`reference count`. To visualize, ``foo`` in the following code is only
-ever called in the main interpreter, despite being accessed in subinterpreters
-through a proxy:
+to the object, such as accessing attributes. To visualize, ``foo`` in the
+following code is only ever called in the main interpreter, despite being
+accessed in subinterpreters through a proxy:
 
 .. code-block:: python
 
@@ -288,10 +287,10 @@ in the wrapped object's interpreter. To visualize:
 Interpreter Lifetimes
 *********************
 
-When an interpreter is destroyed, proxies wrapping objects from that
-interpreter may still exist elsewhere. To prevent this from causing crashes,
-an interpreter will invalidate all proxies pointing to its any of its objects
-by overwriting their wrapped object with ``None``.
+When an interpreter is destroyed, shared object proxies wrapping objects
+owned by that interpreter may still exist elsewhere. To prevent this
+from causing crashes, an interpreter will invalidate all proxies pointing
+to any object it owns by overwriting the proxy's wrapped object with ``None``.
 
 To demonstrate, the following snippet first prints out ``Alive``, and then
 ``None`` after deleting the interpreter:
@@ -317,7 +316,7 @@ To demonstrate, the following snippet first prints out ``Alive``, and then
 
 Note that the proxy is not physically replaced (``wrapped`` in the above example
 is still a ``SharedObjectProxy`` instance), but instead has its wrapped object
-replaced to ``None``.
+replaced with ``None``.
 
 
 Backwards Compatibility