From 791a0f2afcc9c6b5c7c72399ec98aee4aa8c4e48 Mon Sep 17 00:00:00 2001
From: dali546 <35352237+dali546@users.noreply.github.com>
Date: Thu, 20 Jan 2022 12:49:02 +0000
Subject: [PATCH] fix: readd impertive wording FAQ

---
 content/next/index.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/content/next/index.md b/content/next/index.md
index 6b38ebd..2994854 100644
--- a/content/next/index.md
+++ b/content/next/index.md
@@ -194,6 +194,12 @@ revert: let us never again speak of the noodle incident
 Refs: 676104e, a215868
 ```
 
+### What writing form should I use?
+
+We recommend writing a commit description and body using the [imperative](https://en.wikipedia.org/wiki/Imperative_mood) present tense writing form.
+
+There are a significant number of examples of this writing form for commits [1](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)[2](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#subject)[3](https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project)[4](https://medium.com/@danielfeelfine/commit-verbs-101-why-i-like-to-use-this-and-why-you-should-also-like-it-d3ed2689ef70)[5](https://chris.beams.io/posts/git-commit/)
+
 ## About
 
 The Conventional Commit specification is inspired by, and based heavily on, the [Angular Commit Guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines).