message: reword a few bits
diff: @@ -6,7 +6,7 @@ Lagoon supports Active/Standby (also known as blue/green) deployments.
  To change an existing project to support active/standby you'll need to configure some project settings in the Lagoon API
  `productionEnviromment` should be set to the branch name of the current environment that is active
  -`standbyProductionEnvironment` should be set to the branch name of the current environment that is in standby
  +`standbyProductionEnvironment` should be set to the branch name of the environment that will be in standby
  ```
  mutation updateProject {
  @@ -53,10 +53,14 @@ production_routes:
  > Note: Any routes that are under the section `environments.<branch>.routes` will not be moved as part of active/standby, these routes will always be attached to the environment as defined. Ensure that if you do need a specific route to be migrated during an active/standby switch, that you remove them from the `environments` section and place them under the `production_routes` section specific to if it should be an `active` or `standby` route.
  -## Triggering a switch event
  +## Triggering the active/standby switch
  +### via the UI
  +To trigger the switching of environment routes, you can visit the standby environment in the Lagoon UI and click on the button labeled `Switch Active/Standby environments`. You will be prompted to confirm your action.
  -To trigger an event to switch the environments, you can run the following graphQL mutation, this will inform lagoon to begin the process.
  +Once confirmed, it will take you to the tasks page where you can view the progress of the switch.
  +### via the API
  +The following graphQL mutation can be executed which will start the process of switching the environment routes.
  ```
  mutation ActiveStandby {
  switchActiveStandby(
  @@ -95,7 +99,9 @@ By default, projects will be created with the following aliases that will be ava
  * `lagoon-production`
  * `lagoon-standby`
  -The `lagoon-production` alias will resolve point to whichever site is defined as `productionEnvironment`, where `lagoon-standby` will always resolve to the site that is defined as `standbyProductionEnvironment`
  +The `lagoon-production` alias will resolve to whichever environment is currently in the API as `productionEnvironment`, where `lagoon-standby` will always resolve to the environment that is defined as `standbyProductionEnvironment`.
  +
  +> As the active/standby switch updates these as required, `lagoon-production` will always be the `active` environment.
  These alias are configurable by updating the project, but be aware that changing them may require you to update any scripts that rely on them.
  