Merge pull request magento-commerce/devdocs#2736 from magento-devdocs/hg-jan12-cloudimports

Imports to Cloud guide

Author: hguthrie

src/_includes/cloud/cloud-fastly-manage-vcl-from-admin.md

@@ -15,19 +15,24 @@
 1. After the upload completes, refresh the cache according to the notification at the top of the page.
 
 {:.bs-callout-warning}
-The *Custom VCL snippets* UI option shows only the snippets added through the Admin UI. You must use the Fastly API to [manage custom snippets added through the API]({{ site.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-custom-vcl-snippets-using-the-api).
+The *Custom VCL snippets* UI option shows only the snippets added through the Admin UI. You must [manage custom VCL snippets using the Fastly API]({{ site.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-custom-vcl-snippets-using-the-api).
 
 ## Delete the custom VCL snippet
 
-You can delete custom VCL snippet code from your Fastly configuration by uploading an empty version of the snippet from the Admin UI, or delete it completely using the Fastly API.
+1. [Log in]({{ site.baseurl }}/cloud/onboarding/onboarding-tasks.html#admin) to the Admin UI.
+
+1. Click **Stores** > **Settings** > **Configuration** > **Advanced** > **System**.
+
+1. Expand **Full Page Cache** > **Fastly Configuration** > **Custom VCL Snippets**.
+
+   ![Manage custom VCL snippets]
 
--  Upload an empty version of the snippet file to Fastly to remove the VCL logic from the active VCL version:
+1. In the _Action_ column, click the trash icon next to the snippet to delete.
 
-   -  Edit the snippet and delete the **VCL** snippet content.
-   -  Save the configuration.
-   -  Upload the VCL to Fastly to apply your changes.
+1. On the next modal window, click **DELETE** and activate a new version.
 
--  Use the Fastly API [Delete custom VCL snippet]({{ site.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-vcl) operation to delete the snippet completely, or submit a support ticket to request deletion.
+{:.bs-callout-warning}
+The *Custom VCL snippets* UI option shows only the snippets added through the Admin UI. You must [manage custom VCL snippets using the Fastly API]({{ site.baseurl }}/cloud/cdn/cloud-vcl-custom-snippets.html#manage-custom-vcl-snippets-using-the-api).
 
 [Manage custom VCL snippets]: {{site.baseurl}}/common/images/cloud/cloud-fastly-manage-snippets.png
-{:width="650px"}
+{:width="650px"}

src/cloud/env/variables-build.md

@@ -108,26 +108,48 @@ stage:
 
 You can configure multiple locales per theme. This customization helps speed up the build process by reducing the number of unnecessary theme files. For example, you can build the _magento/backend_ theme in English and a custom theme in other languages.
 
-The following example builds the `magento/backend` theme with three locales:
+The following example builds the `Magento/backend` theme with three locales:
 
 ```yaml
 stage:
   build:
     SCD_MATRIX:
-      "magento/backend":
+      "Magento/backend":
         language:
           - en_US
           - fr_FR
           - af_ZA
 ```
+The following example builds three themes with three locales:
 
-Also, you can choose to _not_ deploy a theme:
+```yaml
+stage:
+  build:
+    SCD_MATRIX:
+      "Magento/backend":
+        language:
+          - en_US
+          - fr_FR
+          - af_ZA
+      "Magento/blank":
+        language:
+          - en_US
+          - fr_FR
+          - af_ZA
+      "Magento/luma":
+        language:
+          - en_US
+          - fr_FR
+          - af_ZA
+```
+
+Or, you can choose to _not_ deploy a theme:
 
 ```yaml
 stage:
   build:
     SCD_MATRIX:
-      "magento/backend": [ ]
+      "Magento/backend": [ ]
 ```
 
 ### `SCD_MAX_EXECUTION_TIME`

src/cloud/project/log-locations.md

@@ -19,7 +19,14 @@ You can view the logs from the file system, the project web UI, and the `magento
 -  **Magento Cloud CLI**—You can view logs using the `magento-cloud log` command.
 
 {:.bs-callout-tip}
-Automatic log rotation, compression, and removal are enabled in the Cloud environment. Each log file type has a rotating pattern and lifetime.
+For Pro environments, automatic log rotation, compression, and removal are enabled for log files with a fixed file name. Each log file type has a rotating pattern and lifetime. Starter environments do not have log rotation.
+
+Full details of the environment's log rotation and lifespan of compressed logs can be found in the following locations :
+
+```terminal
+/etc/logrotate.conf
+/etc/logrotate.d/<various>
+```
 
 ## Manage log data
 
@@ -152,7 +159,6 @@ For example, on Pro production environments a PHP access log for 21 days in the
 ```terminal
 /var/log/platform/<project_id>/php.access.log.22.gz
 ```
-
 The archived log files are always stored in the directory where the original file was located before compression.
 
 {:.bs-callout-info}

src/cloud/project/user-admin.md

@@ -36,7 +36,7 @@ When MFA enforcement is enabled on a {{site.data.var.ece}} project, all users wi
 You can add users and assign roles using the Magento Cloud CLI or the Project Web Interface.
 
 {:.bs-callout-tip}
-Changing user configuration on a {{site.data.var.ece}} environment triggers a site deployment, which takes your site offline until deployment completes. For Production environments, we recommend completing user administration tasks during off-peak hours to prevent service disruptions.
+Changing user configuration on an {{site.data.var.ece}} environment requires a site deployment for the changes to take effect, which takes your site offline until the deployment completes. For Production environments, we recommend completing user administration tasks during off-peak hours to prevent service disruptions.
 
 **Prerequisites:**