1 files changed, 6 insertions, 6 deletions
diff --git a/technical/partial-clone.html b/technical/partial-clone.html
index 728b1998d..2d454599a 100644
--- a/technical/partial-clone.html
+++ b/technical/partial-clone.html
@@ -735,14 +735,14 @@ asciidoc.install();
 <body class="article">
 <div id="header">
 <h1>Partial Clone Design Notes</h1>
-<span id="revdate">2023-10-20</span>
+<span id="revdate">2023-10-23</span>
 </div>
 <div id="content">
 <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph"><p>The "Partial Clone" feature is a performance optimization for Git that
 allows Git to function without having a complete copy of the repository.
-The goal of this work is to allow Git better handle extremely large
+The goal of this work is to allow Git to better handle extremely large
 repositories.</p></div>
 <div class="paragraph"><p>During clone and fetch operations, Git downloads the complete contents
 and history of the repository.  This includes all commits, trees, and
@@ -1083,7 +1083,7 @@ Dynamic object fetching invokes fetch-pack once <strong>for each item</strong>
 Dynamic object fetching currently uses the existing pack protocol V0
   which means that each object is requested via fetch-pack.  The server
   will send a full set of info/refs when the connection is established.
-  If there are large number of refs, this may incur significant overhead.
+  If there are a large number of refs, this may incur significant overhead.
 </p>
 </li>
 </ul></div>
@@ -1098,7 +1098,7 @@ Dynamic object fetching currently uses the existing pack protocol V0
 Improve the way to specify the order in which promisor remotes are
   tried.
 </p>
-<div class="paragraph"><p>For example this could allow to specify explicitly something like:
+<div class="paragraph"><p>For example this could allow specifying explicitly something like:
 "When fetching from this remote, I want to use these promisor remotes
 in this order, though, when pushing or fetching to that remote, I want
 to use those promisor remotes in that order."</p></div>
@@ -1172,7 +1172,7 @@ for a dynamic object fetch), but we are not building on that.</p></div>
 <div class="sectionbody">
 <div class="paragraph"><p>[a] expensive-to-modify list of missing objects:  Earlier in the design of
     partial clone we discussed the need for a single list of missing objects.
-    This would essentially be a sorted linear list of OIDs that the were
+    This would essentially be a sorted linear list of OIDs that were
     omitted by the server during a clone or subsequent fetches.</p></div>
 <div class="paragraph"><p>This file would need to be loaded into memory on every object lookup.
 It would need to be read, updated, and re-written (like the .git/index)
@@ -1214,7 +1214,7 @@ type of packfile that references it.</p></div>
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2022-08-18 14:11:07 PDT
+ 2023-10-23 14:43:46 PDT
 </div>
 </div>
 </body>