small terminology updates

_episodes/02-setupVariables.md

@@ -125,9 +125,9 @@ This file has two sections `services` and `secrets`. In the `services` section t
 
 4. Review the COmanage environment variables. A full reference of enviornment variables can be found at the [COmanage Registry Docker Environment Variables guide](https://github.com/Internet2/comanage-registry-docker/blob/master/docs/comanage-registry-common-environment-variables.md). Only a subset of these variables are configured here:
 
-* **Registry Administrator**: The Given Name, Family Name, and Username are needed for the person who will sign into the Registry as soon as it is launched. These three fields are blank; you will fill them in with the person that you have selected to be your CMP Admin.
-* **Database**: These variables are needed to allow the Registry to sign into the MariaDB database that we are installing. When you install COmanage in your own environment, you may be connecting to an existing database rather than one being installed at the same time as the Registry (as we are doing here.) In that situation, you would include information for your own database. 
-* **Email**: COmanage can be configured to send emails to users, for example, for notifications. The file currently has a simple gmail account configured to send emails for the training purposes. 
+* **Registry Administrator**: The Given Name, Family Name, and Username are needed for the person who will sign into COmanage Registry as soon as it is launched. These three fields are blank; you will fill them in with the person that you have selected to be your CMP Admin.
+* **Database**: These variables are needed to allow the Registry to sign into the MariaDB database that we are installing. When you install COmanage in your own environment, you may be connecting to an existing database rather than one being installed at the same time as COmanage Registry (as we are doing here.) In that situation, you would include information for your own database. 
+* **Email**: COmanage Registry can be configured to send emails to users, for example, for notifications. The file currently has a simple gmail account configured to send emails for the training purposes. 
 
 In each case where a password is needed, we are using a password that is stored in the Docker secrets that we reviewed (and added to) earlier. The two passwords that you created in step 2 above are referenced here in the `database` section of the file.