Skip to content

Commit d0de128

Browse files
Merge pull request circleci#3793 from perry-contribs/master
Update README-local-development.md
2 parents a07dcd1 + e0ef0ff commit d0de128

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README-local-development.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ There are two ways to work on CircleCI docs locally: with Docker and with Ruby/B
55

66
## 1. Local Development with Docker (recommended)
77

8-
1. Install Docker for you platform: <https://docs.docker.com/engine/installation/>
8+
1. Install Docker for your platform: <https://docs.docker.com/engine/installation/>
99
2. Clone the CircleCI docs repo: `git clone https://github.com/circleci/circleci-docs.git`
1010
3. Download this file: https://circleci.com/docs/assets/app.bundle-576b5ac91166f5b87d5f6254b647c9182e3468eeea4717c8cdc7ff7304cac0c9.js
1111
4. Rename the file from Step 3 to `app.bundle.js` and save it in the `jekyll/assets/js` directory.
@@ -28,7 +28,7 @@ You're welcome to use [Bundler](http://bundler.io/) to install these gems.
2828

2929
## Building js assets
3030

31-
Our js assets are compiled by webpack and put into a place that the jekyll build can find them.
31+
Our js assets are compiled by webpack and put into a place where the jekyll build can find them.
3232

3333
Anytime you are working on js be sure to run:
3434

@@ -59,7 +59,7 @@ All docs live in folders named after the version of CircleCI. The only two you n
5959

6060
1. Create a branch and switch to it:
6161

62-
`git checkout -b <branch-name`
62+
`git checkout -b <branch-name>`
6363

6464
2. Add or modify Markdown files in these directories according to our [style guide](CONTRIBUTING#style-guide).
6565

0 commit comments

Comments
 (0)