diff --git a/pep-0008.txt b/pep-0008.txt
index bbe93410a..13748ee11 100644
--- a/pep-0008.txt
+++ b/pep-0008.txt
@@ -474,22 +474,21 @@ Naming Conventions
 
     Method Names and Instance Variables
 
-      The story is largely the same as for functions; in general use lowercase
-      with words separated by underscores to improve readability.  Do not use
-      a leading underscore for methods accessed by other classes or functions
-      that are part of the implementation of an object type.
+      The story is largely the same as with functions: in general, use
+      lowercase with words separated by underscores as necessary to improve
+      readability.
 
-      Use one leading underscore for "internal" methods and instance variables
-      when there is no chance of a conflict with subclass or superclass
-      attributes or when a subclass might actually need access to them.
+      Use one leading underscore only for internal methods and instance
+      variables which are not intended to be part of the class's public
+      interface.  Python does not enforce this; it is up to programmers to
+      respect the convention.
 
-      Use two leading underscores (class-private names, enforced by Python
-      1.4) in those cases where it is important that only the current class
-      accesses an attribute.  Realize that Python contains enough loopholes so
-      that an insistent user could gain access nevertheless, e.g. via the
-      __dict__ attribute.  Generally, double leading underscores should be
-      used only to avoid name conflicts with attributes in classes designed to
-      be subclassed.
+      Use two leading underscores to denote class-private names.  Python
+      "mangles" these names with the class name: if class Foo has an
+      attribute named __a, it cannot be accessed by Foo.__a.  (An insistent
+      user could still gain access by calling Foo._Foo__a.)  Generally,
+      double leading underscores should be used only to avoid name conflicts
+      with attributes in classes designed to be subclassed.
 
     Designing for inheritance