diff --git a/README.md b/README.md
index d51b9a9..4e00094 100644
--- a/README.md
+++ b/README.md
@@ -43,9 +43,10 @@ I'll be honest with you, it's not straightforward. You should set aside about an
   - Probably there won't be anything important. The main thing to look out for are user-facing API changes, the `@expo/vector-icons` internals are different enough that you don't need to worry about it.
   - Were any dependencies added? Check imports against those in the current package.json, see why they were added - maybe they support the `bin` scripts, in which case we need them.
 5. Run `yarn` when you're done and it'll copy vendor files over to build.
-6. Go to the website directory, test it out. If new icons were added, ensure that they work here.
+6. Go to the website directory, test it out by changing the `@expo/vector-icons` version to `"../"` (TODO: investigate this quirk!). If new icons were added, ensure that they work here. 
   - While you're here, it would be kind of you to update the Expo SDK version to latest.
-7. You are done! Open a PR, have someone else like @brentvatne look at it, merge it. The website will be deployed when you merge to master.
+7. Publish an alpha release, switch back the version in the website to that version.
+8. Open a PR, have someone else like @brentvatne look at it. If it's good to go, publish the final version, update the website version again, then merge. The website will be deployed when you merge to master.
 
 ### How to deploy the website