- Editorial clean up

- Correct instructions for configuring project and environment variables

Author: maeker12

src/cloud/project/project-webint-basic.md

@@ -61,30 +61,30 @@ You can set the following configuration options for each environment:
    </tr>
    <tr>
       <td>HTTP access control</td>
-      <td>Setting this option <strong>On</strong> enables you to configure security for the project's Web Interface using a login and also IP address access control.</td>
+      <td>Setting this option <strong>On</strong> enables you to configure security for the Project Web Interface using a login and also IP address access control.</td>
    </tr>
 </table>
 
 ### Configure emails for testing {#email}
 
 By default, email support is **disabled** on Staging and Production environments. You must enable email support on an environment to send emails including Welcome, password reset, and two-factor authentication emails for Cloud project users.
 
-You can manage email support for each Cloud project environment from the Project Web interface or from the command line.
+You can manage email support for each Cloud project environment from the Project Web Interface or from the command line.
 
 -  On master and integration branches, use the *Outgoing emails* toggle in the Project Web interface to enable or disable email support.
 
--  On Production and Staging environments or other environments where the *Outgoing emails toggle* is not available in the Project Web interface, you can check the current configuration from the Project Web interface, but you can only change the configuration from the command line using the [Cloud CLI for Commerce]({{ site.baseurl }}/cloud/reference/cli-ref-topic.html) `environment:info` command to set the `enable_smtp` property.
+-  On Production and Staging environments or other environments where the *Outgoing emails toggle* is not available in the Project Web Interface, you can check the current configuration from the Project Web Interface, but you can only change the configuration from the command line using the [Cloud CLI for Commerce]({{ site.baseurl }}/cloud/reference/cli-ref-topic.html) `environment:info` command to set the `enable_smtp` property.
 
    Enabling SMTP updates the `MAGENTO_CLOUD_SMTP_HOST` environment variable with the IP address of the SMTP host for sending mail.
 
 {% include cloud/note-env-config-redeploy-warning.md%}
 
 {:.procedure}
-To manage email support from the Project Web interface:
+To manage email support from the Project Web Interface:
 
 1. [Access your project](#project-access) and select the environment to configure.
 
-1. Select **Configure environment**.
+1. Select **Configure environment**, and then select the **Variables** tab.
 
 1. To enable or disable outgoing emails, toggle *Outgoing emails* **On** or **Off**.
 
@@ -95,7 +95,7 @@ After you change the setting, the environment builds and deploys with the new co
 {:.procedure}
 To manage email support from the command line:
 
-1. Check the current email configuration in the Project web interface.
+1. Check the current email configuration in the Project Web Interface.
 
    ![Check outgoing email configuration]({{ site.baseurl }}/common/images/cloud/cloud-env-outgoing-emails-current-setting.png){:width="650px"}
 
@@ -136,62 +136,66 @@ To manage email support from the command line:
       ```bash
       printenv MAGENTO_CLOUD_SMTP_HOST
       ```
+
    -  Send a test email to your email address or another address you can check.
 
       ```bash
       php -r 'mail("mail@example.com", "test message", "just testing", "From: tester@example.com");'
       ```
 
-## Set environment and project variables {#project-conf-env-var}
+## Set project and environment variables {#project-conf-env-var}
 
-You can set project wide and environment specific variables through the Project Web Interface. Variables can be either text or JSON format. For more information, see [Environment variables]({{ site.baseurl }}/cloud/env/variables-intro.html).
-
-For an example of variables, we walk you through creating Admin variables through Onboarding and project creation tasks. You may want to add _environment variables_ for sensitive data like payment method information. _Project variables_ are set across all branches and environments.
+You can set project wide and environment specific variables through the Project Web Interface. Variables can be either text or JSON format. _Project variables_ are set across all branches and environments. Use _environment variables_ for sensitive data like payment method information. For more information, see [Environment variables]({{ site.baseurl }}/cloud/env/variables-intro.html).
 
 To view or edit environment variables, you must have at minimum the project reader role with [environment admin]({{ site.baseurl }}/cloud/project/user-admin.html) privileges.
 
 {% include cloud/wings-variables.md %}
 
-### Environment variable {#env}
+### Project variables {#project}
 
-To set environment specific variables in the Project Web Interface:
+To set project variables in the Project Web Interface:
+
+1. [Access your project](#project-access).
+1. Select the Settings icon, and then select the **Variables** tab.
+
+   ![Configure project variables]({{ site.baseurl }}/common/images/cloud/cloud-config-project-variables.png){:width="650px"}
 
-1. [Access your project](#project-access) and select a specific environment.
-1. Select the Variables tab.
 1. Click **Add Variable**.
-1. In the **Name** field, enter a variable name. For example, to set the Admin default account password, enter `ADMIN_PASSWORD`.
+1. In the **Name** field, enter a variable name. For example, to set the Admin email for the default account, enter `ADMIN_EMAIL`.
 1. In the **Value** field, enter the value for the variable. For example, enter a valid email address accessible for reset email notifications.
 
-   ![Set environment variables]({{ site.baseurl }}/common/images/cloud/cloud_env-var.png)
+   ![Set project variables]({{ site.baseurl }}/common/images/cloud/cloud_project_variable.png)
 
-1. As needed, select options for **JSON value**, **Enabled**, **Inheritable by child environments** and **Sensitive**. If you do not have Super User access, you may only see the JSON value option.
+1. As needed, select options for **JSON value**, **Visible during build**, and **Visible during runtime**. If you do not have Super User access, you may only see the JSON value option.
 1. Click **Add Variable**. After you add the variable, the environment will deploy. Wait until deployment completes before more edits.
 
-{:.bs-callout-warning}
-If you are attempting to [override configuration settings]({{ site.baseurl }}
-), you must prepend `env:` to the variable name. For example:
-![Environment variable example]({{ site.baseurl }}/common/images/cloud/cloud_env_var_example.png)
-
-### Project variable {#project}
+### Environment variables {#env}
 
-To set project variables in the Project Web Interface:
+To set environment specific variables in the Project Web Interface:
 
 1. [Access your project](#project-access) and select a specific environment.
-1. Select the Variables tab.
+1. Select **Configure environment**.
+1. Select the **Variables** tab.
 1. Click **Add Variable**.
-1. In the **Name** field, enter a variable name. For example, to set the Admin email for the default account, enter `ADMIN_EMAIL`.
+1. In the **Name** field, enter a variable name. For example, to set the Admin default account password, enter `ADMIN_PASSWORD`.
 1. In the **Value** field, enter the value for the variable. For example, enter a valid email address accessible for reset email notifications.
 
-   ![Set project variables]({{ site.baseurl }}/common/images/cloud/cloud_project_variable.png)
+   ![Set environment variables]({{ site.baseurl }}/common/images/cloud/cloud_env-var.png){:width="650px"}
 
-1. As needed, select options for **JSON value**, **Visible during build**, and **Visible during runtime**. If you do not have Super User access, you may only see the JSON value option.
+1. As needed, select options for **JSON value**, **Enabled**, **Inheritable by child environments** and **Sensitive**. If you do not have Super User access, you may only see the JSON value option.
 1. Click **Add Variable**. After you add the variable, the environment will deploy. Wait until deployment completes before more edits.
 
+{:.bs-callout-warning}
+If you are attempting to [override configuration settings]({{ site.baseurl }}
+), you must prepend `env:` to the variable name. For example:
+![Environment variable example]({{ site.baseurl }}/common/images/cloud/cloud_env_var_example.png)
+
 ## Configure routes {#project-conf-env-route}
 
 Routes allow you to set redirects or upstream settings for applications for your specific environment. For full details on routes, see [routes.yaml]({{ site.baseurl }}/cloud/project/routes.html). These routes (or URLs) are used to access your storefront.
 
 1. [Access your project](#project-access) and select a specific environment.
+1. Select **Configure environment**.
 1. Select the Routes tab.
 1. Select **Add Route**.
 1. Enter a URL. You can use `{default}` in the URL, which is a placeholder for the default domain.
@@ -207,7 +211,7 @@ Routes allow you to set redirects or upstream settings for applications for your
 1. To configure a Redirect, enter a URL to **Redirect to**. You can use `{default}` in the URL, which is a placeholder for the default domain.
 1. Click **Add Route** to save. The setting is saved and deployed to the environment.
 
-   ![Configure a route]({{ site.baseurl }}/common/images/cloud/cloud_routes.png)
+   ![Configure a route]({{ site.baseurl }}/common/images/cloud/cloud_routes.png){:width="650px"}
 
 ## View environment history {#project-conf-hist}
 
@@ -218,19 +222,19 @@ An environment's history includes:
 -  Syncs and merges
 -  Code pushes
 
-To view the history for an environment, log in to your project and select the environment. The page displays a general history of actions completed on the page. For a detailed list of completed actions during build and deployment, we recommend reviewing logs directly on the servers. See [View logs]({{ site.baseurl }}/cloud/project/log-locations.html).
+To view the history for an environment, log in to your project and select the environment. The page displays a general history of actions completed on the page. For a detailed list of completed actions during build and deployment, Adobe recommends reviewing logs directly on the servers. See [View logs]({{ site.baseurl }}/cloud/project/log-locations.html).
 
 The following figure shows a sample history.
 
-![Sample environment history]({{ site.baseurl }}/common/images/cloud/cloud_environment-history.png)
+![Sample environment history]({{ site.baseurl }}/common/images/cloud/cloud_environment-history.png){:width="800px"}
 
 The history shows, from oldest to newest:
 
 -  Environment branched from `FeatureX`
 -  Environment synced with the parent
 -  Environment snapshot created
 
-We recommend [creating a snapshot]({{ site.baseurl }}/cloud/project/project-webint-snap.html) before you make any code changes.
+Adobe recommends [creating a snapshot]({{ site.baseurl }}/cloud/project/project-webint-snap.html) before you make any code changes.
 
 -  Environment variable added
 -  Environment snapshot created