1 files changed, 8 insertions, 8 deletions
diff --git a/git-push.html b/git-push.html
index cf8c7ac36..69061302c 100644
--- a/git-push.html
+++ b/git-push.html
@@ -793,7 +793,7 @@ local one.</p></div>
 </dt>
 <dd>
 <p>
-        The "remote" repository that is destination of a push
+        The "remote" repository that is the destination of a push
         operation.  This parameter can be either a URL
         (see the section <a href="#URLS">GIT URLS</a> below) or the name
         of a remote (see the section <a href="#REMOTES">REMOTES</a> below).
@@ -1331,9 +1331,9 @@ further recursion will occur. In this case, "only" is treated as "on-demand".</p
 address of the remote server, and the path to the repository.
 Depending on the transport protocol, some of this information may be
 absent.</p></div>
-<div class="paragraph"><p>Git supports ssh, git, http, and https protocols (in addition, ftp,
+<div class="paragraph"><p>Git supports ssh, git, http, and https protocols (in addition, ftp
 and ftps can be used for fetching, but this is inefficient and
-deprecated; do not use it).</p></div>
+deprecated; do not use them).</p></div>
 <div class="paragraph"><p>The native transport (i.e. git:// URL) does no authentication and
 should be used with caution on unsecured networks.</p></div>
 <div class="paragraph"><p>The following syntaxes may be used with them:</p></div>
@@ -1501,7 +1501,7 @@ config file would appear like this:</p></div>
                 fetch = &lt;refspec&gt;</code></pre>
 </div></div>
 <div class="paragraph"><p>The <code>&lt;pushurl&gt;</code> is used for pushes only. It is optional and defaults
-to <code>&lt;URL&gt;</code>. Pushing to a remote affects all defined pushurls or to all
+to <code>&lt;URL&gt;</code>. Pushing to a remote affects all defined pushurls or all
 defined urls if no pushurls are defined. Fetch, however, will only
 fetch from the first defined url if multiple urls are defined.</p></div>
 </div>
@@ -1515,7 +1515,7 @@ provide a refspec on the command line.  This file should have the
 following format:</p></div>
 <div class="listingblock">
 <div class="content">
-<pre><code>        URL: one of the above URL format
+<pre><code>        URL: one of the above URL formats
         Push: &lt;refspec&gt;
         Pull: &lt;refspec&gt;</code></pre>
 </div></div>
@@ -2036,7 +2036,7 @@ push.default
 </li>
 <li>
 <p>
-<code>simple</code> - pushes the current branch with the same name on the remote.
+<code>simple</code> - push the current branch with the same name on the remote.
 </p>
 <div class="paragraph"><p>If you are working on a centralized workflow (pushing to the same repository you
 pull from, which is typically <code>origin</code>), then you need to configure an upstream
@@ -2073,7 +2073,7 @@ push.followTags
 </dt>
 <dd>
 <p>
-        If set to true enable <code>--follow-tags</code> option by default.  You
+        If set to true, enable <code>--follow-tags</code> option by default.  You
         may override this configuration at time of push by specifying
         <code>--no-follow-tags</code>.
 </p>
@@ -2181,7 +2181,7 @@ push.useBitmaps
 <div id="footer">
 <div id="footer-text">
 Last updated
- 2023-08-24 09:59:29 PDT
+ 2023-10-23 14:43:46 PDT
 </div>
 </div>
 </body>