summaryrefslogtreecommitdiffstats
path: root/docs/html/upgrading.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/upgrading.html')
-rw-r--r--docs/html/upgrading.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/html/upgrading.html b/docs/html/upgrading.html
index 7919fa2f1..8371afa31 100644
--- a/docs/html/upgrading.html
+++ b/docs/html/upgrading.html
@@ -13,7 +13,7 @@ REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
-TITLE="Change Permission Customisation"
+TITLE="Change Permission Customization"
HREF="cust-change-permissions.html"><LINK
REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools"
@@ -92,12 +92,12 @@ CLASS="filename"
><P
>However, things get a bit more complicated if you've made
changes to Bugzilla's code. In this case, you may have to re-make or
- reapply those changes. One good method is to take a diff of your customised
+ reapply those changes. One good method is to take a diff of your customized
version against the original, so you can survey all that you've changed.
- Hopefully, templatisation will reduce the need for
+ Hopefully, templatization will reduce the need for
this in the future.</P
><P
->From version 2.8 onwards, Bugzilla databases can be automatically
+>From version 2.8 onward, Bugzilla databases can be automatically
carried forward during an upgrade. However, because the developers of
Bugzilla are constantly adding new
tables, columns and fields, you'll probably get SQL errors if you just
@@ -157,7 +157,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Change Permission Customisation</TD
+>Change Permission Customization</TD
><TD
WIDTH="34%"
ALIGN="center"