mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2024-11-15 02:45:15 +01:00
fix(lang): singular "parenthesis" to plural "parentheses" (#212)
This commit is contained in:
parent
d8f21847da
commit
3dc14ae6ed
@ -40,7 +40,7 @@ A BREAKING CHANGE can be part of commits of any _type_.
|
||||
|
||||
Additional types are not mandated by the conventional commits specification, and have no implicit effect in semantic versioning (unless they include a BREAKING CHANGE).
|
||||
<br /><br />
|
||||
A scope may be provided to a commit's type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`.
|
||||
A scope may be provided to a commit's type, to provide additional contextual information and is contained within parentheses, e.g., `feat(parser): add ability to parse arrays`.
|
||||
|
||||
## Examples
|
||||
|
||||
@ -94,7 +94,7 @@ The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
|
||||
1. The type `feat` MUST be used when a commit adds a new feature to your application or library.
|
||||
1. The type `fix` MUST be used when a commit represents a bug fix for your application.
|
||||
1. A scope MAY be provided after a type. A scope MUST consist of a noun describing a
|
||||
section of the codebase surrounded by parenthesis, e.g., `fix(parser):`
|
||||
section of the codebase surrounded by parentheses, e.g., `fix(parser):`
|
||||
1. A description MUST immediately follow the colon and space after the type/scope prefix.
|
||||
The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_.
|
||||
1. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.
|
||||
|
Loading…
Reference in New Issue
Block a user