Some 2.0 release note tweaks

Just a few tweaks I noticed while reading through.

docs/ref/checks.txt

@@ -96,7 +96,8 @@ Backwards compatibility
 -----------------------
 
 The following checks are performed to warn the user of any potential problems
-that might occur as a result of a version upgrade.
+that might occur as a result of a version upgrade. Some have been removed since
+they were added as per the deprecation timeline.
 
 * **1_6.W001**: Some project unit tests may not execute as expected. *This
   check was removed in Django 1.8 due to false positives*.

docs/releases/2.0.txt

@@ -12,7 +12,7 @@ their deprecation cycle, and we've :ref:`begun the deprecation process for some
 features <deprecated-features-2.0>`.
 
 This release starts Django's use of a :ref:`loose form of semantic versioning
-<internal-release-cadence>`, however, there aren't any major backwards
+<internal-release-cadence>`, however there aren't any major backwards
 incompatible changes that might be expected of a 2.0 release. Upgrading should
 be a similar amount of effort as past feature releases.
 
@@ -52,7 +52,7 @@ Simplified URL routing syntax
 The new :func:`django.urls.path()` function allows a simpler, more readable URL
 routing syntax. For example, this example from previous Django releases::
 
-    url(r'^articles/(?P<year>[0-9]{4})/$', views.year_archive),
+    url(r'^articles/(?P<year>[0-9]+)/$', views.year_archive),
 
 could be written as::
 
@@ -75,8 +75,8 @@ and provide more details.
 Mobile-friendly ``contrib.admin``
 ---------------------------------
 
-The admin is now responsive and supports all major mobile devices.
-Older browsers may experience varying levels of graceful degradation.
+The admin is now responsive and supports all major mobile devices. Older
+browsers may experience varying levels of graceful degradation.
 
 Window expressions
 ------------------
@@ -172,8 +172,8 @@ Minor features
 Cache
 ~~~~~
 
-* On memcached, ``cache.set_many()`` returns a list of keys that failed to be
-  inserted.
+* ``cache.set_many()`` returns a list of keys that failed to be inserted. For
+  the built-in backends, failed inserts can only happen on memcached.
 
 File Storage
 ~~~~~~~~~~~~
@@ -222,8 +222,8 @@ Management Commands
 Migrations
 ~~~~~~~~~~
 
-* The new :option:`squashmigrations --squashed-name`  option allows naming
-  the squashed migration.
+* The new :option:`squashmigrations --squashed-name` option allows naming the
+  squashed migration.
 
 Models
 ~~~~~~
@@ -242,7 +242,7 @@ Models
   controls the number of results Django fetches from the database adapter.
 
 * :meth:`.QuerySet.earliest`, :meth:`.QuerySet.latest`, and
-  :attr:`Meta.get_latest_by <django.db.models.Options.get_latest_by>`  now
+  :attr:`Meta.get_latest_by <django.db.models.Options.get_latest_by>` now
   allow ordering by several fields.
 
 * Added the :class:`~django.db.models.functions.ExtractQuarter` function to
@@ -776,7 +776,8 @@ See :ref:`deprecated-features-1.10` for details on these changes.
 
 * The ``shell --plain`` option is removed.
 
-* The ``django.core.urlresolvers`` module is removed.
+* The ``django.core.urlresolvers`` module is removed in favor of its new
+  location, ``django.urls``.
 
 * ``CommaSeparatedIntegerField`` is removed, except for support in historical
   migrations.
@@ -797,7 +798,7 @@ See :ref:`deprecated-features-1.10` for details on these changes.
 * Using ``User.is_authenticated()`` and ``User.is_anonymous()`` as methods
   rather than properties is no longer supported.
 
-* The  ``Model._meta.virtual_fields`` attribute is removed.
+* The ``Model._meta.virtual_fields`` attribute is removed.
 
 * The keyword arguments ``virtual_only`` in ``Field.contribute_to_class()`` and
   ``virtual`` in ``Model._meta.add_field()`` are removed.