Skip to content

Commit eb7a082

Browse files
authored
Minor edits to README
1 parent 9d166ff commit eb7a082

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This repo contains the source code and documentation powering [docs.hackerone.co
2121

2222
### Running locally
2323

24-
1. `yarn run gatsby develop` to start the hot-reloading development server (powered by [Gatsby](https://www.gatsbyjs.org))
24+
1. `yarn develop` to start the hot-reloading development server (powered by [Gatsby](https://www.gatsbyjs.org))
2525
1. `open http://localhost:8000` to open the site in your favorite browser
2626

2727
### Deploy
@@ -34,7 +34,7 @@ This repo contains the source code and documentation powering [docs.hackerone.co
3434

3535
### Guidelines
3636

37-
The documentation is divided into several sections with a different tone and purpose. If you plan to write more than a few sentences, you might find it helpful to get familiar with the [contributing guidelines](https://github.com/Hacker0x01/docs.hackerone.com/blob/master/contributing-guidelines.md) for the appropriate sections.
37+
The documentation is divided into several sections with a different tone and purpose. If you plan to write more than a few sentences, you might find it helpful to get familiar with the [contributing guidelines](https://github.com/Hacker0x01/docs.hackerone.com/blob/master/CONTRIBUTING.md) for the appropriate sections.
3838

3939
### Create a branch
4040

@@ -58,10 +58,11 @@ The documentation is divided into several sections with a different tone and pur
5858

5959
1. `git add -A && git commit -m "My message"` (replacing `My message` with a commit message, such as `Fixed header logo on Android`) to stage and commit your changes
6060
1. `git push my-fork-name the-name-of-my-branch`
61-
1. Go to the [docs.hackerone.com repo](https://github.com/Hacker0x01/docs.hackerone.com) and you should see recently pushed branches.
61+
1. Go to the [docs.hackerone.com repo](https://github.com/Hacker0x01/docs.hackerone.com), and you should see recently pushed branches.
6262
1. Follow GitHub's instructions.
6363
1. If possible, include screenshots of visual changes.
6464

6565
## Troubleshooting
6666

67-
- `yarn reset` to clear the local cache
67+
- `yarn clean` to clear the local gatsby cache
68+
- `yarn reset` to clear the local node.js cache

0 commit comments

Comments
 (0)