Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 6 insertions, 6 deletions

diff --git a/git-commit-tree.html b/git-commit-tree.html
index 4d5d657dc..2627fe21d 100644
--- a/git-commit-tree.html
+++ b/git-commit-tree.html
@@ -767,7 +767,7 @@ commits have no parents.</p></div>
 <div class="paragraph"><p>While a tree represents a particular directory state of a working

 directory, a commit represents that state in "time", and explains how

 to get there.</p></div>

-<div class="paragraph"><p>Normally a commit would identify a new "HEAD" state, and while git

+<div class="paragraph"><p>Normally a commit would identify a new "HEAD" state, and while Git

 doesn&#8217;t care where you save the note about that state, in practice we

 tend to just write the result to the file that is pointed at by

 <code>.git/HEAD</code>, so that we can always see what the last committed

@@ -911,14 +911,14 @@ ISO 8601
 <div class="sect1">

 <h2 id="_discussion">Discussion</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>At the core level, git is character encoding agnostic.</p></div>

+<div class="paragraph"><p>At the core level, Git is character encoding agnostic.</p></div>

 <div class="ulist"><ul>

 <li>

 <p>

 The pathnames recorded in the index and in the tree objects

    are treated as uninterpreted sequences of non-NUL bytes.

    What readdir(2) returns are what are recorded and compared

-   with the data git keeps track of, which in turn are expected

+   with the data Git keeps track of, which in turn are expected

    to be what lstat(2) and creat(2) accepts.  There is no such

    thing as pathname encoding translation.

 </p>

@@ -938,9 +938,9 @@ The commit log messages are uninterpreted sequences of non-NUL
 </li>

 </ul></div>

 <div class="paragraph"><p>Although we encourage that the commit log messages are encoded

-in UTF-8, both the core and git Porcelain are designed not to

+in UTF-8, both the core and Git Porcelain are designed not to

 force UTF-8 on projects.  If all participants of a particular

-project find it more convenient to use legacy encodings, git

+project find it more convenient to use legacy encodings, Git

 does not forbid it.  However, there are a few things to keep in

 mind.</p></div>

 <div class="olist arabic"><ol class="arabic">

@@ -1007,7 +1007,7 @@ reversible operation.</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2013-01-18 13:06:16 PST

+Last updated 2013-02-05 21:07:26 PST

 </div>

 </div>

 </body>