From fc85591d984f6801d1e46fa6855f7c6fdfe5ba64 Mon Sep 17 00:00:00 2001 From: Zeke Sikelianos Date: Mon, 1 Jun 2020 11:53:19 -0700 Subject: [PATCH] docs: fix "ommitted" typo --- content/next/index.md | 2 +- content/v1.0.0/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/next/index.md b/content/next/index.md index 1226ce2..5363067 100644 --- a/content/next/index.md +++ b/content/next/index.md @@ -111,7 +111,7 @@ The description is a short summary of the code changes, e.g., _fix: array parsin 1. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., _BREAKING CHANGE: environment variables now take precedence over config files_. 1. If included in the type/scope prefix, breaking changes MUST be indicated by a - `!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be ommitted from the footer section, + `!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change. 1. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: updated ref docs._ 1. The units of information that make up conventional commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase. diff --git a/content/v1.0.0/index.md b/content/v1.0.0/index.md index 7604c87..57870c4 100644 --- a/content/v1.0.0/index.md +++ b/content/v1.0.0/index.md @@ -112,7 +112,7 @@ The description is a short summary of the code changes, e.g., _fix: array parsin 1. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., _BREAKING CHANGE: environment variables now take precedence over config files_. 1. If included in the type/scope prefix, breaking changes MUST be indicated by a - `!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be ommitted from the footer section, + `!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change. 1. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: updated ref docs._ 1. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.