Clarifying language on how PGDG supports a project and EOL date => EOL month.

diff --git a/templates/support/versioning.html b/templates/support/versioning.html
index 34c90f67fe8fc129ddb3f771f76963f0ec3fa449..ea91d1279380d2e18d0352c4ceefb6546ed4697b 100644 (file)
--- a/templates/support/versioning.html
+++ b/templates/support/versioning.html
@@ -31,7 +31,7 @@ Upgrading to a minor release does not require a dump and restore; merely stop th
 
 <h2>PostgreSQL release support policy</h2>
 <p>
-The PostgreSQL project aims to fully support a major release for
+The PostgreSQL Global Development Group aims to support a major release for
 <strong>five years</strong>. After its end-of-life (EOL) month ends, a major version receives one final <a href="/developer/roadmap/">minor release</a>. After that final minor release, bug fixing ceases for that major version.
 </p>
 
@@ -52,7 +52,7 @@ application compatibility. In such cases, early retirement of a major
 version may be required.
 </p>
 
-<h2>End Of Life (EOL) dates</h2>
+<h2>Release History &amp; EOL Months</h2>
 
 <table class="table table-striped">
   <thead class="thead-light">
@@ -60,8 +60,8 @@ version may be required.
       <th>Version</th>
       <th>Current minor</th>
       <th>Supported</th>
-      <th>First release date</th>
-      <th>EOL date</th>
+      <th>First release month</th>
+      <th>EOL month</th>
     </tr>
   </thead>
   <tbody>