summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Pursehouse <david.pursehouse@sonymobile.com>2014-11-28 17:55:48 +0900
committerDavid Pursehouse <david.pursehouse@sonymobile.com>2014-11-28 17:56:04 +0900
commit58ac7a9e009b196ec23ca69f3ab971a26cf1ee0e (patch)
treed348d8be38b0b21e3e8ab8884f144be642b755de
parent7fe39b90b0ac3f0b6cdf416b22b5911dc758405d (diff)
Use US spelling in 2.9.2 release notes
-rw-r--r--ReleaseNotes/ReleaseNotes-2.9.2.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/ReleaseNotes/ReleaseNotes-2.9.2.txt b/ReleaseNotes/ReleaseNotes-2.9.2.txt
index 4fbd6b836a..b175546c8d 100644
--- a/ReleaseNotes/ReleaseNotes-2.9.2.txt
+++ b/ReleaseNotes/ReleaseNotes-2.9.2.txt
@@ -10,7 +10,7 @@ Important Notes
*WARNING:* There are no schema changes from
link:ReleaseNotes-2.9.1.html[2.9.1], but when upgrading from an existing site
-that was initialised with Gerrit version 2.6 or later the primary key column
+that was initialized with Gerrit version 2.6 or later the primary key column
order will be updated for some tables. It is therefore important to upgrade the
site with the `init` program, rather than only copying the .war file over the
existing one.
@@ -45,8 +45,8 @@ database tables. This caused poor performance for those SQL queries which rely
on using a prefix of the primary key column sequence in their WHERE conditions.
+
This version of gwtorm fixes the issue for new sites. For existing sites that
-were initialised with Gerrit version 2.6 or later, the primary key column
-order will be fixed during initialisation when upgrading to 2.9.2.
+were initialized with Gerrit version 2.6 or later, the primary key column
+order will be fixed during initialization when upgrading to 2.9.2.
Secondary Index
~~~~~~~~~~~~~~~