Reworded part of 'Running only some of the tests' in docs/internals/contributing.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15799 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/internals/contributing.txt

@@ -1010,19 +1010,22 @@ dictionary for the applicable database.
 Running only some of the tests
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Django's entire test suite takes a few minutes to run. To run a subset of the
+Django's entire test suite takes a while to run, and running every single test
-unit tests, append the names of the test modules to the ``runtests.py``
+could be redundant if, say, you just added a test to Django that you want to
+run quickly without running everything else. You can run a subset of the unit
+tests by appending the names of the test modules to ``runtests.py`` on the
 command line.
 
-As an example, if you'd like to only run tests for generic relations and
+For example, if you'd like to run tests only for generic relations and
 internationalization, type:
 
 .. code-block:: bash
 
     ./runtests.py --settings=path.to.settings generic_relations i18n
 
-See the list of directories in ``tests/modeltests`` and
+How do you find out the names of individual tests? Look in ``tests/modeltests``
-``tests/regressiontests`` for module names.
+and ``tests/regressiontests`` -- each directory name there is the name of a
+test.
 
 If you just want to run a particular class of tests, you can specify a list of
 paths to individual test classes. For example, to run the ``TranslationTests``
@@ -1032,7 +1035,7 @@ of the ``i18n`` module, type:
 
     ./runtests.py --settings=path.to.settings i18n.TranslationTests
 
-You can specify an individual test like this:
+Going beyond that, you can specify an individual test method like this:
 
 .. code-block:: bash
 
@@ -1052,7 +1055,7 @@ dependencies:
     *  memcached_, plus a :ref:`supported Python binding <memcached>`
     *  gettext_ (:ref:`gettext_on_windows`)
 
-If you want to test the memcached cache backend, you will also need to define
+If you want to test the memcached cache backend, you'll also need to define
 a :setting:`CACHES` setting that points at your memcached instance.
 
 Each of these dependencies is optional. If you're missing any of them, the
@@ -1086,10 +1089,10 @@ Requesting features
 ===================
 
 We're always trying to make Django better, and your feature requests are a key
-part of that. Here are some tips on how to most effectively make a request:
+part of that. Here are some tips on how to make a request most effectively:
 
-    * Request the feature on `django-developers`_, not in the ticket tracker;
+    * Request the feature on `django-developers`_, not in the ticket tracker.
-      it'll get read more closely if it's on the mailing list.
+      It'll get read more closely if it's on the mailing list.
 
     * Describe clearly and concisely what the missing feature is and how you'd
       like to see it implemented. Include example code (non-functional is OK)
@@ -1103,7 +1106,7 @@ part of that. Here are some tips on how to most effectively make a request:
 As with most open-source projects, code talks. If you are willing to write the
 code for the feature yourself or if (even better) you've already written it,
 it's much more likely to be accepted. If it's a large feature that might need
-multiple developers we're always happy to give you an experimental branch in
+multiple developers, we're always happy to give you an experimental branch in
 our repository; see below.
 
 Branch policy