diff --git a/README-release.md b/README-release.md
index 6c302e771c5c5652fe324af24dc2cb49fa5c8e55..3748e6f6c4bcf25181cffa66d5e0ced53057d680 100644
--- a/README-release.md
+++ b/README-release.md
@@ -1,11 +1,10 @@
 # Release Process #
 
 1. User has cloned the [blessed repository](https://bitbucket.org/uwmadison_doit/rpc-netid-php/) and has write access to it.
-2. User has updated the `version` field in `composer.json`. If this does not match the version in the tag name, the release cycle will complete, BUT composer will issue an error when users try to install the dependency.
-3. User runs the following command: `php phing.phar release -Dversion=1.2.3 -Dbranch=myBranch`
-4. The designated branch is checked out.
-5. A tag is created with the name equal to the version number with no extra characters
-6. The repository is pushed to origin with all tags. 
+2. User runs the following command: `php phing.phar release -Dversion=1.2.3 -Dbranch=myBranch`
+3. The designated branch is checked out.
+4. A tag is created with the name equal to the version number with no extra characters
+5. The repository is pushed to origin with all tags. 
 
 The end result is a new tag in the remote repository equal to the version number. Composer clients will now pick up on the new version number.