Little tweaks

Author: hroncok

pep-0394.txt

@@ -51,7 +51,7 @@ For Python runtime distributors
 -------------------------------
 
 * We expect Unix-like software distributions (including systems like macOS and
-  Cygwin) should install the ``python2`` command into the default path
+  Cygwin) to install the ``python2`` command into the default path
   whenever a version of the Python 2 interpreter is installed, and the same
   for ``python3`` and the Python 3 interpreter.
 * When  invoked, ``python2`` should run some version of the Python 2
@@ -104,7 +104,7 @@ For Python script publishers
   This makes the user's environment more predictable (possibly resulting
   in fewer issues), and helps avoid disrupting their system.
 * For scripts that are only expected to be run in an activated virtual
-  environment, shebang lines can be written as ``/usr/bin/env python``,
+  environment, shebang lines can be written as ``#!/usr/bin/env python``,
   as this instructs the script to respect the active virtual environment.
 * In cases where the script is expected to be executed outside virtual
   environments, developers will need to be aware of the following
@@ -114,9 +114,9 @@ For Python script publishers
     refers to Python 2. Most of these distros do *not* provide a
     ``python2`` command.
   * Some newer Linux distributions will provide a ``python`` command that
-    refers to Python 3
+    refers to Python 3.
   * Some Linux distributions will not provide a ``python`` command at
-    all by default, but will provide a ``python3`` command by default
+    all by default, but will provide a ``python3`` command by default.
 
 * When potentially targeting these environments, developers may either
   use a Python package installation tool that rewrites shebang lines for
@@ -148,7 +148,7 @@ These recommendations are the outcome of the relevant python-dev discussions
 in March and July 2011 ([1]_, [2]_), February 2012 ([4]_),
 September 2014 ([6]_), discussion on GitHub in April 2018 ([7]_),
 on python-dev in February 2019 ([8]_), and during the PEP update review
-in May 2019 ([10]_).
+in May/June 2019 ([10]_).
 
 
 History of this PEP