Minor grammar / spelling changes

README.md

@@ -47,7 +47,7 @@ Note: If you are already running a webserver on port 80 (e.g. Macs usually have
 
 If you configure a .env file (just copy [.env.example](https://github.com/iaincollins/nextjs-starter/blob/master/.env.example) over to '.env' and fill in the options) you can configure a range of options.
 
-See the [AUTHENTICATION.md](https://github.com/iaincollins/nextjs-starter/blob/master/AUTHENTICATION.md) for how to set up oAuth if you want to do that. It suggested you start with Twitter as it's the easiest to get working.
+See the [AUTHENTICATION.md](https://github.com/iaincollins/nextjs-starter/blob/master/AUTHENTICATION.md) for how to set up oAuth if you want to do that. I suggest you start with Twitter as it's the easiest to get working.
 
 ## Deploying to the cloud with now.sh
 
@@ -65,15 +65,15 @@ To deploy, just run `now` in the working directory:
 If you configure a .env file `now` will include it when deploying if you use the -E option to deploy:
 
     now -E
-
-If you want to have your local `.env` file have variables for local development and have a different sent of variables you use in production, you can create additional .env files and tell `now` to use a specific file when deploying:
+    
+If you want to use different environment variables for `local` and `production` environments, you can create additional `.env` files and tell `now` to use a specific file when deploying:
 
     now -E production.env
 
 
 ### After deploying
 
-Once you have deployed, `now` will return a URL where the site when it has been deployed to, you can use this to preview everything works correctly in the browser.
+Once you have deployed, `now` will return a URL to where the site has been deployed. You can use this URL to preview everything works correctly in the browser.
 
 If you have set an alias for the site, you can then make the site live on the alias you have defined using `now alias`: