Merge pull request #5249 from tractorcow/pulls/3.2/customise

Standardise spelling of "customise"

docs/en/01_Tutorials/01_Building_A_Basic_Site.md

@@ -371,7 +371,7 @@ It always tries to use the most specific template in an inheritance chain.
 
 ### Creating a new template
 
-To create a new template layout, create a copy of *Page.ss* (found in *themes/simple/templates/Layout*) and call it *HomePage.ss*. If we flush the cache (*?flush=1*), SilverStripe should now be using *HomePage.ss* for the homepage, and *Page.ss* for the rest of the site. Now let's customize the *HomePage* template. 
+To create a new template layout, create a copy of *Page.ss* (found in *themes/simple/templates/Layout*) and call it *HomePage.ss*. If we flush the cache (*?flush=1*), SilverStripe should now be using *HomePage.ss* for the homepage, and *Page.ss* for the rest of the site. Now let's customise the *HomePage* template. 
 
 First, we don't need the breadcrumbs and the secondary menu for the homepage. Let's remove them:
 	:::ss
@@ -405,7 +405,7 @@ then descend into the *themes/simple/templates/Layout* folder, and will use *Pag
 
 ## Summary
 
-So far we have taken a look at the different areas and functionality within the pages area of the CMS. We have learnt about template variables, controls and if statements and used these to build a basic, but fully functional, website. We have also briefly covered page types, and looked at how they correspond to templates and sub-templates. Using this knowledge, we have customized our website's homepage design.
+So far we have taken a look at the different areas and functionality within the pages area of the CMS. We have learnt about template variables, controls and if statements and used these to build a basic, but fully functional, website. We have also briefly covered page types, and looked at how they correspond to templates and sub-templates. Using this knowledge, we have customised our website's homepage design.
 
 In the next tutorial, [Extending a Basic Site](/tutorials/extending_a_basic_site), we will explore page types on a deeper level, and look at customising our own page types to extend the functionality of SilverStripe.
 

docs/en/02_Developer_Guides/00_Model/05_Extending_DataObjects.md

@@ -12,7 +12,7 @@ data records.
 
 ## onBeforeWrite
 
-You can customize saving-behavior for each DataObject, e.g. for adding workflow or data customization. The function is 
+You can customise saving-behavior for each DataObject, e.g. for adding workflow or data customization. The function is 
 triggered when calling *write()* to save the object to the database. This includes saving a page in the CMS or altering 
 a `ModelAdmin` record.
 

docs/en/02_Developer_Guides/01_Templates/02_Common_Variables.md

@@ -380,7 +380,7 @@ By default, it uses the template defined in `cms/templates/BreadcrumbsTemplate.s
 	<% end_if %>
 
 <div class="info" markdown="1">
-To customize the markup that the `$Breadcrumbs` generates, copy `cms/templates/BreadcrumbsTemplate.ss` to 
+To customise the markup that the `$Breadcrumbs` generates, copy `cms/templates/BreadcrumbsTemplate.ss` to 
 `mysite/templates/BreadcrumbsTemplate.ss`, modify the newly copied template and flush your SilverStripe cache.
 </div>
 

docs/en/02_Developer_Guides/01_Templates/05_Template_Inheritance.md

@@ -5,7 +5,7 @@ summary: Override and extend module and core markup templates from your applicat
 
 Bundled within SilverStripe are default templates for any markup the framework outputs for things like Form templates,
 Emails or RSS Feeds. These templates are provided to make getting your site up and running quick with sensible defaults 
-but it's easy to replace and customize SilverStripe (and add-on's) by providing custom templates in your own 
+but it's easy to replace and customise SilverStripe (and add-on's) by providing custom templates in your own 
 `mysite/templates` folder or in your `themes/your_theme/templates` folder.
 
 Take for instance the `GenericEmail` template in SilverStripe. This is the HTML default template that any email created 

docs/en/02_Developer_Guides/01_Templates/06_Themes.md

@@ -75,7 +75,7 @@ themes
 
 If you want to submit your theme to the SilverStripe directory then check
 
-* You should ensure your templates are well structured, modular and commented so it's easy for other people to customize 
+* You should ensure your templates are well structured, modular and commented so it's easy for other people to customise 
 *  Templates should not contain text inside images and all images provided must be open source and not break any 
 copyright or license laws. This includes any icons your template uses.
 *  A theme does not include any PHP files. Only CSS, HTML, Images and javascript.

docs/en/02_Developer_Guides/01_Templates/index.md

@@ -1,6 +1,6 @@
 title: Templates and Views
 summary: This guide showcases the SilverStripe template engine and learn how to build your own themes.
-introduction: SilverStripe comes with it's own templating engine. This guide walks you through the features of the template engine, how to create custom templates and ways to customize your data output.
+introduction: SilverStripe comes with it's own templating engine. This guide walks you through the features of the template engine, how to create custom templates and ways to customise your data output.
 
 Most of what will be public on your website comes from template files that are defined in SilverStripe. Either in the
 core framework, the modules or themes you install, and your own custom templates. 

docs/en/02_Developer_Guides/02_Controllers/01_Introduction.md

@@ -109,7 +109,7 @@ Action methods can return one of four main things:
 	 * We can render HTML and leave SilverStripe to set the response code and body.
 	 */
 	public function htmlaction() {
-		return $this->customize(new ArrayData(array(
+		return $this->customise(new ArrayData(array(
 			'Title' => 'HTML Action'
 		)))->renderWith('MyCustomTemplate');
 	}

docs/en/02_Developer_Guides/03_Forms/00_Introduction.md

@@ -153,7 +153,7 @@ information on the CMS interface.
 
 ## Modifying FormFields
 
-Each [api:FormField] subclass has a number of methods you can call on it to customize its' behavior or HTML markup. The
+Each [api:FormField] subclass has a number of methods you can call on it to customise its' behavior or HTML markup. The
 default `FormField` object has several methods for doing common operations. 
 
 <div class="notice" markdown="1">

docs/en/02_Developer_Guides/03_Forms/Field_types/04_GridField.md

@@ -232,7 +232,7 @@ database.
 ## GridFieldDetailForm
 
 The `GridFieldDetailForm` component drives the record viewing and editing form. It takes its' fields from 
-`DataObject->getCMSFields()` method but can be customized to accept different fields via the 
+`DataObject->getCMSFields()` method but can be customised to accept different fields via the 
 [api:GridFieldDetailForm::setFields()] method.
 
 	:::php

docs/en/02_Developer_Guides/05_Extending/01_Extensions.md

@@ -113,7 +113,7 @@ we added a `SayHi` method which is unique to our extension.
 ## Modifying Existing Methods
 
 If the `Extension` needs to modify an existing method it's a little trickier. It requires that the method you want to
-customize has provided an *Extension Hook* in the place where you want to modify the data. An *Extension Hook* is done 
+customise has provided an *Extension Hook* in the place where you want to modify the data. An *Extension Hook* is done 
 through the [api:Object::extend()] method.
 
 **framework/security/Member.php**

docs/en/02_Developer_Guides/06_Testing/00_Unit_Testing.md

@@ -96,7 +96,7 @@ environments. If for some reason you don't have access to the command line, you
 
 ### Via the CLI
 
-The [sake](../cli) executable that comes with SilverStripe can trigger a customized [api:TestRunner] class that 
+The [sake](../cli) executable that comes with SilverStripe can trigger a customised [api:TestRunner] class that 
 handles the PHPUnit configuration and output formatting. While the custom test runner a handy tool, it's also more 
 limited than using `phpunit` directly, particularly around formatting test output.
 
@@ -176,7 +176,7 @@ databases on your machine. To get rid of them is a call to `http://yoursite.com/
 ## Custom PHPUnit Configuration
 
 The `phpunit` executable can be configured by command line arguments or through an XML file. SilverStripe comes with a 
-default `phpunit.xml.dist` that you can use as a starting point. Copy the file into `phpunit.xml` and customize to your 
+default `phpunit.xml.dist` that you can use as a starting point. Copy the file into `phpunit.xml` and customise to your 
 needs.
 
 **phpunit.xml**

docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md

@@ -231,7 +231,7 @@ After we've created this object in the factory, `getId` is used to retrieve it b
 
 ### Default Properties
 
-Blueprints can be overwritten in order to customize their behavior. For example, if a Fixture does not provide a Team
+Blueprints can be overwritten in order to customise their behavior. For example, if a Fixture does not provide a Team
 name, we can set the default to be `Unknown Team`.
 
 	:::php

docs/en/02_Developer_Guides/06_Testing/index.md

@@ -41,7 +41,7 @@ of course this information can be version controlled and shared with other team
 **Note: This doesn't apply for running tests through the "sake" wrapper**
 
 SilverStripe comes with a default `phpunit.xml.dist` that you can use as a starting point. Copy the file into a new
-`phpunit.xml` and customize to your needs - PHPUnit will auto-detect its existence, and prioritize it over the default
+`phpunit.xml` and customise to your needs - PHPUnit will auto-detect its existence, and prioritize it over the default
 file.
 
 There's nothing stopping you from creating multiple XML files (see the `--configuration` flag in
@@ -99,7 +99,7 @@ All command-line arguments are documented on
 
 ### Via the "sake" Wrapper on Command Line
 
-The [sake](/developer_guides/cli/) executable that comes with SilverStripe can trigger a customized
+The [sake](/developer_guides/cli/) executable that comes with SilverStripe can trigger a customised
 [api:TestRunner] class that handles the PHPUnit configuration and output formatting.
 While the custom test runner a handy tool, its also more limited than using `phpunit` directly,
 particularly around formatting test output.

docs/en/02_Developer_Guides/09_Security/04_Secure_Coding.md

@@ -156,7 +156,7 @@ passing data through, escaping should happen at the end of the chain.
 	  }
 	}
 
-This might not be applicable in all cases - especially if you are building an API thats likely to be customized. If
+This might not be applicable in all cases - especially if you are building an API thats likely to be customised. If
 you're passing unescaped data, make sure to be explicit about it by writing *phpdoc*-documentation and *prefixing* your
 variables ($RAW_data instead of $data).
 

docs/en/02_Developer_Guides/10_Email/index.md

@@ -3,7 +3,7 @@ summary: Send HTML and plain text email from your SilverStripe application.
 # Email
 
 Creating and sending email in SilverStripe is done through the [api:Email] and [api:Mailer] classes. This document 
-covers how to create an `Email` instance, customize it with a HTML template, then send it through a custom `Mailer`.
+covers how to create an `Email` instance, customise it with a HTML template, then send it through a custom `Mailer`.
 
 ## Configuration
 
@@ -32,7 +32,7 @@ to `*text*`).
 
 <div class="info" markdown="1">
 The default HTML template for emails is named `GenericEmail` and is located in `framework/templates/email/`. To 
-customize this template, copy it to the `mysite/templates/Email/` folder or use `setTemplate` when you create the 
+customise this template, copy it to the `mysite/templates/Email/` folder or use `setTemplate` when you create the 
 `Email` instance.
 </div>
 

docs/en/02_Developer_Guides/11_Integration/00_CSV_Import.md

@@ -5,7 +5,7 @@
 CSV import can be easily achieved through PHP's built-in `fgetcsv()` method,
 but this method doesn't know anything about your datamodel. In SilverStripe,
 this can be handled through the a specialized CSV importer class that can
-be customized to fit your data.
+be customised to fit your data.
 
 ## The CsvBulkLoader class
 
@@ -63,7 +63,7 @@ below the search form on the left.
 
 ## Import through a custom controller
 
-You can have more customized logic and interface feedback through a custom controller. 
+You can have more customised logic and interface feedback through a custom controller. 
 Let's create a simple upload form (which is used for `MyDataObject` instances). 
 You'll need to add a route to your controller to make it accessible via URL 
 (see [director](/reference/director)).

docs/en/02_Developer_Guides/11_Integration/02_RSSFeed.md

@@ -144,7 +144,7 @@ Then in our controller, we add a new action which returns a the XML list of `Pla
 ### Customizing the RSS Feed template
 
 The default template used for XML view is `framework/templates/RSSFeed.ss`. This template displays titles and links to 
-the object. To customize the XML produced use `setTemplate`.
+the object. To customise the XML produced use `setTemplate`.
 
 Say from that last example we want to include the Players Team in the XML feed we might create the following XML file.
 

docs/en/02_Developer_Guides/11_Integration/How_Tos/Import_CSV_through_a_Controller.md

@@ -2,7 +2,7 @@ title: Import CSV Data through a Controller
 
 # Import CSV Data through a Controller
 
-You can have more customized logic and interface feedback through a custom controller. Let's create a simple upload 
+You can have more customised logic and interface feedback through a custom controller. Let's create a simple upload 
 form (which is used for `MyDataObject` instances). You can access it through 
 `http://yoursite.com/MyController/?flush=all`.
 

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/01_ModelAdmin.md

@@ -169,7 +169,7 @@ model class, where you can add or remove columns. To change the title, use [api:
 
 The results list are retrieved from [api:SearchContext::getResults()], based on the parameters passed through the search
 form. If no search parameters are given, the results will show every record. Results are a [api:DataList] instance, so
-can be customized by additional SQL filters, joins.
+can be customised by additional SQL filters, joins.
 
 For example, we might want to exclude all products without prices in our sample `MyAdmin` implementation.
 
@@ -192,7 +192,7 @@ For example, we might want to exclude all products without prices in our sample
 		}
 	}
 
-You can also customize the search behavior directly on your `ModelAdmin` instance. For example, we might want to have a
+You can also customise the search behavior directly on your `ModelAdmin` instance. For example, we might want to have a
 checkbox which limits search results to expensive products (over $100).
 
 **mysite/code/MyAdmin.php**
@@ -300,7 +300,7 @@ with a more specific importer implementation, use the [api:ModelAdmin::$model_im
 Export is available as a CSV format through a button at the end of a results list. You can also export search results.
 This is handled through the [api:GridFieldExportButton] component.
 
-To customize the exported columns, create a new method called `getExportFields` in your `ModelAdmin`:
+To customise the exported columns, create a new method called `getExportFields` in your `ModelAdmin`:
 
 	:::php
 	<?php

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/05_Typography.md

@@ -3,7 +3,7 @@ summary: Add custom CSS properties to the rich-text editor.
 
 # WYSIWYG Styles
 
-SilverStripe lets you customize the style of content in the CMS. This is done by setting up a CSS file called
+SilverStripe lets you customise the style of content in the CMS. This is done by setting up a CSS file called
 `editor.css` in either your theme or in your `mysite` folder. This is set through
 
 	:::php

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/06_Javascript_Development.md

@@ -168,7 +168,7 @@ consideration, we provide a library for entwineUI style programming. In entwineU
 objects. entwine extends this concept beyond what is provided by other libraries to provide a very easy to use system
 with class like, ploymorphic, namespaced properties."
 
-Use jQuery.entwine when your code is likely to be customized by others, for example for most work in the CMS interface.
+Use jQuery.entwine when your code is likely to be customised by others, for example for most work in the CMS interface.
 It is also suited for more complex applications beyond a single-purpose plugin.
 
 Example: Highlighter

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/How_Tos/Customise_CMS_Menu.md

@@ -1,4 +1,4 @@
-# How to customize the CMS Menu
+# How to customise the CMS Menu
 
 ## Adding an administration panel
 

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/How_Tos/Customise_CMS_Tree.md

@@ -1,4 +1,4 @@
-# How to customize the CMS tree
+# How to customise the CMS tree
 
 ## Overview
 

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/How_Tos/Extend_CMS_Interface.md

@@ -200,7 +200,7 @@ how-to.
 
 ## Summary
 
-In a few lines of code, we've customized the look and feel of the CMS.
+In a few lines of code, we've customised the look and feel of the CMS.
 
 While this example is only scratching the surface, it includes most building
 blocks and concepts for more complex extensions as well.

docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/How_Tos/Extending_An_Existing_ModelAdmin.md

@@ -1,6 +1,6 @@
 ## Extending existing ModelAdmin
 
-Sometimes you'll work with ModelAdmins from other modules. To customize these interfaces, you can always subclass. But there's
+Sometimes you'll work with ModelAdmins from other modules. To customise these interfaces, you can always subclass. But there's
 also another tool at your disposal: The [api:Extension] API.
 
 	:::php

docs/en/04_Changelogs/2.3.0.md

@@ -1154,7 +1154,7 @@ See http://open.silverstripe.com/changeset/69688
  * ![rev:63652] Added Controller->render($params) as a shortcut for Controller->customise($params)->renderWith(array('MyTemplate','MySubTemplate')) - templates are auto-detected by Controller->getViewer() and Controller->getAction()
  * ![rev:63651] Consistently allowing for $restrictFields and $fieldClasses parameters passed to DataObject->scaffoldFormFields(), DataObject->scaffoldSearchFields(), DataObject->scaffoldCMSFields()
  * ![rev:63650] Added RequestHandlingTest->testNestedBase()
- * ![rev:63648] Added support for customize parameters to ViewableData->renderWith() to avoid unnecessary chaining ($this->customize($params)->renderWith($template))
+ * ![rev:63648] Added support for customise parameters to ViewableData->renderWith() to avoid unnecessary chaining ($this->customise($params)->renderWith($template))
  * ![rev:63633] Better i18n for TableField and ComplexTableField
  * ![rev:63632] Using DataObject->Title for has_one dropdowns generated in DataObject->scaffoldFormFields()
  * ![rev:63630] Added DataObject->fieldLabel() and removed $fieldname parameter from DataObject->fieldLabels($fieldName) to simplify overloading of fieldLabels() for i18n
@@ -1788,7 +1788,7 @@ See http://open.silverstripe.com/changeset/69688
  * ![rev:64863] Changed default # of rows on HTMLEditorField from 15 to 30
  * ![rev:64862] Fixed TinyMCE stylihg
  * ![rev:64839] Fixed CMS uploading
- * ![rev:64814] call $this->extend('updateFieldLabels', $labels) in FieldLabels() to get its decorator's customized field labels
+ * ![rev:64814] call $this->extend('updateFieldLabels', $labels) in FieldLabels() to get its decorator's customised field labels
  * ![rev:64778] Removed scrubbing of the HTML
  * ![rev:64768] #2957 - Fixed entity decoding in Convert::html2raw
  * ![rev:64760] Fixed bug in tinymce_ssbuttons plugin inclusion

docs/en/04_Changelogs/2.4.1.md

@@ -206,7 +206,7 @@ existing pages when their title is changed.
  * [rev:106200] added prefix and suffix support to !ContextSummary
  * [rev:106194] Prevent image search queries all images in the site initially when the page is loaded
  * [rev:106178] Enable switch between legacy image search and new version
- * [rev:106118] added setRows() and setColumns() to customize the size of the textarea field outside of the controller
+ * [rev:106118] added setRows() and setColumns() to customise the size of the textarea field outside of the controller
  * [rev:105890] Added method for $this->request->latestParam() backwards compatibility with Director::urlParam()
  * [rev:105732] Ability to hide form by className or for the whole !ModelAdmin
  * [rev:105712] Added !MySQLDatabaseConfigurationHelper::getDatabaseVersion() which abstracts the version number away from the version check the installer requires

docs/en/04_Changelogs/2.4.2.md

@@ -2,7 +2,7 @@
 
  * Fixed a security issue where pages in draft mode might be visible to unauthenticated users
  * Fixed a security issue where users with access to admin/security (but limited privileges) can take over a known administrator account by changing its password
- * Allow Apache webserver to customized error pages in HTML, rather than Apache default styling
+ * Allow Apache webserver to customised error pages in HTML, rather than Apache default styling
  * Testing harness improvements: More verbose testing output, fixed coverage report generation
  * Fixed installer logic for SQLite database drivers
  * All unit tests pass on Windows OS/SQL Server

docs/en/04_Changelogs/3.0.0.md

@@ -348,7 +348,7 @@ See the [template reference](/developer_guides/templates) for a list of method r
 
 Most aspects of the interface have been redesigned, which necessitated a substantial
 redevelopment of the underlying logic and presentation. 
-If you have customized the admin interface in any way, please review
+If you have customised the admin interface in any way, please review
 the detailed changelog for this release. Many interface components have changed completely,
 unfortunately there is no clear upgrade path for every interface detail.
 As a starting point, have a look at the new templates in `cms/templates`

docs/en/04_Changelogs/3.1.0.md

@@ -421,7 +421,7 @@ you can enable those warnings and future-proof your code already.
    have custom code relying on these two libraries, please update your code to include the files yourself
  * Removed `SiteTree.MetaKeywords` since they are irrelevant in terms of SEO
    ([seomoz article](http://www.mattcutts.com/blog/keywords-meta-tag-in-web-search/)) and general page informancy
- * Removed `SiteTree.MetaTitle` as a means to customize the window title, use `SiteTree.Title` instead
+ * Removed `SiteTree.MetaTitle` as a means to customise the window title, use `SiteTree.Title` instead
  * Deprecated `Profiler` class, use third-party solutions like [xhprof](https://github.com/facebook/xhprof/)
  * Removed defunct or unnecessary debug GET parameters: 
    `debug_profile`, `debug_memory`, `profile_trace`, `debug_javascript`, `debug_behaviour`

docs/en/04_Changelogs/3.2.0.md

@@ -826,7 +826,7 @@ In order to remove the new "archive" action and restore the old "delete" action
  * 2015-07-10 [560f9a6](https://github.com/silverstripe/silverstripe-framework/commit/560f9a6e39df4f09dfe4bed5978f6dcddc0bb299) respect custom attributes on OptionsetField and CheckboxSetField (Damian Mooyman)
  * 2015-06-15 [f3e1472](https://github.com/silverstripe/silverstripe-cms/commit/f3e1472493b15758c67bb2c8814bc28765eac401) Revert DataObject::validate to 3.1 method signature (protected) (Damian Mooyman)
  * 2015-06-15 [58cc3da](https://github.com/silverstripe/silverstripe-framework/commit/58cc3da8d8005d6a367d88fb7c5d41c96dd8946f) Revert DataObject::validate to 3.1 method signature (protected) (Damian Mooyman)
- * 2015-06-13 [e766658](https://github.com/silverstripe/silverstripe-framework/commit/e766658ee3b9e70988b79d99d75124857f2a7ccc) Allow HTTP Cache Headers to be customized (Jeremy Shipman)
+ * 2015-06-13 [e766658](https://github.com/silverstripe/silverstripe-framework/commit/e766658ee3b9e70988b79d99d75124857f2a7ccc) Allow HTTP Cache Headers to be customised (Jeremy Shipman)
  * 2015-06-12 [8389260](https://github.com/silverstripe/silverstripe-framework/commit/838926085cac00ec65ee5aecb67e6102ea8b6f20) and renamed image functions (Jonathon Menz)
  * 2015-06-09 [914d734](https://github.com/silverstripe/silverstripe-framework/commit/914d734df004947eb869de2abb6fb2fc463be574) Disable deprecation notices by default (Damian Mooyman)
  * 2015-06-09 [a8ace75](https://github.com/silverstripe/silverstripe-framework/commit/a8ace7534194b5e1a636c96eca4607d08726dfeb) Support for multiple HTMLEditorConfig per page (Damian Mooyman)

docs/en/04_Changelogs/alpha/2.4.0-alpha1.md

@@ -43,7 +43,7 @@
  * [rev:88474] Refactored ViewableData. The main changes are:
  * [rev:88472] Added the Shortcode API (ShortcodeParser) to allow you to replace simple BBCode-like tags in a string with the results of a callback. From: Andrew Short
  * [rev:88468] Added utility methods to enable and disable nested URLs to SiteTree. From: Andrew Short
- * [rev:88104] added extend() call to enable FieldHolder() html to be customized via extensions.
+ * [rev:88104] added extend() call to enable FieldHolder() html to be customised via extensions.
  * [rev:85789] Added Widget_Controller class to enable nested forms within Wiget class.
 
 

docs/en/04_Changelogs/alpha/3.0.0-alpha1.md

@@ -222,7 +222,7 @@ See [3.0.0 upgrading guide](../3.0.0) for further details.
  * 2011-07-05 [a1b8698](https://github.com/silverstripe/sapphire/commit/a1b8698) Removed '.LeftAndMain' selector from rules in order to avoid DOM hierarchy confusion (.LeftAndMain contains .cms-content vs .LeftAndMain equals .cms-content) (Ingo Schommer)
  * 2011-07-05 [19b9edb](https://github.com/silverstripe/sapphire/commit/19b9edb) Clearer CSS classes in CMS controller templates. Fixed JS loading of ModelAdmin panels. Added $BaseCSSClasses to content templates in order to support partial template loads through ajax (instead of relying on stale CSS classes on the <body> tag). Leaving $BaseCSSClasses in LeftAndMain.ss base template for legacy reasons. (Ingo Schommer)
  * 2011-07-05 [38db63c](https://github.com/silverstripe/silverstripe-cms/commit/38db63c) Clearer CSS classes in CMS controller templates, added $BaseCSSClasses to content templates in order to support partial template loads through ajax (instead of relying on stale CSS classes on the <body> tag) (Ingo Schommer)
- * 2011-07-04 [1dc9457](https://github.com/silverstripe/sapphire/commit/1dc9457) Using LeftAndMain->BaseCSSClasses() instead of ViewableData->CSSClasses() to avoid conflicts with customized controller objects (e.g. ModelAdmin_RecordController->edit()) (Ingo Schommer)
+ * 2011-07-04 [1dc9457](https://github.com/silverstripe/sapphire/commit/1dc9457) Using LeftAndMain->BaseCSSClasses() instead of ViewableData->CSSClasses() to avoid conflicts with customised controller objects (e.g. ModelAdmin_RecordController->edit()) (Ingo Schommer)
  * 2011-07-04 [c4a99df](https://github.com/silverstripe/silverstripe-cms/commit/c4a99df) Redirecting page links in CMSPagesController to CMSPageEditController (admin/pages/show/99 to admin/page/show/99) (Ingo Schommer)
  * 2011-07-04 [2e9ea1d](https://github.com/silverstripe/sapphire/commit/2e9ea1d) Disable ping until jQuery.entwine _super() confusion is resolved (Ingo Schommer)
  * 2011-06-25 [ebb1e0f](https://github.com/silverstripe/silverstripe-cms/commit/ebb1e0f) Additional HTML for tree styling in SiteTree->getTreeTitle() (Ed)

docs/en/04_Changelogs/beta/2.4.0-beta2.md

@@ -488,7 +488,7 @@
  * [rev:99112] migrated headers in SiteConfig to i18n'd (from r86429)
  * [rev:99111] Localized File->uploadMetadataFields()
  * [rev:99110] Documentation
- * [rev:99099] ability to customize the text that comes out of Member->Title
+ * [rev:99099] ability to customise the text that comes out of Member->Title
  * [rev:99099] updated workflow reports (from r96352)
  * [rev:99098] Added Requirements for SilverStripeNavigator (see r99080)
  * [rev:99097] Added Requirements for SilverStripeNavigator (see r99080)

docs/en/04_Changelogs/beta/3.2.0-beta1.md

@@ -789,7 +789,7 @@ In order to remove the new "archive" action and restore the old "delete" action
 
  * 2015-06-16 [f3e1472](https://github.com/silverstripe/silverstripe-cms/commit/f3e1472) Revert DataObject::validate to 3.1 method signature (protected) (Damian Mooyman)
  * 2015-06-16 [58cc3da](https://github.com/silverstripe/sapphire/commit/58cc3da) Revert DataObject::validate to 3.1 method signature (protected) (Damian Mooyman)
- * 2015-06-13 [e766658](https://github.com/silverstripe/sapphire/commit/e766658) Allow HTTP Cache Headers to be customized (Jeremy Shipman)
+ * 2015-06-13 [e766658](https://github.com/silverstripe/sapphire/commit/e766658) Allow HTTP Cache Headers to be customised (Jeremy Shipman)
  * 2015-06-12 [8389260](https://github.com/silverstripe/sapphire/commit/8389260) New and renamed image functions (Jonathon Menz)
  * 2015-06-09 [a8ace75](https://github.com/silverstripe/sapphire/commit/a8ace75) Support for multiple HTMLEditorConfig per page (Damian Mooyman)
  * 2015-05-15 [b169823](https://github.com/silverstripe/silverstripe-cms/commit/b169823) Deprecate delete in favour of archive Remove "delete from live" duplicate action in favour of existing "unpublish" which is more consistent with current terminology Add pop-up verification to destructive actions Fix bug preventing side-by-side preview of archived pages Fix bug in reporting publishing of error pages Restoring a page without an available parent will restore to root (Damian Mooyman)

docs/en/04_Changelogs/pr/3.0.0-pr1.md

@@ -297,7 +297,7 @@ See [3.0.0 upgrading guide](../3.0.0)
  * 2009-11-21 [5f8a164](https://github.com/silverstripe/silverstripe-cms/commit/5f8a164) Defaulting to action_save button in ajaxSubmit() javascript logic in CMS form ENHANCEMENT Making ajax options overrideable in ajaxSubmit() javascript logic in CMS form (Ingo Schommer)
  * 2009-11-21 [b6dc2de](https://github.com/silverstripe/silverstripe-cms/commit/b6dc2de) Added initial implementation of jquery-changetracker as a replacement for the existing ChangeTracker behaviour/prototype javascript class (Ingo Schommer)
  * 2009-11-21 [bc2cad4](https://github.com/silverstripe/silverstripe-cms/commit/bc2cad4) Floating tinymce toolbar icons in CMS to allow for smaller widths without having tinymce hide the tabset scrollbars (Ingo Schommer)
- * 2009-11-21 [c2d24f9](https://github.com/silverstripe/silverstripe-cms/commit/c2d24f9) Changed CMSMain and LeftAndMain form submissions to return raw HTML instead of using FormResponse logic and evaluated javascript. This allows a more customizeable UI layer that is decoupled from the serverside logic. Any state changes should be propagated through the form itself. ENHANCEMENT Using new 'X-STATUS' HTTP response header for CMS form responses, as it is more robust for submitting variable length strings than the original 'Status' header. The status is evaluated in LeftAndMain.EditForm.js API CHANGE Removed CMSMain->tellBrowserAboutPublicationChange(), LeftAndMain->returnItemToUser(), LeftAndMain->getActionUpdateJS(), LeftAndMain->addTreeNodeJS(), LeftAndMain->deleteTreeNodeJS(). Use javascript to respond to state changes API CHANGE Removed CMSForm and CMSRightForm javascript classes, superseded by LeftAndMain.EditForm.js ENHANCEMENT Removed custom change detection in LeftAndMain->save(), this should be handled by DataObject->write() ENHANCEMENT Removed switch in LeftAndMain->save() which doesnt process saving if the record hasn't been altered, to simplify the saving logic ENHANCEMENT Removed custom add/remove tree node logic in LeftAndMain->save() which was retrieving state from DataObjectLog. This was never actively used, and should be handled by custom clientside logic. (Ingo Schommer)
+ * 2009-11-21 [c2d24f9](https://github.com/silverstripe/silverstripe-cms/commit/c2d24f9) Changed CMSMain and LeftAndMain form submissions to return raw HTML instead of using FormResponse logic and evaluated javascript. This allows a more customiseable UI layer that is decoupled from the serverside logic. Any state changes should be propagated through the form itself. ENHANCEMENT Using new 'X-STATUS' HTTP response header for CMS form responses, as it is more robust for submitting variable length strings than the original 'Status' header. The status is evaluated in LeftAndMain.EditForm.js API CHANGE Removed CMSMain->tellBrowserAboutPublicationChange(), LeftAndMain->returnItemToUser(), LeftAndMain->getActionUpdateJS(), LeftAndMain->addTreeNodeJS(), LeftAndMain->deleteTreeNodeJS(). Use javascript to respond to state changes API CHANGE Removed CMSForm and CMSRightForm javascript classes, superseded by LeftAndMain.EditForm.js ENHANCEMENT Removed custom change detection in LeftAndMain->save(), this should be handled by DataObject->write() ENHANCEMENT Removed switch in LeftAndMain->save() which doesnt process saving if the record hasn't been altered, to simplify the saving logic ENHANCEMENT Removed custom add/remove tree node logic in LeftAndMain->save() which was retrieving state from DataObjectLog. This was never actively used, and should be handled by custom clientside logic. (Ingo Schommer)
  * 2009-11-21 [41c1c49](https://github.com/silverstripe/silverstripe-cms/commit/41c1c49) Better response handling in LeftAndMain.EditForm BUGFIX Fixed event cancellation in LeftAndMain.EditForm javascript buttons (Ingo Schommer)
  * 2009-11-21 [87a6e33](https://github.com/silverstripe/silverstripe-cms/commit/87a6e33) Disabling validator in CMSMain->getCMSFields() unless its explicitly set through SiteTree->getCMSValidator(). We don't fully support validation in the CMS (yet), and it causes unnecessary bloat in the document body for now. (Ingo Schommer)
  * 2009-11-21 [021c8d4](https://github.com/silverstripe/silverstripe-cms/commit/021c8d4) Initialize the east layout panel in CMSMain.js as hidden, so users can't toggle it without going through tinyMCE buttons (Ingo Schommer)
@@ -320,7 +320,7 @@ See [3.0.0 upgrading guide](../3.0.0)
  * 2009-11-21 [d95f867](https://github.com/silverstripe/sapphire/commit/d95f867) Triggering jQuery events in TreeSelectorField.js in preparation to switching the tree logic to jQuery. This prevents developers from using the soon-to-be-deprecated Observable prototype (Ingo Schommer)
  * 2009-11-21 [28109df](https://github.com/silverstripe/sapphire/commit/28109df) Removed UniqueField.js dependency to CMS-related statusMessage() javascript class, and using jQuery even triggers instead (Ingo Schommer)
  * 2009-11-21 [0b25cb9](https://github.com/silverstripe/sapphire/commit/0b25cb9) Removed UpdateURL.js, moved logic to CMSMain.js ENHANCEMENT Using plain TextField for URLSegment in SiteTree->getCMSFields(), and using custom logic in CMSMain.js. The field didn't have any serverside validation anyway, and the remaining parts are quite custom (Ingo Schommer)
- * 2009-11-21 [f60e94b](https://github.com/silverstripe/sapphire/commit/f60e94b) Using native jQuery.getScript() in customized jQuery.ondemand plugin. Moved processDemandHeaders() into jQuery namespace, and adjusted customized prototype.js library (Ingo Schommer)
+ * 2009-11-21 [f60e94b](https://github.com/silverstripe/sapphire/commit/f60e94b) Using native jQuery.getScript() in customised jQuery.ondemand plugin. Moved processDemandHeaders() into jQuery namespace, and adjusted customised prototype.js library (Ingo Schommer)
  * 2009-11-21 [0abe472](https://github.com/silverstripe/sapphire/commit/0abe472) Added SiteTree->getStageURLSegment() and SiteTree->getLiveURLSegment() to allow auto-population in the CMS edit form. This information is necessary to keep clientside UI state consistent. (Ingo Schommer)
  * 2009-11-21 [9ecd359](https://github.com/silverstripe/sapphire/commit/9ecd359) Setting proper text/javascript content-type in FormResponse so clientside ajax-handling knows how to deal with it. (Ingo Schommer)
  * 2009-11-21 [beb4efe](https://github.com/silverstripe/sapphire/commit/beb4efe) Disabling form validation for right-panel forms in CMS in HtmlEditorField. None of the fields have validation attached to them at the moment, so the generic validation output is unnecessary bloat. (Ingo Schommer)
@@ -1238,7 +1238,7 @@ See [3.0.0 upgrading guide](../3.0.0)
  * 2010-04-14 [4703aa6](https://github.com/silverstripe/sapphire/commit/4703aa6) Fixed SapphireTest->logInWithPermission() spelling (from r99491) (Ingo Schommer)
  * 2010-04-14 [76d57b6](https://github.com/silverstripe/sapphire/commit/76d57b6) Temporarily disabled nested url specific cases inTranslatableTest->testAlternateGetByLink(), unclear functionality requirements (from r99350) (Ingo Schommer)
  * 2010-04-14 [e99d56d](https://github.com/silverstripe/sapphire/commit/e99d56d) Localized File->uploadMetadataFields() (from r99111) (Ingo Schommer)
- * 2010-04-14 [ae7439a](https://github.com/silverstripe/sapphire/commit/ae7439a) ability to customize the text that comes out of Member->Title MINOR updated workflow reports (from r96352) (from r99099) (Ingo Schommer)
+ * 2010-04-14 [ae7439a](https://github.com/silverstripe/sapphire/commit/ae7439a) ability to customise the text that comes out of Member->Title MINOR updated workflow reports (from r96352) (from r99099) (Ingo Schommer)
  * 2010-04-14 [3dc4486](https://github.com/silverstripe/sapphire/commit/3dc4486) Added Requirements for SilverStripeNavigator (see r99080) (from r99097) (Ingo Schommer)
  * 2010-04-14 [ec983ae](https://github.com/silverstripe/sapphire/commit/ec983ae) make static caching smarter around cacheSubdirs (from r99076) (Ingo Schommer)
  * 2010-04-14 [7c057cb](https://github.com/silverstripe/sapphire/commit/7c057cb) adjustments to ensure that the cached permissions were actually hit (from r98835) (from r99068) (Ingo Schommer)
@@ -1398,7 +1398,7 @@ See [3.0.0 upgrading guide](../3.0.0)
  * 2009-11-21 [e3a51fe](https://github.com/silverstripe/silverstripe-cms/commit/e3a51fe) Bugfixes for SWFUpload (Ingo Schommer)
  * 2009-11-21 [394e0c0](https://github.com/silverstripe/silverstripe-cms/commit/394e0c0) Removed cms/thirdparty/swfupload, moved to sapphire/thirdparty (Ingo Schommer)
  * 2009-11-21 [683dfa9](https://github.com/silverstripe/silverstripe-cms/commit/683dfa9) Styling of side reports and tree area in CMS (Ingo Schommer)
- * 2009-11-21 [1bc268e](https://github.com/silverstripe/silverstripe-cms/commit/1bc268e) Only fetching EditForm in LeftAndMain->show() if called by ajax, the customize() call for non-ajax views confuses the renderer otherwise (Ingo Schommer)
+ * 2009-11-21 [1bc268e](https://github.com/silverstripe/silverstripe-cms/commit/1bc268e) Only fetching EditForm in LeftAndMain->show() if called by ajax, the customise() call for non-ajax views confuses the renderer otherwise (Ingo Schommer)
  * 2009-11-21 [32d6342](https://github.com/silverstripe/silverstripe-cms/commit/32d6342) Fixed merge errors (Ingo Schommer)
  * 2009-11-21 [8f92ee3](https://github.com/silverstripe/silverstripe-cms/commit/8f92ee3) Fixed Requirements paths in LeftAndMain.php (Ingo Schommer)
  * 2009-11-21 [c189230](https://github.com/silverstripe/silverstripe-cms/commit/c189230) Fixed merge error (Ingo Schommer)
@@ -1561,8 +1561,8 @@ See [3.0.0 upgrading guide](../3.0.0)
  * 2009-11-21 [9889ba5](https://github.com/silverstripe/sapphire/commit/9889ba5) Moved Function.prototype.create from tree.js into behaviour.js (Ingo Schommer)
  * 2009-11-21 [146979b](https://github.com/silverstripe/sapphire/commit/146979b) Documentation and code formatting for jquery.ondemand.js (Ingo Schommer)
  * 2009-11-21 [073ebbe](https://github.com/silverstripe/sapphire/commit/073ebbe) Moved sapphire/javascript/core to sapphire/javascript/jquery-ondemand to fit with patterns in sapphire/thirdparty (Ingo Schommer)
- * 2009-11-21 [fd1cb12](https://github.com/silverstripe/sapphire/commit/fd1cb12) Removed unused sapphire/thirdparty/jquery.ondemand.js library, we use a heavily customized version in sapphire/javascript/jquery-ondemand instead (Ingo Schommer)
- * 2009-11-21 [5d6233a](https://github.com/silverstripe/sapphire/commit/5d6233a) Indentation in customized jquery.ondemand.js (Ingo Schommer)
+ * 2009-11-21 [fd1cb12](https://github.com/silverstripe/sapphire/commit/fd1cb12) Removed unused sapphire/thirdparty/jquery.ondemand.js library, we use a heavily customised version in sapphire/javascript/jquery-ondemand instead (Ingo Schommer)
+ * 2009-11-21 [5d6233a](https://github.com/silverstripe/sapphire/commit/5d6233a) Indentation in customised jquery.ondemand.js (Ingo Schommer)
  * 2009-11-21 [1b138d6](https://github.com/silverstripe/sapphire/commit/1b138d6) Removed layout_helpers.js dependency (Ingo Schommer)
  * 2009-11-21 [df1766b](https://github.com/silverstripe/sapphire/commit/df1766b) Removed unused css/CalendarDateField.css (Ingo Schommer)
  * 2009-11-21 [2fc966c](https://github.com/silverstripe/sapphire/commit/2fc966c) Removed loader.js dependencies (Ingo Schommer)

docs/en/04_Changelogs/rc/2.4.1-rc1.md

@@ -47,7 +47,7 @@
  * [rev:106200] added prefix and suffix support to ContextSummary
  * [rev:106194] Prevent image search queries all images in the site initially when the page is loaded
  * [rev:106178] Enable switch between legacy image search and new version
- * [rev:106118] added setRows() and setColumns() to customize the size of the textarea field outside of the controller
+ * [rev:106118] added setRows() and setColumns() to customise the size of the textarea field outside of the controller
  * [rev:105890] Added method for $this->request->latestParam() backwards compatibility with Director::urlParam()
  * [rev:105732] Ability to hide form by className or for the whole ModelAdmin
  * [rev:105712] Added MySQLDatabaseConfigurationHelper::getDatabaseVersion() which abstracts the version number away from the version check the installer requires