From f02224332ddaa003e17b27d67c56725d3faeba4b Mon Sep 17 00:00:00 2001 From: Dan Dascalescu Date: Wed, 30 Nov 2022 02:42:01 -0800 Subject: [PATCH] docs: remove repeated "the" --- content/v1.0.0/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v1.0.0/index.md b/content/v1.0.0/index.md index e7be63f..b977fdd 100644 --- a/content/v1.0.0/index.md +++ b/content/v1.0.0/index.md @@ -34,7 +34,7 @@ consumers of your library: 1. **feat:** a commit of the _type_ `feat` introduces a new feature to the codebase (this correlates with [`MINOR`](http://semver.org/#summary) in Semantic Versioning). 1. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with [`MAJOR`](http://semver.org/#summary) in Semantic Versioning). A BREAKING CHANGE can be part of commits of any _type_. -1. _types_ other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [the Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`, +1. _types_ other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`, `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others. 1. _footers_ other than `BREAKING CHANGE: ` may be provided and follow a convention similar to [git trailer format](https://git-scm.com/docs/git-interpret-trailers).