Autogenerated HTML docs for v1.9.1-506-g7bf27

1 files changed, 5 insertions, 5 deletions

diff --git a/git-log.html b/git-log.html
index 7be5f1df4..f88961fbb 100644
--- a/git-log.html
+++ b/git-log.html
@@ -1317,7 +1317,7 @@ list.</p></div>
         reflog entries from the most recent one to older ones.

         When this option is used you cannot specify commits to

         exclude (that is, <em>&#94;commit</em>, <em>commit1..commit2</em>,

-        nor <em>commit1...commit2</em> notations cannot be used).

+        and <em>commit1...commit2</em> notations cannot be used).

 </p>

 <div class="paragraph"><p>With <tt>--pretty</tt> format other than <tt>oneline</tt> (for obvious reasons),

 this causes the output to have two extra lines of information

@@ -1911,7 +1911,7 @@ people using 80-column terminals.</p></div>
         Show the notes (see <a href="git-notes.html">git-notes(1)</a>) that annotate the

         commit, when showing the commit log message.  This is the default

         for <tt>git log</tt>, <tt>git show</tt> and <tt>git whatchanged</tt> commands when

-        there is no <tt>--pretty</tt>, <tt>--format</tt> nor <tt>--oneline</tt> option given

+        there is no <tt>--pretty</tt>, <tt>--format</tt>, or <tt>--oneline</tt> option given

         on the command line.

 </p>

 <div class="paragraph"><p>By default, the notes shown are from the notes refs listed in the

@@ -2252,7 +2252,7 @@ Subject: [PATCH] &lt;title line&gt;</tt></pre>
 stored in the commit object.  Notably, the SHA-1s are

 displayed in full, regardless of whether --abbrev or

 --no-abbrev are used, and <em>parents</em> information show the

-true parent commits, without taking grafts nor history

+true parent commits, without taking grafts or history

 simplification into account.</p></div>

 </li>

 <li>

@@ -3209,7 +3209,7 @@ another file.</p></div>
 <p>

         Omit the preimage for deletes, i.e. print only the header but not

         the diff between the preimage and <tt>/dev/null</tt>. The resulting patch

-        is not meant to be applied with <tt>patch</tt> nor <tt>git apply</tt>; this is

+        is not meant to be applied with <tt>patch</tt> or <tt>git apply</tt>; this is

         solely for people who want to just concentrate on reviewing the

         text after the change. In addition, the output obviously lack

         enough information to apply such a patch in reverse, even manually,

@@ -3698,7 +3698,7 @@ added, from the point of view of that parent).</p></div>
 <div class="paragraph"><p>In the above example output, the function signature was changed

 from both files (hence two <tt>-</tt> removals from both file1 and

 file2, plus <tt>++</tt> to mean one line that was added does not appear

-in either file1 nor file2).  Also eight other lines are the same

+in either file1 or file2).  Also eight other lines are the same

 from file1 but do not appear in file2 (hence prefixed with <tt>+</tt>).</p></div>

 <div class="paragraph"><p>When shown by <tt>git diff-tree -c</tt>, it compares the parents of a

 merge commit with the merge result (i.e. file1..fileN are the