committers-guide: git always requires a clean tree to rebase.

Remove confusing word.

Sponsored by:		Netflix

1 files changed, 1 insertions, 1 deletions

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index 44360132c1..e27ffcfe8e 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -739,7 +739,7 @@ I have opted to do it on the commit command line, but you can also do it with 'g
 When it is time to bring in a new version, it is almost the same as w/o the branches.
 You would update like you would above, but there is one extra command before you update, and one after.
 The following assumes you are starting with an unmodified tree.
-It is important to start rebasing operations with a clean tree (Git usually requires this).
+It is important to start rebasing operations with a clean tree (Git requires this).
 
 [source,shell]
 ....