Autogenerated HTML docs for v1.6.6.1-383-g5a9f

1 files changed, 5 insertions, 5 deletions

diff --git a/git-blame.html b/git-blame.html
index d0d0f3ad2..531e64bb7 100644
--- a/git-blame.html
+++ b/git-blame.html
@@ -331,7 +331,7 @@ git-blame(1) Manual Page
 last modified the line. Optionally, start annotating from the given revision.</p></div>

 <div class="para"><p>The command can also limit the range of lines annotated.</p></div>

 <div class="para"><p>The report does not tell you anything about lines which have been deleted or

-replaced; you need to use a tool such as <em>git-diff</em> or the "pickaxe"

+replaced; you need to use a tool such as <em>git diff</em> or the "pickaxe"

 interface briefly mentioned in the following paragraph.</p></div>

 <div class="para"><p>Apart from supporting file annotation, git also supports searching the

 development history for when a code snippet occurred in a change. This makes it

@@ -567,7 +567,7 @@ commit.</p></div>
         file (see <tt>-M</tt>).  The first number listed is the score.

         This is the number of alphanumeric characters detected

         as having been moved between or within files.  This must be above

-        a certain threshold for <em>git-blame</em> to consider those lines

+        a certain threshold for <em>git blame</em> to consider those lines

         of code to have been moved.

 </p>

 </dd>

@@ -669,7 +669,7 @@ header elements later.</p></div>
 </div>

 <h2 id="_specifying_ranges">SPECIFYING RANGES</h2>

 <div class="sectionbody">

-<div class="para"><p>Unlike <em>git-blame</em> and <em>git-annotate</em> in older versions of git, the extent

+<div class="para"><p>Unlike <em>git blame</em> and <em>git annotate</em> in older versions of git, the extent

 of the annotation can be limited to both line ranges and revision

 ranges.  When you are interested in finding the origin for

 lines 40-60 for file <tt>foo</tt>, you can use the <tt>-L</tt> option like so

@@ -688,7 +688,7 @@ git blame -L 40,+21 foo</tt></pre>
 <div class="para"><p>which limits the annotation to the body of the <tt>hello</tt> subroutine.</p></div>

 <div class="para"><p>When you are not interested in changes older than version

 v2.6.18, or changes older than 3 weeks, you can use revision

-range specifiers  similar to <em>git-rev-list</em>:</p></div>

+range specifiers  similar to <em>git rev-list</em>:</p></div>

 <div class="literalblock">

 <div class="content">

 <pre><tt>git blame v2.6.18.. -- foo

@@ -859,7 +859,7 @@ the email address.</p></div>
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2010-01-17 02:43:49 UTC

+Last updated 2010-01-21 17:44:21 UTC

 </div>

 </div>

 </body>