681834 rra-draft-ijackson number paras

diff --git a/681834_gnome_recommends_networkmanager/rra-draft-ijackson b/681834_gnome_recommends_networkmanager/rra-draft-ijackson
index 5ef60764d0f636c5583c85b61b27b4cd8544352e..3aa53ebd5f9f3bebc4401f8028099e8a096959e8 100644 (file)
--- a/681834_gnome_recommends_networkmanager/rra-draft-ijackson
+++ b/681834_gnome_recommends_networkmanager/rra-draft-ijackson
@@ -1,15 +1,15 @@
-    The gnome-core metapackage is intended to reflect the core of the
+ 1. The gnome-core metapackage is intended to reflect the core of the
     GNOME desktop environment: the basic tools and subsystems that
     together constitute GNOME.  The gnome metapackage is intended to
     reflect the broader desktop environment, including extra components
     and applications.
 
-    network-manager is the GNOME network control system, and is
+ 2. network-manager is the GNOME network control system, and is
     recommended for most GNOME users.  Some Debian GNOME users don't like
     some of network-manager's behavior and prefer to instead use other
     tools, either basic ifupdown or other frameworks such as wicd.
 
-    In squeeze, the gnome metapackage lists network-manager in Recommends
+ 3. In squeeze, the gnome metapackage lists network-manager in Recommends
     but not Depends.  In wheezy, currently, network-manager has moved from
     gnome to gnome-core, and from Recommends to Depends.  This represents
     a substantially increased insistance that users of the GNOME
@@ -19,7 +19,7 @@
     integration of network-manager into GNOME than was the case in
     squeeze.
 
-    If matters are left as they currently stand, users who have the gnome
+ 4. If matters are left as they currently stand, users who have the gnome
     metapackages installed but do not have network-manager installed will,
     in the process of upgrading from squeeze to wheezy (either due to an
     explicit decision to remove it or an implicit decision to not install
@@ -28,7 +28,7 @@
     installed.  It will also no longer be possible for users to install
     GNOME metapackages in wheezy without installing network-manager.
 
-    For most applications and components, the only drawback of this would
+ 5. For most applications and components, the only drawback of this would
     be some additional disk space usage, since the application, despite
     being installed, wouldn't need to be used.  However, network-manager
     assumes that, if it is installed, it should attempt to manage the
@@ -39,7 +39,7 @@
     average user) action to disable network-manager after it has been
     installed.
 
-    The Technical Committee believes that this will cause undesireable
+ 6. The Technical Committee believes that this will cause undesireable
     behavior for upgrades from squeeze, and (of somewhat lesser
     importance) will make it more difficult than necessary for GNOME users
     to swap network management components, something for which there
@@ -48,21 +48,21 @@
     moved from the gnome-core metapackage to the gnome metapackage (which
     is defined as including additional, optional components).
 
-    Please note that this is not a general statement about GNOME
+ 7. Please note that this is not a general statement about GNOME
     components.  It is very specific to network-manager because all of the
     following apply:
 
-    1. The package takes action automatically because it is installed,
+    (i) The package takes action automatically because it is installed,
        rather than being a component that can either be run or not at the
        user's choice.
 
-    2. The package has historically been recommended rather than listed as
+    (ii) The package has historically been recommended rather than listed as
        a dependency, so existing Debian users are used to that behavior.
 
-    3. There is both demonstrable, intentional widespread replacement of
+    (ii) There is both demonstrable, intentional widespread replacement of
        that package by Debian GNOME users and no significant loss of
        unrelated GNOME desktop functionality by replacing it with a
        different component.
 
-    If any of these points did not apply, the situation would be
+ 8. If any of these points did not apply, the situation would be
     significantly different.