Fix typos in 2023-05-11 update patch

Reported-by: Daniel Gustafsson <daniel@yesql.se>

diff --git a/templates/index.html b/templates/index.html
index 92c3648e19c68bb30d11439d039d94dd5acef07d..e29d17335f6a0d3949ff204002574fbbe2598fd8 100644 (file)
--- a/templates/index.html
+++ b/templates/index.html
@@ -60,15 +60,15 @@
           The PostgreSQL Global Development Group has
           <a href="/download/">released an update</a> to all supported
           versions of PostgreSQL, including 15.3, 14.8, 13.11, 12.15, and 11.20.
-          This release fixes two security vulnerabilities over 80 bugs reported
-          over the last several months.
+          This release fixes two security vulnerabilities and over 80 bugs
+          reported over the last several months.
         </p>
         <p>
           PostgreSQL 11 will stop receiving fixes on November 9, 2023. If you
           are running PostgreSQL 11 in a production environment, we suggest that
-          you make pgrade to a newer, supported version of PostgreSQL. Please
-          see our <a href="/support/versioning/">versioning policy</a> for more
-          information.
+          you make plans to upgrade to a newer, supported version of PostgreSQL.
+          Please see our <a href="/support/versioning/">versioning policy</a>
+          for more information.
         </p>
         <p>
           For the full list of changes, please review the
@@ -170,15 +170,15 @@
           The PostgreSQL Global Development Group has
           <a href="/download/">released an update</a> to all supported versions
           of PostgreSQL, including 15.3, 14.8, 13.11, 12.15, and 11.20. This
-          release fixes two security vulnerabilities over 80 bugs reported over
-          the last several months.
+          release fixes two security vulnerabilities and over 80 bugs reported
+          over the last several months.
         </p>
         <p>
           PostgreSQL 11 will stop receiving fixes on November 9, 2023. If you
           are running PostgreSQL 11 in a production environment, we suggest that
-          you make pgrade to a newer, supported version of PostgreSQL. Please
-          see our <a href="/support/versioning/">versioning policy</a> for more
-          information.
+          you make plans to upgrade to a newer, supported version of PostgreSQL.
+          Please see our <a href="/support/versioning/">versioning policy</a>
+          for more information.
         </p>
         <p>
           For the full list of changes, please review the