From 905cb4614dcecdb907bb3fd08158e146d93bada4 Mon Sep 17 00:00:00 2001 From: tidy-dev <75402236+tidy-dev@users.noreply.github.com> Date: Fri, 26 Aug 2022 09:37:23 -0400 Subject: [PATCH] Grammar Co-authored-by: Steve Ward --- docs/learn-more/unreachable-commits.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn-more/unreachable-commits.md b/docs/learn-more/unreachable-commits.md index 6b696e6d8d..add4701f51 100644 --- a/docs/learn-more/unreachable-commits.md +++ b/docs/learn-more/unreachable-commits.md @@ -59,7 +59,7 @@ In GitHub Desktop, commits are displayed linearly and in chronological order. Th ![image](https://user-images.githubusercontent.com/75402236/186673232-8100fe29-4351-4a20-a96a-6043dd8d351d.png) -In GitHub Desktop, diffing across multiple commits is accomplished through a range selection that results in executing `git diff` that shows the changes of comparing the first and last commit in the selection (inclusive). Therefore, generating a diff on a branch where merge commits exist may result in unreachable commits being inside a diff selection. The following shows the unreachable commit scenario described above in `Merge Commits`. +In GitHub Desktop, diffing across multiple commits is accomplished through a range selection that results in executing `git diff`, which shows the changes of comparing the first and last commit in the selection (inclusive). Therefore, generating a diff on a branch where merge commits exist may result in unreachable commits being inside a diff selection. The following shows the unreachable commit scenario described above in `Merge Commits`. https://user-images.githubusercontent.com/75402236/186671802-4ba49315-e25c-4a6c-93d1-70f2f24fbc19.mov