From a37288c88706ac44754fad94024f98655184c4b4 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Thu, 22 Mar 2018 11:46:57 +0100 Subject: [PATCH] Tweak wording around minor rev upgrades Change "risk of upgrading" to "risk associated with upgrading". --- templates/support/versioning.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/support/versioning.html b/templates/support/versioning.html index 76342510..9c1b67b3 100644 --- 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

-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, security, and data corruption bugs to reduce the risk of upgrading. The community considers not upgrading to be riskier than upgrading. +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, security, and data corruption bugs to reduce the risk associated with upgrading. The community considers not upgrading to be riskier than upgrading.

-- 2.39.5