summaryrefslogtreecommitdiff
path: root/doc/gitlab-basics/start-using-git.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-11-14 18:06:15 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2019-11-14 18:06:15 +0000
commit921d16124a626ad94e14bacb734033b0293ba431 (patch)
tree11be086bbc2b27701c3f8d885dd552af85b100c4 /doc/gitlab-basics/start-using-git.md
parentd88843f370acfcbbd3e2b9d6d662d62132647d86 (diff)
downloadgitlab-ce-921d16124a626ad94e14bacb734033b0293ba431.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/gitlab-basics/start-using-git.md')
-rw-r--r--doc/gitlab-basics/start-using-git.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/gitlab-basics/start-using-git.md b/doc/gitlab-basics/start-using-git.md
index 05329993c64..1f43b151d5d 100644
--- a/doc/gitlab-basics/start-using-git.md
+++ b/doc/gitlab-basics/start-using-git.md
@@ -287,7 +287,7 @@ git reset HEAD~1
This leaves the changed files and folders unstaged in your local repository.
CAUTION: **Warning:**
-A Git commit should not usually be reverse, particularly if you already pushed it
+A Git commit should not usually be reversed, particularly if you already pushed it
to the remote repository. Although you can undo a commit, the best option is to avoid
the situation altogether by working carefully.