Skip to content

docs(readme): fix some typos #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 4, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@

[![npm latest][2]][3] [![npm next][10]][3] [![Travis branch][4]][5] [![AppVeyor branch][6]][7]

`commitlint` helps your team adhereing to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy.
`commitlint` helps your team adhering to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy.

# Getting started

Expand All @@ -37,7 +37,7 @@ npm install -g @commitlint/cli @commitlint/config-angular
## Configure

```bash
echo "module.exports = {extends: [@commitlint/config-angular']}" > commitlint.config.js
echo "module.exports = {extends: ['@commitlint/config-angular']}" > commitlint.config.js
```

## Test
Expand All @@ -59,7 +59,7 @@ commitlint --from=HEAD~1
## Documentation

* **Guides** - Common use cases explained in a step-by-step pace
* **Concepts** - Overarching topics important to unterstand the use of `commitlint`
* **Concepts** - Overarching topics important to understand the use of `commitlint`
* **Reference** - Mostly technical documentation


Expand Down