Tweak wording around minor rev upgrades

Change "risk of upgrading" to "risk associated with upgrading".

diff --git a/templates/support/versioning.html b/templates/support/versioning.html
index 763425100bc5ea6316912e1e21fff0d15d1142a1..9c1b67b32e3b46a1fbab6ed3c381a8bee1de1c00 100644 (file)
--- a/templates/support/versioning.html
+++ b/templates/support/versioning.html
@@ -17,7 +17,7 @@ Major releases usually change the internal format of system tables and data file
 </p>
 
 <p>
-Minor releases are numbered by increasing the last part of the version number.  Beginning with version 10, this is the second part of the version number, e.g. 10.0 to 10.1; for older versions this is the third part of the version number, e.g. 9.5.3 to 9.5.4. The PostgreSQL team only adds bug fixes to minor releases. All users should upgrade to the most recent minor release as soon as possible. While upgrades always have some risk, PostgreSQL minor releases fix only frequently-encountered, <a href="/support/security">security</a>, and data corruption bugs to reduce the risk of upgrading. <i>The community considers not upgrading to be riskier than upgrading</i>.
+Minor releases are numbered by increasing the last part of the version number.  Beginning with version 10, this is the second part of the version number, e.g. 10.0 to 10.1; for older versions this is the third part of the version number, e.g. 9.5.3 to 9.5.4. The PostgreSQL team only adds bug fixes to minor releases. All users should upgrade to the most recent minor release as soon as possible. While upgrades always have some risk, PostgreSQL minor releases fix only frequently-encountered, <a href="/support/security">security</a>, and data corruption bugs to reduce the risk associated with upgrading. <i>The community considers not upgrading to be riskier than upgrading</i>.
 </p>
 
 <p>