changed MAGE to Mage throughout documentation

Author: jmckomni

CHANGELOG.md

@@ -1,7 +1,7 @@
 # Change Log
 
 All notable changes to this project will be documented in this file.
-MAGE adheres to [Semantic Versioning](http://semver.org/).
+Mage adheres to [Semantic Versioning](http://semver.org/).
 
 ---
 

README.md

@@ -1,4 +1,4 @@
-MAGE 6.2.x on Amazon Linux 2023
+Mage 6.2.x on Amazon Linux 2023
 
 1. Install docker
 ```

aws_amazon_linux_2023.md

@@ -1,10 +1,10 @@
 # Running with Docker
 
-## MAGE server image
+## Mage server image
 
-The MAGE Server image contains the the core MAGE server Node app that consists
-of the ReST web service and the MAGE web app.  By default, the image also
-includes plugins maintained in the [MAGE server repository](../plugins/).  By
+The Mage Server image contains the the core Mage server Node app that consists
+of the ReST web service and the Mage web app.  By default, the image also
+includes plugins maintained in the [Mage server repository](../plugins/).  By
 default, the server [Dockerfile](./server/Dockerfile) pulls the latest tagged
 versions from the NPM registry.  You can override the version using Docker's
 `--build-arg` CLI switch to set the package versions you want in the image.
@@ -23,23 +23,23 @@ Dockerfile builds exactly the same as the standard Dockerfile.
 
 ## Docker Compose
 
-You can start a MAGE server by using [docker compose](https://docs.docker.com/compose/) to start services
-defined in MAGE's [Compose file](docker-compose.yml).
+You can start a Mage server by using [docker compose](https://docs.docker.com/compose/) to start services
+defined in Mage's [Compose file](docker-compose.yml).
 
-The first time you run MAGE with Docker, execute the following steps from the directory where you cloned the
-MAGE Git repository.
+The first time you run Mage with Docker, execute the following steps from the directory where you cloned the
+Mage Git repository.
 ```bash
 $ cd ./docker
 $ docker compose up -d # build the service images, then create and start the service containers for the first time
 ```
-If you want to use a MAGE server image tagged with a different version than
+If you want to use a Mage server image tagged with a different version than
 the `mage-server` Compose service currently defines, prepend the `MAGE_VERSION`
 environment variable to the command.
 ```bash
 $ MAGE_VERSION=6.3.0-beta.1 docker compose up -d
 ```
 With all the default settings, you should then be able to browse to
-http://localhost:4242 to interact with the MAGE web app.
+http://localhost:4242 to interact with the Mage web app.
 
 ## Interacting with the containers
 
@@ -49,7 +49,7 @@ you are operating from the [`docker`](docker) directory.
 After the initial `up` command, you can use `docker compose stop` and
 `docker compose start` to stop and start the service containers.
 
-You can use [`docker compose ps`](https://docs.docker.com/engine/reference/commandline/compose_ps/) to see the state of the MAGE service containers.
+You can use [`docker compose ps`](https://docs.docker.com/engine/reference/commandline/compose_ps/) to see the state of the Mage service containers.
 ```bash
 $ docker compose ps
 NAME                   COMMAND                  SERVICE             STATUS              PORTS
@@ -59,10 +59,10 @@ docker-mage-server-1   "./mage.service --pl…"   mage-server         running
 You can use [`docker-compose logs <service>`](https://docs.docker.com/engine/reference/commandline/compose_logs/) to display console logging for a service.
 ```
 $ docker compose logs mage-server
-mage-server_1  | 2018-04-26T23:30:30.684Z - info: Starting MAGE Server ...
+mage-server_1  | 2018-04-26T23:30:30.684Z - info: Starting Mage Server ...
 mage-server_1  | 2018-04-26T23:30:31.403Z - info: setting up provision uid
 mage-server_1  | 2018-04-26T23:30:31.861Z - info: Using '/var/lib/mage/attachments' as base directory for feature attachments.
-mage-server_1  | 2018-04-26T23:30:31.861Z - info: Using '/var/lib/mage/icons' as base directory for MAGE icons.
+mage-server_1  | 2018-04-26T23:30:31.861Z - info: Using '/var/lib/mage/icons' as base directory for Mage icons.
 # etc., etc.
 ```
 While the service containers are up, you can interact with them using
@@ -75,7 +75,7 @@ UID        PID  PPID  C STIME TTY          TIME CMD
 mongodb      1     0  0 07:16 ?        00:03:47 mongod --dbpath /data/mage --logpath /var/log
 root        67     0  0 22:37 pts/0    00:00:00 bash
 root        73    67  0 22:37 pts/0    00:00:00 ps -ef
-root@df8b00beafa2:/# mongo # interact directly with the running MAGE database # do some ill-advised things directly to the database
+root@df8b00beafa2:/# mongo # interact directly with the running Mage database # do some ill-advised things directly to the database
 MongoDB shell version v3.6.3
 connecting to: mongodb://127.0.0.1:27017
 MongoDB server version: 3.6.3
@@ -112,22 +112,22 @@ users
 
 ### App Services
 
-The MAGE Server Docker app consists of three service containers: the MongoDB
-database, the MAGE Node.js app, and the optional nginx TLS reverse proxy.
+The Mage Server Docker app consists of three service containers: the MongoDB
+database, the Mage Node.js app, and the optional nginx TLS reverse proxy.
 
 ### MongoDB
 
 The MongoDB image is the official MongoDB image available from [Docker Hub](https://hub.docker.com/_/mongo/).  The Compose
 file builds that image unmodified, but uses a custom command to launch MongoDB with specific settings.  The Compose file
 runs MongoDB as the service `mage-db`.
 
-### MAGE server
+### Mage server
 
 The Compose file references a custom, local [Dockerfile](server/Dockerfile) based on the official [Node.js](https://hub.docker.com/_/node/)
-image to build the MAGE server image.  At build time, the MAGE server Dockerfile
-copies whatever MAGE server package tarballs you supply into the MAGE server
+image to build the Mage server image.  At build time, the Mage server Dockerfile
+copies whatever Mage server package tarballs you supply into the Mage server
 image, which might not match the default version the Compose currently defines.
-If you want the MAGE server image that Compose builds to have a different tag,
+If you want the Mage server image that Compose builds to have a different tag,
 override the `MAGE_VERSION` default value in the Compose file.
 ```bash
 MAGE_VERSION=6.2.0 docker compose build

docker/README.md

@@ -1,7 +1,7 @@
-# MAGE Authentication and Identity Providers
+# Mage Authentication and Identity Providers
 
 To configure authentication settings and identity providers
-1. Click the gear icon in the upper right of the MAGE web app to load the _Admin_ page.
+1. Click the gear icon in the upper right of the Mage web app to load the _Admin_ page.
 1. Click, the _Settings_ tab in the tab strip on the left of the page.
 1. Click the _Authentication_ tab near the top of the main content pane.  This tab should be selected by default.
 1. Click any of the accordion headings to expand the section for the authentication you want to configure, or
@@ -11,13 +11,13 @@ To configure authentication settings and identity providers
 
 ## OAuth 2.0
 
-Here is an example of using Google's OAuth 2.0 [endpoints](https://developers.google.com/identity/gsi/web/guides/overview) to authenticate MAGE
+Here is an example of using Google's OAuth 2.0 [endpoints](https://developers.google.com/identity/gsi/web/guides/overview) to authenticate Mage
 users.  This setup is very similar to Google OpenID Connect authentication.
 
 Obtain your _Client Identifier_ and _Client Secret_ from Google's [API Console](https://console.cloud.google.com/apis/credentials/oauthclient).
 Additionally on that page, ensure you register the correct callback URL, e.g., `https://mage.example.com/auth/oauth/callback`
 
-On the MAGE Admin page, click the  _Settings_ tab.
+On the Mage Admin page, click the  _Settings_ tab.
 
 _Authorization URL_ - `https://accounts.google.com/o/oauth2/v2/auth`
 _Token URL_ - `https://oauth2.googleapis.com/token`
@@ -30,7 +30,7 @@ _Display Name Property_ - `name`
 
 ## LDAP
 
-You can setup MAGE to authenticate users with an LDAP server.  For development
+You can setup Mage to authenticate users with an LDAP server.  For development
 testing, the [`auth-idp`](../docker/auth-idp/docker-compose.yml) Compose file
 uses the [osixia/openldap](https://github.com/osixia/docker-openldap) and
 [osixia/phpLDAPAdmin](https://github.com/osixia/docker-phpLDAPAdmin) images
@@ -79,9 +79,9 @@ Using the phpLDAPAdmin UI to setup a simple group structure.
 You now have a simple group structure and user account in your LDAP database.
 
 Now that you have an LDAP database with a user account, you can configure LDAP
-authentication in MAGE.  This assumes you're running a MAGE server on
+authentication in Mage.  This assumes you're running a Mage server on
 http://localhost:4242.
-1. Open the MAGE web app in your browser.
+1. Open the Mage web app in your browser.
 1. Click the gear icon in the top right to load the _Admin_ page.
 1. Click the _Security_ tab in the vertical tab strip on the left.
 1. Click the _New Authentication_ button.
@@ -108,15 +108,15 @@ http://localhost:4242.
 1. Adjust the color settings to your preference.
 1. Click the _Next_ button.
 1. Review the settings and click the _Save_ button.
-1. Open a new private browser tab or window and load your MAGE server web app.
+1. Open a new private browser tab or window and load your Mage server web app.
 1. The sign-in page should display a button labeled _SIGN IN WITH LOCAL LDAP_
    under two text fields.
 1. In the _Local LDAP Username_ text field, enter `batman`.
 1. In the _Local LDAP Password_ text field, enter `i heart alfred`.
 1. Click the _SIGN IN WITH LOCAL LDAP_ button.
 1. The page will most likely display a dialog that states the account needs
    admin approval.
-1. In the browser tab with your MAGE admin page, click the _Users_ tab in the
+1. In the browser tab with your Mage admin page, click the _Users_ tab in the
    tab strip on the left.
 1. Click the _Inactive_ search facet near the top left of the main pane.  The
    user list should contain the _Batman_ user with a green _Activate_ button.
@@ -130,7 +130,7 @@ http://localhost:4242.
 1. You are now authenticated with your LDAP account.
 
 ## SAML
-You can setup MAGE to authenticate users with an SAML server.  For development
+You can setup Mage to authenticate users with an SAML server.  For development
 testing, the [`auth-idp`](../docker/auth-idp/docker-compose.yml) Compose file
 uses the [kristophjunge/test-saml-idp](https://github.com/kristophjunge/docker-test-saml-idp)
 Start the `mage-idp-saml` SAML
@@ -144,7 +144,7 @@ The docker compose file is set to seed a few users with the .saml/authsources.ph
 file is mounted under volumes in the docker compose. Once it is spun up, you are ready to
 configure your saml authentication provider.
 
-1. Open the MAGE web app in your browser.
+1. Open the Mage web app in your browser.
 1. Click the gear icon in the top right to load the _Admin_ page.
 1. Click the _Security_ tab in the vertical tab strip on the left.
 1. Click the _New Authentication_ button.
@@ -168,7 +168,7 @@ configure your saml authentication provider.
 1. Adjust the color settings to your preference.
 1. Click the _Next_ button.
 1. Review the settings and click the _Save_ button.
-1. Open a new private browser tab or window and load your MAGE server web app.
+1. Open a new private browser tab or window and load your Mage server web app.
 1. The sign-in page should display a button labeled _Continue with SAML_
 1. Clicking this button will take you to a simple login page where the saml server is running.
 1. for Username enter `saml.user1`