Autogenerated HTML docs for v2.38.0-83-gd420d

2 files changed, 10 insertions, 10 deletions

diff --git a/technical/bundle-uri.html b/technical/bundle-uri.html
index f22657a9b..10ee76499 100644
--- a/technical/bundle-uri.html
+++ b/technical/bundle-uri.html
@@ -942,8 +942,8 @@ bundle.<id>.creationToken
 <dd>

 <p>

         This value is a nonnegative 64-bit integer used for sorting the bundles

-        the list. This is used to download a subset of bundles during a fetch

-        when <code>bundle.heuristic=creationToken</code>.

+        list. This is used to download a subset of bundles during a fetch when

+        <code>bundle.heuristic=creationToken</code>.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1052,10 +1052,10 @@ If the downloaded data from a bundle URI is a bundle, then the client
    making those OIDs present. When all required OIDs are present, the

    client unbundles that data using a refspec. The default refspec is

    <code>+refs/heads/*:refs/bundles/*</code>, but this can be configured. These refs

-   are stored so that later <code>git fetch</code> negotiations can communicate the

-   bundled refs as <code>have`s, reducing the size of the fetch over the Git

+   are stored so that later <code>git fetch</code> negotiations can communicate each

+   bundled ref as a <code>have</code>, reducing the size of the fetch over the Git

    protocol. To allow pruning refs from this ref namespace, Git may

-   introduce a numbered namespace (such as `refs/bundles/&lt;i&gt;/*</code>) such that

+   introduce a numbered namespace (such as <code>refs/bundles/&lt;i&gt;/*</code>) such that

    stale bundle refs can be deleted.

 </p>

 </li>

@@ -1463,7 +1463,7 @@ would cause these on-demand downloads to be too aggressive.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-09-21 15:44:34 PDT

+ 2022-10-11 11:07:16 PDT

 </div>

 </div>

 </body>

diff --git a/technical/bundle-uri.txt b/technical/bundle-uri.txt
index 18f2dedd4..b78d01d9a 100644
--- a/technical/bundle-uri.txt
+++ b/technical/bundle-uri.txt
@@ -153,8 +153,8 @@ bundle.<id>.filter::
 
 bundle.<id>.creationToken::
 	This value is a nonnegative 64-bit integer used for sorting the bundles
-	the list. This is used to download a subset of bundles during a fetch
-	when `bundle.heuristic=creationToken`.
+	list. This is used to download a subset of bundles during a fetch when
+	`bundle.heuristic=creationToken`.
 
 bundle.<id>.location::
 	This string value advertises a real-world location from where the bundle
@@ -234,8 +234,8 @@ will interact with bundle URIs according to the following flow:
    making those OIDs present. When all required OIDs are present, the
    client unbundles that data using a refspec. The default refspec is
    `+refs/heads/*:refs/bundles/*`, but this can be configured. These refs
-   are stored so that later `git fetch` negotiations can communicate the
-   bundled refs as `have`s, reducing the size of the fetch over the Git
+   are stored so that later `git fetch` negotiations can communicate each
+   bundled ref as a `have`, reducing the size of the fetch over the Git
    protocol. To allow pruning refs from this ref namespace, Git may
    introduce a numbered namespace (such as `refs/bundles/<i>/*`) such that
    stale bundle refs can be deleted.