From 976054d8cbbe6a5ae13ac7f1eb54d3e3d26a5243 Mon Sep 17 00:00:00 2001 From: Ceri Davies Date: Mon, 26 Apr 2021 09:35:00 +0000 Subject: [PATCH] Correct typo. --- documentation/content/en/articles/committers-guide/_index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index e47a0ddff2..5567215dcb 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'. -- 2.31.1