Rewrite of proposed section by Ben

Co-authored-by: Ben Straub <[email protected]>

Author: HonkingGoose

book/07-git-tools/sections/rewriting-history.asc

@@ -310,22 +310,15 @@ pick 461cb2a This commit is OK
 drop 5aecc10 This commit is broken
 ----
 
-[CAUTION]
-====
-Do not delete/drop a commit that other commits depend on!
-It's a bad idea to drop the first commit in the `rebase -i` script list.
-The following commits depend on the first commit being present, as the root of all changes that follow.
-====
+Because of the way Git builds commit objects, deleting or altering a commit will cause the rewriting of all the commits that follow it.
+The further back in your repo's history you go, the more commits will need to be recreated.
+This can cause lots of merge conflicts if you have many commits later in the sequence that depend on the one you just deleted.
 
-Avoid doing this:
-[source,console]
-----
-drop 5aecc10 This commit is broken
-pick c6be4c9 This commit is OK but depends on changes made in 5aecc10
-----
+If you get partway through a rebase like this and decide it's not a good idea, you can always stop.
+Type `git rebase --abort`, and your repo will be returned to the state it was in before you started the rebase.
 
-Git will complain about the broken state, and ask you to resolve the conflicts manually.
-You can also just back out of the rebase by using `git rebase --abort`.
+If you finish a rebase and decide it's not what you want, you can use `git reflog` to recover an earlier version of your branch.
+See <<ch10-git-internals#_data_recovery>> for more information on the `reflog` command.
 
 [NOTE]
 ====