These may not be obvious to non-native English speakers Signed-off-by: Mike Ralphson <mike@xxxxxxxxxxxx> --- Documentation/git-am.txt | 2 +- Documentation/gitk.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/git-am.txt b/Documentation/git-am.txt index ff307eb..75081d9 100644 --- a/Documentation/git-am.txt +++ b/Documentation/git-am.txt @@ -121,7 +121,7 @@ the commit, after stripping common prefix "[PATCH <anything>]". It is supposed to describe what the commit is about concisely as a one line text. -The body of the message (iow, after a blank line that terminates +The body of the message (in other words, after a blank line that terminates RFC2822 headers) can begin with "Subject: " and "From: " lines that are different from those of the mail header, to override the values of these fields. diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt index bd005bc..cf465cb 100644 --- a/Documentation/gitk.txt +++ b/Documentation/gitk.txt @@ -74,7 +74,7 @@ frequently used options. <path>...:: Limit commits to the ones touching files in the given paths. Note, to - avoid ambiguity wrt. revision names use "--" to separate the paths + avoid ambiguity with respect to revision names use "--" to separate the paths from any preceding options. Examples -- 1.6.0.2.229.g1293c.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
