update readme for local gatsby

Author: EdwardAngert

README.md

@@ -8,7 +8,7 @@ Pantheon Documentation
 
 https://pantheon.io/docs/
 
-This repository contains the [Pantheon](https://pantheon.io) documentation, as well as the tools to build local test environments.
+This repository contains the [Pantheon](https://pantheon.io) documentation as well as the tools to build local test environments.
 
 ## Changelog
 
@@ -25,6 +25,7 @@ Read [our Style Guide](https://pantheon.io/docs/style-guide) for our guidelines
 ### Prerequisites
   - MacOS or Linux system (untested with Bash on Windows)
   - [Node.js](https://nodejs.org/en/)
+  - [NVM](https://github.com/nvm-sh/nvm#installing-and-updating)
   - Gatsby CLI:
 
     ```bash
@@ -33,53 +34,61 @@ Read [our Style Guide](https://pantheon.io/docs/style-guide) for our guidelines
 
   - Alternatively, you can use [Lando](https://docs.lando.dev). Use Lando to bypass installing Node.js and the Gatsby CLI on your local machine. Lando requires a Docker version in the `2.1.0.0` - `3.1.99` range.
 
-### Get the Code
+#### Mac Steps
 
-Fork and clone this repository.
+This list of steps should work on a Mac with [Homebrew](https://brew.sh/):
 
 ```bash
-git clone https://github.com/pantheon-systems/documentation.git
+brew install node
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh | bash
+nvm install 14
+npm install -g gatsby-cli
 ```
 
-Or
+### Get the Code
+
+Fork and clone this repository:
 
 ```bash
 git clone git@github.com:pantheon-systems/documentation.git
 cd documentation
 ```
 
-### Install
-
-#### Using the Gatsby CLI directly
-
-```bash
-npm ci
-```
+### Create a GitHub API Token
 
-#### GitHub Token
-You can install directly on your host computer or via Lando. Both ways require the docs app to use a `GITHUB_API` token to operate.
 We use the [gatsby-remark-embed-snippet](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-remark-embed-snippet) to use files from GitHub in our docs. Before you can build a local development site, you need to provide a GitHub token to the environment:
 
 1. Log in to GitHub and go to <https://github.com/settings/tokens>
-1. Click Generate new token
-1. Give the token a name and click the **public_repo** checkbox, then the Generate Token button at the bottom
-1. Copy the token to your clipboard.
-1. Create or edit `.env.development`, and add (replacing `$TOKENHASH` ):
+1. Click **Generate new token**
+1. Give the token a name and click the **public_repo** checkbox, then the **Generate Token** button at the bottom
+1. Copy the token to your clipboard
+1. In the root `documentation` directory, create a new file called `.env.development` and add (replacing `$TOKENHASH` ):
 
     ```bash
     GITHUB_API=$TOKENHASH
     ```
 
+## Install With The Gatsby Cli
+
+From the `documentation` directory:
+
+```bash
+npm ci
+```
+
 ### Run
 
+Still in the `documentation` directory:
+
 ```bash
-cd documentation/
-gatsby develop
+npm run develop
 ```
-You can view the local environment at `localhost:8000/`. Updates to docs are automatically refreshed in the browser.
 
+Use your local browser to navigate to `localhost:8000/`.
+
+Locally saved updates to docs are automatically refreshed in the browser.
 
-#### Using Lando
+## Install With Lando
 
 Alternatively, you can use [Lando](https://gist.github.com/tormi/a8b8fc39f9481373b24dc94cb8d2ee31). The `lando start` command initiates the app, installs node dependencies, and starts the `gatsby develop` server for you:
 
@@ -89,12 +98,10 @@ lando start
 
 You can view the local environment at `localhost:8000/`. Updates to docs are automatically refreshed in the browser.
 
-
 ## Testing
 
 We include several tools to test that new content doesn't break the documentation. Most of these tests are performed automatically by our continuous integration service, but pull requests created from external contributors aren't included in CI tests. If you want to manually test your branch, you can execute the following tests within the Docker container.
 
 ### Merge Conflicts
 
 To check for merge conflict messages accidentally committed into the docs, run `merge_conflicts.sh` from `scripts`.
-