Change customizing to customising in all variants.

Make the spelling of customizing follow the British (also Australian
since Richard Jones is from there) spelling. Non-native English
speakers will see a consistent spelling of the word. The filename is
still customizing.txt/html (US spelling) though.

Author: rouilj

doc/admin_guide.txt

@@ -371,7 +371,7 @@ interface. These changes are also trusted code that will be run
 when invoked.
 
 More secure CSPs can also be created. However because of the ability
-to customize the web interface, it is difficult to provide guidance.
+to customise the web interface, it is difficult to provide guidance.
 
 Dynamic CSP
 -----------

doc/customizing.txt

@@ -1,6 +1,6 @@
 .. meta::
     :description:
-        How to customize and extend the Roundup Issue
+        How to customise and extend the Roundup Issue
         Tracker. Includes many cookbook and how-to
         examples.
 
@@ -2376,7 +2376,7 @@ The `reference document`_ also has examples:
 Examples on the Wiki
 ====================
 
-Even more examples of customization have been contributed by
+Even more examples of customisation have been contributed by
 users. They can be found on the `wiki
 <https://wiki.roundup-tracker.org/CustomisationExamples>`_.
 

doc/index.txt

@@ -23,7 +23,7 @@ Contents
 
    user_guide
 
-   customizing
+   customising <customizing.txt>
    rest
    xmlrpc
    reference

doc/installation.txt

@@ -1182,7 +1182,7 @@ in config.ini should be ``https://tracker.example.org``.
 	# going though roundup
 	location /@@file/ {
 	  rewrite ^/@@file/(.*) /html/$1 break;
-	  # note that you can not use cache control (see customizing doc)
+	  # note that you can not use cache control (see customising doc)
           # in roundup to set the expires headers since we are
 	  # bypassing roundup. Consider using a map or different
 	  # location stanzas to vary the expiration times.  

doc/overview.txt

@@ -253,7 +253,7 @@ number of other items in the in the database.  A *multilink*
 property, for example, can be used to refer to related items
 or keyword categories relevant to an item.
 
-For Roundup, all items have four properties that are not customizable:
+For Roundup, all items have four properties that are not customisable:
 
 1. a *date* property named **creation**
 2. a *link* property named **creator**

doc/reference.txt

@@ -13,20 +13,20 @@ Roundup Reference
 
 .. admonition:: Welcome
 
-  This document used to be part of the `customization document`_.  The
-  customization document was getting large and unwieldy.  It was a
+  This document used to be part of the `customisation document`_.  The
+  customisation document was getting large and unwieldy.  It was a
   combination of examples and internal information that made finding
   information difficult. We often had questions on the mailing list that
-  were well answered in the customization document, but finding the info
+  were well answered in the customisation document, but finding the info
   was difficult.
 
   The documentation is slowly being reorganized using the `Diataxis
   framework`_. Help with the reorganization is welcome.
 
   This is the document you should look at for background on a tutorial
-  or how-to guide in the customization document.
+  or how-to guide in the customisation document.
 
-  .. _customization document: customizing.html
+  .. _customisation document: customizing.html
   .. _diataxis framework: https://diataxis.fr/
 
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
@@ -1553,7 +1553,7 @@ this you can:
 but with great power comes great responsibility.
 
 Interfaces.py has been around since the earliest releases of Roundup
-and used to be the main way to get a lot of customization done. In
+and used to be the main way to get a lot of customisation done. In
 modern Roundup, the extensions_ mechanism is used to `add actions
 <#defining-new-web-actions>`_ and `templating utilities`_. But there are
 places where interfaces.py is still useful. Note that the tracker

doc/rest.txt

@@ -1743,7 +1743,7 @@ seen.
 However the templating system can access the hyperdb directly which
 allows filtering to happen with admin privs escaping the standard
 permissions scheme. For example access to a user's roles should be
-limited to the user (read only) and an admin.  If you have customized
+limited to the user (read only) and an admin.  If you have customised
 your schema to implement `Restricting the list of
 users that are assignable to a task <customizing.html#restricting-the-list-of-users-that-are-assignable-to-a-task>`__
 so that only users with a

doc/upgrading-history.txt

@@ -82,7 +82,7 @@ Roundup used to allow certain HTML-Tags in OK- and Error-messages. Since
 these messages are passed via the URL (due to roundup redirecting after
 an edit), we did have security-issues (see issue2550724).
 
-If you have customized the OK or Error messages in your
+If you have customised the OK or Error messages in your
 roundup-installation and you were using features like bold or italic
 in the message, you will have to do without this highlighting and
 remove HTML tags from messages.
@@ -326,14 +326,14 @@ Migrating from 1.4.x to 1.4.9
 Customized MailGW Class
 -----------------------
 
-If you have customized the MailGW class in your tracker: The new MailGW
+If you have customised the MailGW class in your tracker: The new MailGW
 class opens the database for each message in the method handle_message
 (instance.open) instead of passing the opened database as a parameter to
 the MailGW constructor. The old handle_message has been renamed to
 _handle_message. The new method opens the database and wraps the call to
 the old method into a try/finally.
 
-Your customized MailGW class needs to mirror this behavior.
+Your customised MailGW class needs to mirror this behavior.
 
 Fix the "remove" button in issue files and messages lists
 ---------------------------------------------------------

doc/upgrading.txt

@@ -1204,7 +1204,7 @@ Statusauditor.py has been enhanced to prevent the status from changing
 to "chatting" until a second user (person) adds a message.  If you
 want this functionality, you need to merge the distributed
 statusauditor.py with your tracker's statusauditor.py. If you have not
-customized your tracker's statusauditor.py, copy the one from the
+customised your tracker's statusauditor.py, copy the one from the
 distibuted template. In addition to the python file, you also must
 copy/merge the distributed ``detectors/config.ini`` into your
 tracker's detectors directory. Most people can copy

doc/whatsnew-0.7.txt

@@ -137,7 +137,7 @@ Extending the cgi interface
 Before 0.7.0 adding or extending web actions was done by overriding or adding
 methods on the Client class. Though this approach still works to provide
 backwards compatibility, it is recommended you upgrade to the new approach, as
-described in the `Defining new web actions`__ section of the customization
+described in the `Defining new web actions`__ section of the customisation
 documentation. You might also want to take a look at the `Using an external
 password validation source`__ example.