Update release process documentation.

Author: Robert Jackson

RELEASE.md

@@ -30,12 +30,36 @@ When reviewing merged PR's the labels to be used are:
 
 Once the prep work is completed, the actual release is straight forward:
 
+* First ensure that you have `release-it` installed globally, generally done by
+  using one of the following commands:
+
+```
+# using https://volta.sh
+volta install release-it
+
+# using Yarn
+yarn global add release-it
+
+# using npm
+npm install --global release-it
+```
+
+* Second, ensure that you have installed your projects dependencies:
+
 ```
+# using yarn
 yarn install
-yarn release
+
+# using npm
+npm install
+```
+
+* And last (but not least 😁) do your release:
+
+```
+release-it
 ```
 
-The `release` script leverages
-[release-it](https://github.com/release-it/release-it/) to do the mechanical
+[release-it](https://github.com/release-it/release-it/) manages the actual
 release process. It will prompt you through the process of choosing the version
 number, tagging, pushing the tag and commits, etc.

package.json

@@ -35,8 +35,8 @@
     "update-docs": "codemod-cli update-docs"
   },
   "dependencies": {
-    "ember-codemods-telemetry-helpers": "^0.5.0",
     "codemod-cli": "^2.0.0",
+    "ember-codemods-telemetry-helpers": "^0.5.0",
     "fs-extra": "^8.0.1",
     "git-repo-info": "^2.1.0",
     "minimatch": "^3.0.4",
@@ -63,7 +63,7 @@
   },
   "release-it": {
     "hooks": {
-      "before:release": "yarn update-docs"
+      "after:bump": "yarn update-docs"
     },
     "plugins": {
       "release-it-lerna-changelog": {