diff --git a/dev/guides/releasing.md b/dev/guides/releasing.md
index 165045e0b..e1c17a796 100644
--- a/dev/guides/releasing.md
+++ b/dev/guides/releasing.md
@@ -4,21 +4,25 @@ This guide provides step by step guidance for cutting a new release of Nomad.
 2. Run `make prerelease`
 3. Commit any changed, generated files.
 4. On the Linux Vagrant run `make release`
-5. `mv pkg/ pkg2/`
+5. `mv pkg/ pkg2/`. We move the compiled packages such that when we run step 6,
+   the binaries are deleted.
 6. On a Mac, run `make release`
-7. `mv pkg2/* pkg/`
-8. `./scripts/dist.sh <version>`. Formating of <version> is 0.x.x(-|rcx|betax)
+7. `mv pkg2/* pkg/`. This moves all the binaries into the same folder and thus
+   we are ready for releasing.
+8. Ensure you have the hc-release environment variables set for being able to
+   read/write to S3. This can be retrieved from 1password.
+9. `./scripts/dist.sh <version>`. Formating of <version> is 0.x.x(-|rcx|betaX)
 
 # Only on final releases
 
 1. Add the new version to checkpoint.
 
-# Modifying the webiste
+# Modifying the website
 
 Assuming master is the branch you want the website to reflect
 
 1. On master, bump the version in `website/config.rb`
 2. Delete the remote stable-website branch (`git push -d origin stable-website`)
-3. Create the new stable webiste, `git checkout -b stable-webiste`
+3. Create the new stable website, `git checkout -b stable-website`
 4. `git push origin stable-website
 5. In Slack run, `hashibot deploy nomad`