--- UPGRADE_10.txt	2010-10-21 10:31:57.000000000 +0100
+++ UPGRADE_11.txt	2010-10-21 10:50:16.000000000 +0100
@@ -126,54 +126,8 @@ following the instructions in the INTROD
   are not yet running the latest 6.x version, you will need to update to the
   latest 6.x version.
 
-2. Prepare for the upgrade by ensuring that:
-
-  * Your system meets or exceeds minimum requirements for Drupal 7 as
-    specified at http://drupal.org/requirements
-
-  * You have done an inventory of all your installed non-core modules,
-    checking which have a Drupal 7-compatible version and which do not:
-
-    - For contributed modules, visit http://drupal.org/project/modules and
-      change 'Filter by compatibility:' to 7.x, then click the Search button
-      to check for modules matching your version of Drupal.
-
-    - For custom modules, review http://drupal.org/update/modules to
-      ensure that your custom module is compatible with the current version.
-
-    - Check each module's project page for any special procedures to follow
-      when upgrading to Drupal version 7, and read any UPGRADE.txt files found
-      in the Drupal 6 or 7 releases of the module. You may find that your module
-      has been included in the core of Drupal 7, has been discontinued, or has
-      not yet been upgraded for Drupal 7. See http://drupal.org/node/895314 for
-      a list of modules that have been moved into the core of Drupal 7.
-
-    -  If there is a problem or a conflict with this document, consult one of
-       the support options listed on http://drupal.org/support
-
-  * You have done an inventory of all your installed non-core themes,
-    checking which have a Drupal 7-compatible version and which do not:
-
-    - For contributed themes, visit http://drupal.org/project/themes and
-      change 'Filter by compatibility:' to 7.x, then click the Search button
-      to check for themes matching your version of Drupal.
-
-    - For custom themes, review http://drupal.org/update/theme and
-      http://drupal.org/theme-guide to ensure that your custom theme
-      is compatible with the current version.
-
-    - Check each theme's project page for any special procedures to follow
-      when upgrading to Drupal version 7, and read any UPGRADE.txt files found
-      in the Drupal 6 or 7 releases of the theme. You may find that your theme
-      has been discontinued, or has not yet been upgraded for Drupal 7.
-
-    -  If there is a problem or a conflict with this document, consult one of
-       the support options listed on http://drupal.org/support
-
-  * At this point, with your assessment, if you find that there are modules or
-    themes that you need that you cannot upgrade to Drupal 7, do not proceed
-    with this upgrade. You might consider contributing to the modules or themes
-    that are not yet ready for Drupal 7.
+2. Check that the custom modules and themes you are using on your site have 
+  versions compatible with Drupal 7 - see http://drupal.org/node/948216
 
 3. Log in as user ID 1 (also known as the site maintenance account).
   IMPORTANT! Do not close your browser until the final step is complete.
@@ -209,11 +163,12 @@ following the instructions in the INTROD
 
 9. Remove any modules from sites/all/modules and other sites/*/modules
   directories that you don't plan to enable in Drupal 7. Also remove modules
-  whose functionality has been moved into the core of Drupal 7. You can leave
-  the Drupal 6 versions of other modules in place, even though they are
-  incompatible with Drupal 7. The benefit of leaving them is that Drupal 7 will
-  list them and show their dependencies, even though they can't be enabled. This
-  may help you in the process of upgrading them in a non-conflicting order.
+  whose functionality has been moved into the core of Drupal 7 - see 
+  http://drupal.org/node/895314 for a list. You can leave the Drupal 6 versions 
+  of other modules in place, even though they are incompatible with Drupal 7. 
+  The benefit of leaving them is that Drupal 7 will list them and show their 
+  dependencies, even though they can't be enabled. This may help you in the 
+  process of upgrading them in a non-conflicting order.
 
   Follow the same process with custom and contributed themes.