uniformity: ‘administration’ not ‘admin’

see style guide pls thx

Author: petecooper

_recycle/out-of-scope-tutorials/unicode_support.textile

@@ -36,7 +36,7 @@ h4(#utf-8_support_in_textpattern). UTF-8 support in Textpattern
 
 Textpattern supports UTF-8 as best as is possible under the circumstances (also see the explanation under the _The Quick Guide for the End-User_ section above). What this currently means is when you install Textpattern it will (if you are using MySQL4.1 and above) create the tables in the database as UTF-8 (with the default UTF-8 collation of utf8_general_ci). Textpattern uses MySQL's fulltext indexing to provide its search-functionality, this means if you are using characters outside of the ASCII range your search will likely only function properly with MySQL4.1 and above (but Textpattern will still work with MySQL versions 4.0.x and 3.x in general).
 
-Currently Textpattern tries to be as conservative as possible in the use of PHP's string-functions. So articles are only processed by Textile which only replaces distinct syntax that it recognizes and otherwise leaves the text alone. The i18n-strings that Textpattern uses for the admin-side (and some parts of the public-side) are also in UTF-8 and stay mostly untouched.
+Currently Textpattern tries to be as conservative as possible in the use of PHP's string-functions. So articles are only processed by Textile which only replaces distinct syntax that it recognizes and otherwise leaves the text alone. The i18n-strings that Textpattern uses for the administration-side (and some parts of the public-side) are also in UTF-8 and stay mostly untouched.
 
 *Note:* Textpattern does not rely on the mb_strings extension for PHP. Future versions may well take advantage of it where available, but it won't be a requirement.
 

administration/diagnostics-panel.md

@@ -102,7 +102,7 @@ Locale
 : The language and character set you have configured.
 
 Site / Admin language
-: Language designations for the front-side and admin-side areas.
+: Language designations for the front-side and administration-side areas.
 
 Web server
 : Your web server type (e.g. Apache, Nginx).

administration/extensions-region.md

@@ -3,21 +3,21 @@ layout: document
 category: Administration
 published: true
 title: Extensions region
-description: The extensions administration region appears to the higher user roles if any of the admin-side plugins that employ it are installed.
+description: The extensions administration region appears to the higher user roles if any of the administration-side plugins that employ it are installed.
 ---
 
 # Extensions region
 
-The Extensions administration region is not an out-of-the-box feature. It appears to the higher [user roles](/administration/user-roles-and-privileges) if any of the admin-side plugins that employ it are installed.
+The Extensions administration region is not an out-of-the-box feature. It appears to the higher [user roles](/administration/user-roles-and-privileges) if any of the administration-side plugins that employ it are installed.
 
-When relevant, the Extensions administration region will be seen in the administration navigation from all admin-side views *except* when you are in context of the [Plugins panel](/administration/plugins-panel), even for the administrator. This behaviour ensures being able to safely deactivate and/or remove outdated or buggy plugins if they are causing problems. To access the Extensions administration region from the Plugins panel, move to anywhere else in the admin-side first, and the Extensions administration region will appear in the navigation again.
+When relevant, the Extensions administration region will be seen in the administration navigation from all administration-side views *except* when you are in context of the [Plugins panel](/administration/plugins-panel), even for the administrator. This behaviour ensures being able to safely deactivate and/or remove outdated or buggy plugins if they are causing problems. To access the Extensions administration region from the Plugins panel, move to anywhere else in the administration-side first, and the Extensions administration region will appear in the navigation again.
 
 When you upload a plugin that uses the Extensions administration region, a new panel option will appear under the region that provides the plugin's associated functionality or configuration controls.
 
 ## Unconventional panel placement
 
 The use of the Extensions administration region is a convention adopted by plugin developers to put administration-side plugin preferences and other functional controls in a logical place, and that's a good thing when it can be done.
 
-Not all administration-side plugins use the Extensions administration region, however. Some plugins will add their associated admin-side panel in one of the core regions. This may happen when panel placement is decided with respect to functional context over convention. Another reason may be a concern for having too many plugin panels under the Extensions administration region, though this is likely a moot issue for most Textpattern users.
+Not all administration-side plugins use the Extensions administration region, however. Some plugins will add their associated administration-side panel in one of the core regions. This may happen when panel placement is decided with respect to functional context over convention. Another reason may be a concern for having too many plugin panels under the Extensions administration region, though this is likely a moot issue for most Textpattern users.
 
 [Related: Home administration region](/administration/home-region)

administration/home-region.md

@@ -3,14 +3,14 @@ layout: document
 category: Administration
 published: true
 title: Home region
-description: The Home administration region appears to the higher user roles if any of the admin-side plugins that employ it are installed.
+description: The Home administration region appears to the higher user roles if any of the administration-side plugins that employ it are installed.
 ---
 
 # Home region
 
-The Home administration region is not an out-of-the-box feature. It appears to the higher [user roles](/administration/user-roles-and-privileges) if any of the admin-side plugins that employ it are installed.
+The Home administration region is not an out-of-the-box feature. It appears to the higher [user roles](/administration/user-roles-and-privileges) if any of the administration-side plugins that employ it are installed.
 
-When relevant, the Home administration region will be seen in the administration navigation from all admin-side views *except* when you are in context of the [Plugins panel](/administration/plugins-panel) even for the administrator. This behaviour ensures being able to safely deactivate and/or remove outdated or buggy plugins if they are causing problems. To access the Home administration region from the Plugins panel, move to anywhere else in the admin-side first, and the Home administration region will appear in the navigation again
+When relevant, the Home administration region will be seen in the administration navigation from all administration-side views *except* when you are in context of the [Plugins panel](/administration/plugins-panel) even for the administrator. This behaviour ensures being able to safely deactivate and/or remove outdated or buggy plugins if they are causing problems. To access the Home administration region from the Plugins panel, move to anywhere else in the administration-side first, and the Home administration region will appear in the navigation again
 
 When you upload a plugin that uses the Home administration region, a new panel option will appear under the region that provides the plugin's associated functionality or configuration controls.
 

administration/index.md

@@ -165,6 +165,6 @@ The [Extensions](/administration/extensions-region) region is one you may see in
 
 ## Changing default login panel
 
-The default admin-side landing location changes once you initially set your language preferences. You'll find yourself landing on the [Write](/administration/write-panel) panel from that point on, which is the default panel under the Content region.
+The default administration-side landing location changes once you initially set your language preferences. You'll find yourself landing on the [Write](/administration/write-panel) panel from that point on, which is the default panel under the Content region.
 
 You can change the default landing panel to whichever one you want using the **Default panel** preference under the Admin area of the [Preferences](/administration/preferences-panel) panel.

administration/languages-panel.md

@@ -22,11 +22,11 @@ On this page:
 
 ## Site language
 
-The primary language that the website will be targeted at. You can choose from any of the installed language packs. This is used on the public site and as the default admin-side language for users (unless changed in the 'User language' option - see below).
+The primary language that the website will be targeted at. You can choose from any of the installed language packs. This is used on the public site and as the default administration-side language for users (unless changed in the 'User language' option - see below).
 
 ## User language
 
-From Textpattern version 4.7 onwards, each user within the admin-side can be choose their specific language for the admin panels. You can choose from any of the installed language packs. This does not affect the 'Site language'.
+From Textpattern version 4.7 onwards, each user within the administration-side can be choose their specific language for the admin panels. You can choose from any of the installed language packs. This does not affect the 'Site language'.
 
 ## List of available languages
 

administration/users-panel.md

@@ -18,7 +18,7 @@ On this page:
   * [Administrator controls](#administrator-controls)
 * [User data form](#user-data-form)
 * [Extending user account functionality](#extending-user-account-functionality)
-  * [Admin-side management and data extension](#admin-side-management-and-data-extension)
+  * [Administration-side management and data extension](#administration-side-management-and-data-extension)
   * [Autonomous registration, log in, and data access/submission](#autonomous-registration-log-in-and-data-accesssubmission)
 
 ## User accounts table
@@ -61,19 +61,19 @@ It's common for site owners of multi-user sites to extend Textpattern's core fun
 
 There are two convenient contexts for talking about user accounts extension:
 
-1. Admin-side management and data extension
+1. Administration-side management and data extension
 2. Autonomous (self) registration, log in, and data access/submission
 
-### Admin-side management and data extension
+### Administration-side management and data extension
 
-The most popular approach for admin-side extension of user accounts, indeed what should nearly be core functionality, is to install and use two plugins that work together:
+The most popular approach for administration-side extension of user accounts, indeed what should nearly be core functionality, is to install and use two plugins that work together:
 
 * [smd_user_manager](https://forum.textpattern.com/viewtopic.php?id=36558) - This plugin provides a much richer set of features for managing user accounts, including modifying the core user roles and privileges.
 * [smd_bio](https://forum.textpattern.com/viewtopic.php?id=31496) - This plugin extends the user account data itself, so you can create user bios or profiles having any data structure you want and display that data on the front-side of a website.[^5]
 
 ### Autonomous registration, log in, and data access/submission
 
-There are situations (membership communities, employee intranets, magazine article contributions, etc.) where people may not need physical access to the admin-side, but still need user accounts to access specific information, contribute content, or edit their own account details. Various plugins can help with the initial setup of this front-side access, which effectively abstracts the admin-side UI panels away from such users. Depending on what you need or want to do, there are various plugins to try:
+There are situations (membership communities, employee intranets, magazine article contributions, etc.) where people may not need physical access to the administration-side, but still need user accounts to access specific information, contribute content, or edit their own account details. Various plugins can help with the initial setup of this front-side access, which effectively abstracts the administration-side UI panels away from such users. Depending on what you need or want to do, there are various plugins to try:
 
 * [cbe_frontauth](https://forum.textpattern.com/viewtopic.php?id=36552) - A plugin that enables front-side log in abilities for *existing* account holders. This plugin is often used in combination with [cbe_members](https://forum.textpattern.com/viewtopic.php?id=37760).
 * [mem_self_register](https://forum.textpattern.com/viewtopic.php?id=8520) - A plugin similar to cbe_frontauth, but also enables the ability to register an account too. This plugin is often used in combination with [mem_form](https://forum.textpattern.com/viewtopic.php?id=25247).

administration/write-panel.md

@@ -10,7 +10,7 @@ description: The Write panel reveals the various features for managing articles
 
 <img class="img--bordered" width="680" height="422" alt="Figure 2" src="/img/47x/admin-panel-write.png" srcset="/img/47x/admin-panel-write.png 1x, /img/47x/[email protected] 2x">
 
-The Write panel is the default panel of the administration side of Textpattern; it opens when you log in to the admin-side (see Figure 1). The exceptions are when 1) you log in after a new update of your Textpattern installation, in which case you're initially routed to the [Languages panel](/administration/languages-panel), or 2) if you change the default panel to something else via the preference for it in the **Admin** section of the [Preferences panel](/administration/preferences-panel). (The Languages and Preferences panels are both under the main Admin menu.)
+The Write panel is the default panel of the administration side of Textpattern; it opens when you log in to the administration-side (see Figure 1). The exceptions are when 1) you log in after a new update of your Textpattern installation, in which case you're initially routed to the [Languages panel](/administration/languages-panel), or 2) if you change the default panel to something else via the preference for it in the **Admin** section of the [Preferences panel](/administration/preferences-panel). (The Languages and Preferences panels are both under the main Admin menu.)
 
 The Write panel reveals the editing fields for article content, and various controls for managing content display and publication, such as content organization, date and time, associated images, how you want to format your text, and so on.
 

brand/editorial-guide.md

@@ -221,7 +221,7 @@ Avoid using 'admin' as an abbreviation unless you are specifically referring to
 
 * The top-level Admin section, as labeled in the navigation for it. (In the 'Classic' theme, this defaults to the Users panel.)
 * The Admin section of the Preferences panel.
-* The Admin-side theme preference in the Admin section of the Preferences panel.
+* The Administration-side theme preference in the Admin section of the Preferences panel.
 
 Any other use of 'admin' can lead to confusion about what is meant. Whether you mean *administration* or *administrator*, write it out fully every time so the meaning and context is perfectly clear.
 
@@ -419,23 +419,23 @@ Keep links in body copy to a minimum. Ensure links that are used are focused on
 
 ## Terminology
 
-Textpattern terms as admin-side panel and link references
-When using the name of any admin-side panel to mean the location of that panel, it should always be a non-italicised link to the given wiki page it's referring to, and the link should only be on the word itself, i.e. the link text should be the same as the name of the wiki page it's pointing to.
+Textpattern terms as administration-side panel and link references
+When using the name of any administration-side panel to mean the location of that panel, it should always be a non-italicised link to the given wiki page it's referring to, and the link should only be on the word itself, i.e. the link text should be the same as the name of the wiki page it's pointing to.
 
 Correct → Most of your content is created in the Write panel.
 
 Wrong → Most of your content is created in the Write panel.
 
 Wrong → Most of your content is created in the Write panel.
- There are two exceptions to the rule in bold above. Wiki pages for the Images and Comments panels are titled "Images (panel)" and "Comments (admin-side)", respectively. These are necessary (though inconsistently named) titles to avoid wiki page title conflicts with Tag pages having the same names. But they are unattractive, so we use custom links to these pages via wiki syntax.
+ There are two exceptions to the rule in bold above. Wiki pages for the Images and Comments panels are titled "Images (panel)" and "Comments (administration-side)", respectively. These are necessary (though inconsistently named) titles to avoid wiki page title conflicts with Tag pages having the same names. But they are unattractive, so we use custom links to these pages via wiki syntax.
 
 Correct → Photos and other images are uploaded in the Images panel.
 
 Correct → You can edit article comments in the Comments panel.
 
 Wrong → Photos and other images are uploaded in the Images (panel).
 
-Wrong → You can edit article comments in the Comments (admin-side) panel.
+Wrong → You can edit article comments in the Comments (administration-side) panel.
 
 Textpattern terms as semantical (non-linked) references
 Certain panel names—often considered to be Textpattern's semantical features—have a lot of similarity with general web terms, and thus can be easily confused if not clearly distinguished in documentation. Textpattern terms used in context of semantics, but not linked to panel documentation pages, should be capitalised and italicised.

build/creating-administration-themes.md

@@ -62,7 +62,7 @@ Delete the _screenshot.png_ file if not needed, or replace it with one you will
 
 **Step 4:**
 
-Log in to the back-end. Go to Admin > Preferences > Admin, look for the **Admin-side theme** preference and select the newly added theme (step 3).
+Log in to the back-end. Go to Admin > Preferences > Admin, look for the **Administration-side theme** preference and select the newly added theme (step 3).
 
 **Step 5:**
 

development/admin-side-events-and-steps.md

@@ -2,13 +2,13 @@
 layout: document
 category: Development
 published: true
-title: Admin-side events and steps
-description: These are the main events and steps that Textpattern uses as you interact with the admin-side interface.
+title: Administration-side events and steps
+description: These are the main events and steps that Textpattern uses as you interact with the administration-side interface.
 ---
 
-# Admin-side events and steps
+# Administration-side events and steps
 
-These are the main events and steps that Textpattern uses as you interact with the admin-side interface. An *event* is usually the panel or plugin name, e.g. `prefs` or `image`. A *step* is Textpattern terminology for an action that occurs on that panel, for example `save` or `image_edit`.
+These are the main events and steps that Textpattern uses as you interact with the administration-side interface. An *event* is usually the panel or plugin name, e.g. `prefs` or `image`. A *step* is Textpattern terminology for an action that occurs on that panel, for example `save` or `image_edit`.
 
 Although they are not direct [callbacks](/development/core-callbacks-reference), you may hook into these events and steps from a plugin to perform an action.