Similar to the previous commit, the use of backticks for monospacing and a single quote as an apostrophe trip up AsciiDoc in two places which render as follows: `git range-diff ... diffs' coloring ‘1` is ... commits' patches Reword slighly to avoid those last single quotes. Signed-off-by: Martin Ågren <martin.agren@xxxxxxxxx> --- Documentation/git-range-diff.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-range-diff.txt b/Documentation/git-range-diff.txt index fe350d7f40..6e9a0ea6b6 100644 --- a/Documentation/git-range-diff.txt +++ b/Documentation/git-range-diff.txt @@ -45,7 +45,7 @@ OPTIONS ------- --no-dual-color:: When the commit diffs differ, `git range-diff` recreates the - original diffs' coloring, and adds outer -/+ diff markers with + coloring of the original diffs, and adds outer -/+ diff markers with the *background* being red/green to make it easier to see e.g. when there was a change in what exact lines were added. + @@ -239,8 +239,8 @@ because of the modification: In mathematical terms, what we are looking for is some sort of a minimum cost bipartite matching; `1` is matched to `C` at some cost, etc. The underlying graph is in fact a complete bipartite graph; the cost we -associate with every edge is the size of the diff between the two -commits' patches. To explain also new commits, we introduce dummy nodes +associate with every edge is the size of the diff between the patches of +the two commits. To explain also new commits, we introduce dummy nodes on both sides: ------------ -- 2.31.1.751.gd2f1c929bd