diff --git a/doc/4.7-rc.md b/doc/4.7-rc.md
index d6301bc9425ff415bed8f0eab653e2c8819f6535..85f57807d291c93f42f7ce0bdf9125f46e12f7ce 100644
--- a/doc/4.7-rc.md
+++ b/doc/4.7-rc.md
@@ -82,7 +82,12 @@ You might want to spot-check a few URLs to ensure the branches were published, e
  * https://github.com/civicrm/civicrm-packages/tree/4.7.X-rc
  * https://github.com/civicrm/civicrm-wordpress/tree/4.7.X-rc
 
-## 3: Publish tarballs
+## 3: Setup automated tests
+
+ * Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
+ * In the list of `CIVIVER`s, remove any old RC's. Add the current RC.
+
+## 4: Publish tarballs
 
  * Go to https://test.civicrm.org/job/CiviCRM-Publish/
  * Check to see if the new branch is being built automatically. If not:
@@ -90,7 +95,7 @@ You might want to spot-check a few URLs to ensure the branches were published, e
    * Click "Build with parameters"
    * For the branch name, enter your chosen `4.7.X-rc`.
 
-## 4: Bump version number on `master` to  `4.7.Y`
+## 5: Bump version number on `master` to  `4.7.Y`
 
 The original branch, "master", should continue development with the next version, e.g. "4.7.Y".
 
@@ -101,8 +106,3 @@ git pull --ff-only origin master
 ./tools/bin/scripts/set-version.php 4.7.Y --commit
 git push origin master
 ```
-
-## 5: Setup automated tests
-
- * Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
- * In the list of `CIVIVER`s, remove any old RC's. Add the current RC.