Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 8 insertions, 8 deletions

diff --git a/git-commit.html b/git-commit.html
index 1e468167e..3c86e478a 100644
--- a/git-commit.html
+++ b/git-commit.html
@@ -781,7 +781,7 @@ by using <em>git rm</em> to remove files from the working tree
 by listing files as arguments to the <em>commit</em> command, in which

    case the commit will ignore changes staged in the index, and instead

    record the current content of the listed files (which must already

-   be known to git);

+   be known to Git);

 </p>

 </li>

 <li>

@@ -823,7 +823,7 @@ that, you can recover from it with <em>git reset</em>.</p></div>
 <p>

         Tell the command to automatically stage files that have

         been modified and deleted, but new files you have not

-        told git about are not affected.

+        told Git about are not affected.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1431,17 +1431,17 @@ refuses to run when given pathnames (but see <code>-i</code> option).</p></div>
 with a single short (less than 50 character) line summarizing the

 change, followed by a blank line and then a more thorough description.

 The text up to the first blank line in a commit message is treated

-as the commit title, and that title is used throughout git.

+as the commit title, and that title is used throughout Git.

 For example, <a href="git-format-patch.html">git-format-patch(1)</a> turns a commit into email, and it uses

 the title on the Subject line and the rest of the commit in the body.</p></div>

-<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>

@@ -1461,9 +1461,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">

@@ -1564,7 +1564,7 @@ information.</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2013-01-20 18:01:21 PST

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

 </div>

 </div>

 </body>