Autogenerated HTML docs for v1.6.2.2-414-g81aa

1 files changed, 3 insertions, 3 deletions

diff --git a/git-pack-refs.html b/git-pack-refs.html
index 36ee25acd..03fd54112 100644
--- a/git-pack-refs.html
+++ b/git-pack-refs.html
@@ -336,7 +336,7 @@ problem by stashing the refs in a single file,
 <tt>$GIT_DIR/packed-refs</tt>.  When a ref is missing from the

 traditional <tt>$GIT_DIR/refs</tt> hierarchy, it is looked up in this

 file and used if found.</p></div>

-<div class="para"><p>Subsequent updates to branches always creates new file under

+<div class="para"><p>Subsequent updates to branches always create new files under

 <tt>$GIT_DIR/refs</tt> hierarchy.</p></div>

 <div class="para"><p>A recommended practice to deal with a repository with too many

 refs is to pack its refs with <tt>--all --prune</tt> once, and

@@ -344,7 +344,7 @@ occasionally run <tt>git pack-refs --prune</tt>.  Tags are by
 definition stationary and are not expected to change.  Branch

 heads will be packed with the initial <tt>pack-refs --all</tt>, but

 only the currently active branch heads will become unpacked,

-and next <tt>pack-refs</tt> (without <tt>--all</tt>) will leave them

+and the next <tt>pack-refs</tt> (without <tt>--all</tt>) will leave them

 unpacked.</p></div>

 </div>

 <h2 id="_options">OPTIONS</h2>

@@ -384,7 +384,7 @@ hierarchy after packing them.  This option tells it not to.
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2009-04-02 06:49:59 UTC

+Last updated 2009-04-05 09:18:10 UTC

 </div>

 </div>

 </body>