revert

book/07-git-tools/sections/advanced-merging.asc

@@ -514,6 +514,7 @@ The downside of this approach is that it's rewriting history, which can be probl
 Check out <<_rebase_peril>> for more on what can happen; the short version is that if other people have the commits you're rewriting, you should probably avoid `reset`.
 This approach also won't work if any other commits have been created since the merge; moving the refs would effectively lose those changes.
 
+[[_reverse_commit]]
 ===== Reverse the commit
 
 If moving the branch pointers around isn't going to work for you, Git gives you the option of making a new commit which undoes all the changes from an existing one.

book/C-git-commands/1-git-commands.asc

@@ -365,6 +365,9 @@ We also use it in an interactive scripting mode with the `-i` option in <<_chang
 
 ==== revert
 
+The `git revert` command is essentially a reverse `git cherry-pick`. It creates a new commit that applies the exact opposite of the change introduced in the commit you're targeting, essentially undoing or reverting it.
+
+We use this in <<_reverse_commit>> to undo a merge commit.
 
 === Email