Autogenerated HTML docs for v2.38.0-rc1

9 files changed, 19 insertions, 21 deletions

diff --git a/technical/api-error-handling.html b/technical/api-error-handling.html
index c9659fcb7..70dbbf693 100644
--- a/technical/api-error-handling.html
+++ b/technical/api-error-handling.html
@@ -799,7 +799,7 @@ parse-options.c.</p></div>
 </li>

 </ul></div>

 <div class="paragraph"><p>These reports will be logged via the trace2 facility. See the "error"

-event in <a href="api-trace2.txt">trace2 API</a>.</p></div>

+event in <a href="api-trace2.html">trace2 API</a>.</p></div>

 </div>

 </div>

 <div class="sect1">

@@ -878,7 +878,7 @@ a message, pass a strbuf that is explicitly ignored:</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-06-10 15:52:52 PDT

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

 </div>

 </div>

 </body>

diff --git a/technical/api-error-handling.txt b/technical/api-error-handling.txt
index 70bf1d3e5..665c4960b 100644
--- a/technical/api-error-handling.txt
+++ b/technical/api-error-handling.txt
@@ -46,7 +46,7 @@ parse-options.c.
   returns -1 after reporting the situation to the caller.
 
 These reports will be logged via the trace2 facility. See the "error"
-event in link:api-trace2.txt[trace2 API].
+event in link:api-trace2.html[trace2 API].
 
 Customizable error handlers
 ---------------------------
diff --git a/technical/api-index.html b/technical/api-index.html
index bb337b5ab..32213dff0 100644
--- a/technical/api-index.html
+++ b/technical/api-index.html
@@ -775,7 +775,7 @@ documents them.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-09-15 16:31:14 PDT

+ 2022-09-21 15:44:50 PDT

 </div>

 </div>

 </body>

diff --git a/technical/api-parse-options.html b/technical/api-parse-options.html
index 8820a402d..ed4a928a8 100644
--- a/technical/api-parse-options.html
+++ b/technical/api-parse-options.html
@@ -833,7 +833,7 @@ There must be exactly one subcommand among the arguments, or zero if the
 <p>

 All arguments following the subcommand are considered to be arguments of

   the subcommand, and, conversely, arguments meant for the subcommand may

-  not preceed the subcommand.

+  not precede the subcommand.

 </p>

 </li>

 </ul></div>

@@ -1351,7 +1351,7 @@ for real-world examples.</p></div>
 <div id="footer">

 <div id="footer-text">

 Last updated

- 2022-09-01 13:55:22 PDT

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

 </div>

 </div>

 </body>

diff --git a/technical/api-parse-options.txt b/technical/api-parse-options.txt
index c2a5e4291..61fa6ee16 100644
--- a/technical/api-parse-options.txt
+++ b/technical/api-parse-options.txt
@@ -60,7 +60,7 @@ Subcommands are special in a couple of ways:
 
 * All arguments following the subcommand are considered to be arguments of
   the subcommand, and, conversely, arguments meant for the subcommand may
-  not preceed the subcommand.
+  not precede the subcommand.
 
 Therefore, if the options array contains at least one subcommand and
 `parse_options()` encounters the first dashless argument, it will either:
diff --git a/technical/bundle-uri.html b/technical/bundle-uri.html
index 4c392bcf1..f22657a9b 100644
--- a/technical/bundle-uri.html
+++ b/technical/bundle-uri.html
@@ -741,8 +741,7 @@ asciidoc.install();
 <div class="sectionbody">

 <div class="paragraph"><p>Git bundles are files that store a pack-file along with some extra metadata,

 including a set of refs and a (possibly empty) set of necessary commits. See

-<a href="../git-bundle.html">git-bundle(1)</a> and <a href="bundle-format.txt">the bundle format</a> for more

-information.</p></div>

+<a href="../git-bundle.html">git-bundle(1)</a> and <a href="../gitformat-bundle.html">gitformat-bundle(5)</a> for more information.</p></div>

 <div class="paragraph"><p>Bundle URIs are locations where Git can download one or more bundles in

 order to bootstrap the object database in advance of fetching the remaining

 objects from a remote.</p></div>

@@ -1118,7 +1117,7 @@ bundle list (although we do <em>not</em> want to use parallel downloads here). W
 expect that the process will end when all prerequisite commit OIDs in a

 thin bundle are already in the object database.</p></div>

 <div class="paragraph"><p>When using the <code>creationToken</code> heuristic, the client can avoid downloading

-any bundles if their creation tokenss are not larger than the stored

+any bundles if their creation tokens are not larger than the stored

 creation token. After fetching new bundles, Git updates this local

 creation token.</p></div>

 <div class="paragraph"><p>If the bundle provider does not provide a heuristic, then the client

@@ -1154,7 +1153,7 @@ The client receives a 400-level response (such as <code>404 Not Found</code> or
 </li>

 <li>

 <p>

-The server reports any other failure reponse.

+The server reports any other failure response.

 </p>

 </li>

 <li>

@@ -1307,7 +1306,7 @@ is to have more frequent bundle creation. For example, bundles could be
 created every hour, and then once a day those "hourly" bundles could be

 merged into a "daily" bundle. The daily bundles are merged into the

 oldest bundle after 30 days.</p></div>

-<div class="paragraph"><p>It is recommened that this bundle strategy is repeated with the <code>blob:none</code>

+<div class="paragraph"><p>It is recommended that this bundle strategy is repeated with the <code>blob:none</code>

 filter if clients of this repository are expecting to use blobless partial

 clones. This list of blobless bundles stays in the same list as the full

 bundles, but uses the <code>bundle.&lt;id&gt;.filter</code> key to separate the two groups.

@@ -1464,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-08-18 14:11:07 PDT

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

 </div>

 </div>

 </body>

diff --git a/technical/bundle-uri.txt b/technical/bundle-uri.txt
index c25c42378..18f2dedd4 100644
--- a/technical/bundle-uri.txt
+++ b/technical/bundle-uri.txt
@@ -3,8 +3,7 @@ Bundle URIs
 
 Git bundles are files that store a pack-file along with some extra metadata,
 including a set of refs and a (possibly empty) set of necessary commits. See
-linkgit:git-bundle[1] and link:bundle-format.txt[the bundle format] for more
-information.
+linkgit:git-bundle[1] and linkgit:gitformat-bundle[5] for more information.
 
 Bundle URIs are locations where Git can download one or more bundles in
 order to bootstrap the object database in advance of fetching the remaining
@@ -290,7 +289,7 @@ expect that the process will end when all prerequisite commit OIDs in a
 thin bundle are already in the object database.
 
 When using the `creationToken` heuristic, the client can avoid downloading
-any bundles if their creation tokenss are not larger than the stored
+any bundles if their creation tokens are not larger than the stored
 creation token. After fetching new bundles, Git updates this local
 creation token.
 
@@ -319,7 +318,7 @@ Here are a few example error conditions:
   Git's other HTTP protocols in terms of handling specific 400-level
   errors.
 
-* The server reports any other failure reponse.
+* The server reports any other failure response.
 
 * The client receives data that is not parsable as a bundle or bundle list.
 
@@ -447,7 +446,7 @@ created every hour, and then once a day those "hourly" bundles could be
 merged into a "daily" bundle. The daily bundles are merged into the
 oldest bundle after 30 days.
 
-It is recommened that this bundle strategy is repeated with the `blob:none`
+It is recommended that this bundle strategy is repeated with the `blob:none`
 filter if clients of this repository are expecting to use blobless partial
 clones. This list of blobless bundles stays in the same list as the full
 bundles, but uses the `bundle.<id>.filter` key to separate the two groups.
diff --git a/technical/commit-graph.txt b/technical/commit-graph.txt
index f05e7bda1..90c9760c2 100644
--- a/technical/commit-graph.txt
+++ b/technical/commit-graph.txt
@@ -40,7 +40,7 @@ Values 1-4 satisfy the requirements of parse_commit_gently().
 
 There are two definitions of generation number:
 1. Corrected committer dates (generation number v2)
-2. Topological levels (generation nummber v1)
+2. Topological levels (generation number v1)
 
 Define "corrected committer date" of a commit recursively as follows:
 
@@ -48,7 +48,7 @@ Define "corrected committer date" of a commit recursively as follows:
     equal to its committer date.
 
  * A commit with at least one parent has corrected committer date equal to
-    the maximum of its commiter date and one more than the largest corrected
+    the maximum of its committer date and one more than the largest corrected
     committer date among its parents.
 
  * As a special case, a root commit with timestamp zero has corrected commit
diff --git a/technical/remembering-renames.txt b/technical/remembering-renames.txt
index af091a755..1e34d9139 100644
--- a/technical/remembering-renames.txt
+++ b/technical/remembering-renames.txt
@@ -407,7 +407,7 @@ considered to be "irrelevant".  See for example the following commits:
 		no longer relevant", 2021-03-13)
 
 Relevance is always determined by what the _other_ side of history has
-done, in terms of modifing a file that our side renamed, or adding a
+done, in terms of modifying a file that our side renamed, or adding a
 file to a directory which our side renamed.  This means that a path
 that is "irrelevant" when picking the first commit of a series in a
 rebase or cherry-pick, may suddenly become "relevant" when picking the