1 files changed, 2 insertions, 2 deletions

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index dc3e6a4679..0b23426894 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -2480,7 +2480,7 @@ The subject should, by itself, allow the reader to quickly determine if the chan
 
 The subject line should be as short as possible while still retaining the required information.
 This is to make browsing Git log more efficient, and so that git log --oneline can display the short hash and subject on a single 80-column line.
-A good rule of thumb is to stay below 63 characters, and aim for about 50 or fewer if possible.
+A good rule of thumb is to stay below 67 characters, and aim for about 50 or fewer if possible.
 
 === Prefix the subject line with a component, if applicable
 
@@ -2489,7 +2489,7 @@ If applicable, try to use the same prefix used in previous commits to the same f
 
 ✓ `foo: Add -k option to keep temporary data`
 
-Include the prefix in the 63-character limit suggested above, so that `git log --oneline` avoids wrapping.
+Include the prefix in the 67-character limit suggested above, so that `git log --oneline` avoids wrapping.
 
 === Capitalize the first letter of the subject