diff --git a/pep-0304.txt b/pep-0304.txt
index 7e65b7224..53a3e3160 100644
--- a/pep-0304.txt
+++ b/pep-0304.txt
@@ -18,8 +18,9 @@ location of compiled Python bytecode files.  This idea originally
 arose as a patch request [1]_ and evolved into a discussion thread on
 the python-dev mailing list [2]_.  The introduction of an environment
 variable will allow people installing Python or Python-based
-third-party packages to control whether or not bytecode files
-should be generated, and if so, where they should be written.
+third-party packages to control whether or not bytecode files should
+be generated at installation time, and if so, where they should be
+written.
 
 
 Proposal
@@ -49,6 +50,10 @@ After startup, all runtime references are to sys.bytecodebase,
 not the PYTHONBYTECODEBASE environment variable.  sys.path is not
 modified.
 
+Note that this PEP is explicitly *not* about providing
+module-by-module or directory-by-directory control over the
+disposition of bytecode files.
+
 
 Glossary
 --------
@@ -106,6 +111,7 @@ augmented directory is thus derived as ::
     if base[0] == "\\": base = base[1:]
     augdir = os.path.join(pcb, drive, base)
 
+
 Fixing the location of the bytecode base
 ----------------------------------------