PEP 8002: Astropy: Improve wording (thanks to Thomas Robitaille)

pep-8002.rst

@@ -681,22 +681,22 @@ Regular decision process
 Code-level decisions
 ~~~~~~~~~~~~~~~~~~~~
 
-The Astropy Project is organized as *sub-packages*.  Each sub-package has an
-official *maintainer* as well as one or more *deputies*, who are responsible
-for ensuring code is reviewed and generally architecting the subpackage.
-Code-level decisions are therefore made in GitHub issues or pull requests
-(PRs), usually on the basis of consensus, moderated by the maintainer
-and deputies of that sub-package.
+The Astropy Project includes the *core Astropy package* and other
+*affiliated packages*.  For the sake of simplicity, we will avoid
+discussing affiliated packages, which can have their own rules.
+Therefore, everything below will concern the core Astropy package.
+
+The core Astropy package is organized as *sub-packages*.  Each sub-package
+has an official *maintainer* as well as one or more *deputies*, who are
+responsible for ensuring code is reviewed and generally architecting the
+subpackage.  Code-level decisions are therefore made in GitHub issues or
+pull requests (PRs), usually on the basis of consensus, moderated by the
+maintainer and deputies of that sub-package.
 
 When there is specific disagreement, majority vote of those who are involved
 in the discussion (e.g. PR) determines the winner, with the CoCo called on
 to break ties or mediate disagreements.
 
-.. note::
-   Some sub-packages (also named "affiliated packages") have a more
-   independent relationship to the Astropy Project than which is described
-   here.  For simplicity, we decided to omit them from this review.
-
 Non-code decisions
 ~~~~~~~~~~~~~~~~~~