aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCeri Davies <ceri@submonkey.net>2021-04-26 18:18:49 +0000
committerGuangyuan Yang <ygy@FreeBSD.org>2021-04-26 18:18:49 +0000
commitcdc25df8deabea284a5d1fba92bd4a1510141d63 (patch)
treef37845d31585a762f6d9aa660a7c44de65f9728e
parentb9c2beb17bbb78591ccad1078705f67fe48e6055 (diff)
downloaddoc-cdc25df8deabea284a5d1fba92bd4a1510141d63.tar.gz
doc-cdc25df8deabea284a5d1fba92bd4a1510141d63.zip
articles/committers-guide: fix typo
-rw-r--r--documentation/content/en/articles/committers-guide/_index.adoc2
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 1799f8d47e..1f9c843090 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -486,7 +486,7 @@ All changes that you have not pushed are local and can easily be modified (git r
===== Keeping local changes
The simplest way to keep local changes (especially trivial ones) is to use 'git stash'.
-In its simples form, you use 'git stash' to record the changes (which pushes them onto the stash stack).
+In its simplest form, you use 'git stash' to record the changes (which pushes them onto the stash stack).
Most people use this to save changes before updating the tree as described above.
They then use 'git stash apply' to re-apply them to the tree.
The stash is a stack of changes that can be examined with 'git stash list'.