From 4b4661af6501b5277e4d574764caef2a322af22f Mon Sep 17 00:00:00 2001
From: James McDonald <38434825+mcdonaldjc@users.noreply.github.com>
Date: Thu, 1 Dec 2022 09:35:22 -0600
Subject: [PATCH] fix: change 'updated' to 'update' in example

---
 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 b977fdd..3b783f6 100644
--- a/content/v1.0.0/index.md
+++ b/content/v1.0.0/index.md
@@ -121,7 +121,7 @@ _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 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. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: update 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.
 1. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.