diff --git a/README.md b/README.md
index 6bd5057ec..c90e1dadc 100644
--- a/README.md
+++ b/README.md
@@ -1,15 +1,16 @@
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/git/external?repository-url=https%3A%2F%2Fgithub.com%2Fvercel%2Fcommerce&project-name=commerce&repo-name=commerce&demo-title=Next.js%20Commerce&demo-description=An%20all-in-one%20starter%20kit%20for%20high-performance%20e-commerce%20sites.&demo-url=https%3A%2F%2Fcommerce-demo.vercel.app%2F&demo-image=https%3A%2F%2Fbigcommerce-demo-asset-ksvtgfvnd.vercel.app%2Fbigcommerce.png&integration-ids=oac_MuWZiE4jtmQ2ejZQaQ7ncuDT)
+
 # Next.js Commerce
+
 The all-in-one starter kit for high-performance e-commerce sites. With a few clicks, Next.js developers can clone, deploy and fully own their own store.
 Start right now at nextjs.org/commerce
 
 Demo live at: [commerce-demo.vercel.app](https://commerce-demo.vercel.app/)
 
-This project is currently under development.  
-
-## Why
-Ecommerce is one of the most important uses of the web and together we can raise the standard for ecommerce sites. 
+This project is currently under development.
 
 ## Goals and Features
+
 - Performant by default
 - SEO Ready
 - Internationalization
@@ -20,13 +21,13 @@ Ecommerce is one of the most important uses of the web and together we can raise
 - Integrations - Integrate seamlessly with the most common ecommerce platforms.
 
 ## Contribute
-Our Commitment to Open Source can be found [here](https://vercel.com/oss).
+
+Our commitment to Open Source can be found [here](https://vercel.com/oss).
 
 1. [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your own GitHub account and then [clone](https://help.github.com/articles/cloning-a-repository/) it to your local device.
 2. Create a new branch `git checkout -b MY_BRANCH_NAME`
 3. Install yarn: `npm install -g yarn`
 4. Install the dependencies: `yarn`
 5. Run `yarn dev` to build and watch for code changes
-7. The development branch is `development` (this is the branch pull requests should be made against). 
-On a release, the relevant parts of the changes in the `staging` branch are rebased into `master`.
-
+6. The development branch is `development` (this is the branch pull requests should be made against).
+   On a release, the relevant parts of the changes in the `staging` branch are rebased into `master`.