Merge pull request #154 from magento-devdocs/DOC-470-cloud-round-1

Rebranding for cloud guide

Author: jeff-matthews

src/_data/var.yml

@@ -20,7 +20,7 @@ mbi: Adobe Commerce Reporting
 
 # Cloud product name variables
 
-ece: Cloud for Adobe Commerce
+ece: Adobe Commerce on cloud infrastructure
 ece-release-date: July 29, 2021
 csuite: Cloud Suite for Commerce
 

src/cloud/architecture/cloud-architecture.md

@@ -1,6 +1,6 @@
 ---
 group: cloud-guide
-title: Magento Commerce Cloud architecture
+title: Cloud architecture for Commerce
 functional_areas:
   - Cloud
 redirect_from:

src/cloud/architecture/starter-develop-deploy-workflow.md

@@ -102,7 +102,7 @@ For the best information on configurations, review the documentation for {{site.
 *  [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html) for roles, tools, notifications, and your encryption key for your database
 *  Extension settings using their documentation
 
-Beyond just store settings, you can further configure multiple sites and stores, configured services, and more. See [Configure Magento Commerce]({{ site.baseurl }}/cloud/configure/configuration-overview.html).
+Beyond just store settings, you can further configure multiple sites and stores, configured services, and more. See [Configure your store]({{ site.baseurl }}/cloud/configure/configuration-overview.html).
 
 Now you need to get these settings into your code. We have a helpful command to do this, keep reading.
 

src/cloud/before/before-workspace-magento-prereqs.md

@@ -176,7 +176,7 @@ To set `auto_increment_increment` to 3:
 
 To install the `magento-cloud` CLI , see the [Magento Cloud CLI reference]({{ site.baseurl }}/cloud/reference/cli-ref-topic.html).
 
-## Additional requirements for Magento Commerce {#commerce}
+## Additional requirements
 
 The requirements listed in this topic are specific to {{site.data.var.ece}} environments. You will also install {{site.data.var.ee}} on your VM or Docker container. For that installation, you should also review the following:
 

src/cloud/bk-cloud.md

@@ -1,6 +1,6 @@
 ---
 group: cloud-guide
-title: Magento Commerce Cloud guide
+title: Cloud guide for Commerce
 functional_areas:
   - Cloud
 ---

src/cloud/cdn/cloud-fastly.md

@@ -35,7 +35,7 @@ Fastly provides the following services to optimize and secure content delivery o
 
    -  **SSL/TLS certificates**–The Fastly service requires an SSL/TLS certificate to serve secure traffic over HTTPS. Magento provides a Domain-validated Let's Encrypt SSL/TLS certificate for each Staging and Production environment. Magento completes domain validation and certificate provisioning during the Fastly set up process. See [TLS and Fastly].
 
-   -  **Origin cloaking**–Magento can enable Origin Cloaking for all Magento Commerce projects hosted on the Cloud platform. This option hides the IP addresses of your origin servers to protect them from direct access. When this feature is enabled, all traffic to your Cloud infrastructure must route through the Fastly CDN or another secure channel. Any traffic sent directly to the Origin servers is blocked. If you have traffic that does not require caching, you can customize the Fastly service configuration to allow requests to [bypass the Fastly cache].
+   -  **Origin cloaking**–Adobe can enable Origin Cloaking for all {{ site.data.var.ece }} projects. This option hides the IP addresses of your origin servers to protect them from direct access. When this feature is enabled, all traffic to your Cloud infrastructure must route through the Fastly CDN or another secure channel. Any traffic sent directly to the Origin servers is blocked. If you have traffic that does not require caching, you can customize the Fastly service configuration to allow requests to [bypass the Fastly cache].
 
 -  **Image optimization**—Offloads image processing and resizing load to the Fastly service freeing servers to process orders and conversions efficiently. See [Fastly image optimization].
 

src/cloud/cdn/configure-fastly-customize-cache.md

@@ -16,7 +16,7 @@ The following sections provide an overview and instructions for configuring some
 Fastly provides the _Force TLS_ option to redirect unencrypted requests (HTTP) to Fastly. After your Staging or Production environment has been provisioned with a [valid SSL/TLS certificate]({{ site.baseurl }}/cloud/cdn/configure-fastly.html#provision-ssltls-certificates), you can update the Fastly configuration for your store to enable the Force TLS option. See the Fastly [Force TLS guide](https://github.com/fastly/fastly-magento2/blob/master/Documentation/Guides/FORCE-TLS.md) in the Fastly CDN Module for Magento 2 documentation.
 
 {:.bs-callout-info}
-Enabling the Force TLS option is a recommended best practice for Magento Commerce stores.
+Enabling the Force TLS option is a recommended best practice for {{ site.data.var.ece }} stores.
 
 ## Extend Fastly timeout
 

src/cloud/composer-packages/patch-notes.md

@@ -1,6 +1,6 @@
 ---
 group: cloud-guide
-title: Magento Commerce Cloud package updates
+title: Cloud package updates for Commerce
 functional_areas:
   - Cloud
   - Setup

src/cloud/docker/docker-config-sources.md

@@ -19,7 +19,7 @@ You can create the Docker Compose configuration to build and deploy the Docker c
 {:.bs-callout-info}
 When you build the Docker Compose configuration file, the `ece-docker build:compose` command overwrites the existing `docker-compose.yml` configuration file. You can save customizations for the Docker Compose configuration in a `docker-compose.override.yml` file.  If the `docker-compose.override.yml` file is present, then the override configuration merges with the base configuration. See [Override configuration].
 
-## Magento Commerce Cloud configuration
+## Cloud configuration for Commerce
 
 You need the following {{site.data.var.ece}} project configuration files to emulate a Cloud project in the Docker environment.
 

src/cloud/docker/docker-installation.md

@@ -6,22 +6,22 @@ functional_areas:
   - Configuration
 ---
 
-{{site.data.var.mcd-prod}} is one of the {{site.data.var.csuite}} packages designed to deploy and manage local {{site.data.var.ee}} Docker environments for both Cloud and On-premises projects.
+{{site.data.var.mcd-prod}} is one of the {{site.data.var.csuite}} packages designed to deploy and manage local {{site.data.var.ee}} Docker environments for both cloud and on-premises projects.
 
 If you are using {{ site.data.var.ee }} on Cloud, you most likely have the `{{ site.data.var.mcd-package }}` package installed together with the `{{site.data.var.ct-repo}}` package.
 
 An on-premises installation requires the stand-alone `{{ site.data.var.mcd-package }}` package available in the [Magento Cloud Docker GitHub repository](https://github.com/magento/magento-cloud-docker).
 
-## Initialize the Magento project
+## Initialize the Commerce project
 
-{{ site.data.var.mcd-prod }} supports the {{site.data.var.ee}} installation for both Cloud and On-premises projects. The initialization steps are different for each project type.
+{{ site.data.var.mcd-prod }} supports the {{site.data.var.ee}} installation for both cloud and on-premises projects. The initialization steps are different for each project type.
 
-### Magento Commerce Cloud projects
+### Cloud projects
 
 {:.procedure}
-To install a Magento Commerce Cloud project:
+To install a {{ site.data.var.ece }} project:
 
-1. Download a Magento application template from the [Magento Cloud repository][cloud-repo]. Be careful to select the branch that corresponds with the Magento version.
+1. Download an application template from the [Magento Cloud repository][cloud-repo]. Be careful to select the branch that corresponds with the Commerce version.
 
 1. Optionally, you can clone the latest template.
 
@@ -33,12 +33,12 @@ To install a Magento Commerce Cloud project:
 
 1. Add your [Magento access credentials][magento-creds] to the `auth.json` file.
 
-### Magento Commerce On-premises projects
+### On-premises projects
 
 When you initialize a {{site.data.var.ee}} project for Docker development, you must create a [.magento.docker.yml][unified configuration] configuration source file to create the Docker containers for the local environment.
 
 {:.procedure}
-To install a Magento Commerce On-premises project:
+To install an Adobe Commerce on-premises project:
 
 1. Create a project using [Composer]({{site.baseurl}}/guides/v2.4/install-gde/composer.html).
 

src/cloud/env/variables-build.md

@@ -137,7 +137,7 @@ stage:
 
 Allows you to increase the maximum expected execution time for static content deployment.
 
-By default, Magento Commerce sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
+By default, {{ site.data.var.ece }} sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
 
 ```yaml
 stage:

src/cloud/env/variables-deploy.md

@@ -494,7 +494,7 @@ stage:
 
 Allows you to increase the maximum expected execution time for static content deployment.
 
-By default, Magento Commerce sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
+By default, {{ site.data.var.ee }} sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
 
 ```yaml
 stage:

src/cloud/env/variables-global.md

@@ -65,7 +65,7 @@ return array(
 
 Allows you to increase the maximum expected execution time for static content deployment.
 
-By default, Magento Commerce sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
+By default, {{ site.data.var.ee }} sets the maximum expected execution to 900 seconds, but in some scenarios you might need more time to complete the static content deployment for a Cloud project.
 
 ```yaml
 stage:

src/cloud/live/live-prot.md

@@ -39,7 +39,7 @@ Unblocking is automated upon resolution of the security risk. The block is remov
 
 ## Opt out of the protective block
 
-The protective block is there to protect you against known vulnerabilities in the software you deploy on Magento Commerce.
+The protective block is there to protect you against known vulnerabilities in the software you deploy {{ site.data.var.ece }}.
 
 However, you can opt out of the protective block by adding the following to [`.magento.app.yaml`]({{ site.baseurl }}/cloud/project/magento-app.html):
 

src/cloud/live/site-launch-checklist.md

@@ -20,7 +20,7 @@ See [Test deployment]({{ site.baseurl }}/cloud/live/stage-prod-test.html) for te
 
 Magento provides a Let's Encrypt SSL/TLS certificate for each environment. This certificate is required for Fastly to serve secure traffic over HTTPS.
 
-To use this certificate, you must update your DNS configuration so that Magento can complete domain validation and apply the certificate to your environment. Each environment has a unique certificate that covers the domains for the Magento Commerce sites deployed in that environment. We recommend completing and the configuration updates during the [Fastly set up process]({{ site.baseurl }}/cloud/cdn/configure-fastly.html).
+To use this certificate, you must update your DNS configuration so that Magento can complete domain validation and apply the certificate to your environment. Each environment has a unique certificate that covers the domains for the {{ site.data.var.ece }} sites deployed in that environment. We recommend completing and the configuration updates during the [Fastly set up process]({{ site.baseurl }}/cloud/cdn/configure-fastly.html).
 
 ## Update DNS configuration with production settings {#dns}
 

src/cloud/live/stage-prod-live.md

@@ -48,7 +48,7 @@ For detailed information of the process, see [Pro Develop and Deploy Workflow]({
 
 ### Git and SSH URLs {#git-ssh}
 
-For Pro, locate your Git and SSH URLs from the OneDrive onboarding document you received when you signed up for Magento Commerce.
+For Pro, locate your Git and SSH URLs from the OneDrive onboarding document you received when you signed up for {{ site.data.var.ece }}.
 
 After you know these URLs, you can access those environments without further intervention.
 

src/cloud/project/new-relic.md

@@ -98,13 +98,13 @@ runtime:
 
 To connect a Cloud environment to New Relic, add the New Relic license key to the environment.
 
--  For Pro accounts, Magento adds the license key to your Cloud environments during the provisioning process. You can log in to your New Relic account to verify connectivity between your Magento Commerce site and New Relic.
+-  For Pro accounts, Adobe adds the license key to your Cloud environments during the provisioning process. You can log in to your New Relic account to verify connectivity between your {{ site.data.var.ece }} site and New Relic.
 
 -  For Starter accounts, you have a New Relic license key that supports up to three environments. You must add the key to your environment configurations manually. The license key is not pre-provisioned on Starter environments.
 
 ### Configure New Relic for Starter environments
 
-For Starter environments, enable the New Relic integration by adding the New Relic license key to the environment configuration. We recommend adding the key to the Staging and Production (master) environments and one other environment of your choice. Only the New Relic license key is required for configuration. You can find information about additional configuration options in the [New Relic reporting] topic in the _Magento Commerce User Guide_.
+For Starter environments, enable the New Relic integration by adding the New Relic license key to the environment configuration. We recommend adding the key to the Staging and Production (master) environments and one other environment of your choice. Only the New Relic license key is required for configuration. You can find information about additional configuration options in the [New Relic reporting] topic in the _Adobe Commerce User Guide_.
 
 {:.bs-callout-warning}
 Updating the environment configuration triggers a redeployment, which takes your site offline until deployment completes. For Production environments, we recommend completing this work during off-peak hours to avoid service disruptions. See [Working with variables].

src/cloud/project/privatelink-service.md

@@ -25,7 +25,7 @@ The PrivateLink service integration for {{site.data.var.ece}} projects includes
 -  You cannot establish SSH connections using PrivateLink. For SSH, use the Magento SSH capabilities. See [Enable SSH keys][].
 -  Magento support does not cover troubleshooting AWS PrivateLink issues beyond initial enablement.
 -  Customers are responsible for costs associated with managing their own VPC.
--  You cannot use the HTTPS protocol (port 443) to connect to Magento Commerce over PrivateLink.
+-  You cannot use the HTTPS protocol (port 443) to connect to {{ site.data.var.ece }} over PrivateLink.
 -  PrivateDNS is not available.
 
 ## PrivateLink connection types
@@ -36,7 +36,7 @@ The following network diagram shows the PrivateLink connection types available t
 
 You must determine the PrivateLink connection type required for your {{site.data.var.ece}} environments:
 
--  **Unidirectional PrivateLink**–Choose this configuration to retrieve data securely from a Magento Commerce store.
+-  **Unidirectional PrivateLink**–Choose this configuration to retrieve data securely from a {{ site.data.var.ece }} store.
 -  **Bidirectional PrivateLink**–Choose this configuration to establish secure connections to and from systems outside of the {{site.data.var.ece}} environment. The bidirectional option requires two connections:
    -  A connection between the customer VPC and the Magento VPC
    -  A connection between the Magento VPC and the customer VPC

src/cloud/project/project-upgrade-parent.md

@@ -7,9 +7,9 @@ functional_areas:
 ---
 The Upgrades and patches section contains detailed release notes for the `{{site.data.var.ct}}` package, and information on how to upgrade the `{{site.data.var.ct}}` package, upgrade {{site.data.var.ece}}, and apply custom patches and hotfixes.
 
-The Upgrades and patches section provides information about how to update `{{site.data.var.ct}}`, upgrade the Magento version, and how to [apply patches] to your {{site.data.var.ece}} project.
+The Upgrades and patches section provides information about how to update `{{site.data.var.ct}}`, upgrade the {{site.data.var.ee}} version, and how to [apply patches] to your {{site.data.var.ece}} project.
 
-Some restrictions in the core Magento Commerce code base affect your ability to update to a specific `{{site.data.var.ct}}` release or to upgrade Magento. Use the following table to determine the best path:
+Some restrictions in the {{site.data.var.ee}} code base affect your ability to update to a specific `{{site.data.var.ct}}` release or to upgrade. Use the following table to determine the best path:
 
 | Current Version | Upgrade Path | Instructions
 | --- | --- | --- |

src/cloud/project/projects.md

@@ -29,10 +29,10 @@ The following sections detail more about project and environment variables:
 
 ### Upgrade and patch {#upgrade}
 
-To upgrade and patch Magento, see:
+To upgrade and patch {{ site.data.var.ece }} projects, see:
 
--  [Upgrade and test Magento Commerce]({{ site.baseurl }}/cloud/project/project-upgrade.html)
--  [Patch and test Magento Commerce]({{ site.baseurl }}/cloud/project/project-patch.html)
+-  [Upgrade versions]({{ site.baseurl }}/cloud/project/project-upgrade.html)
+-  [Apply patches]({{ site.baseurl }}/cloud/project/project-patch.html)
 
 ## Access the Project Web Interface {#login}
 

src/cloud/release-notes/cloud-release-archive.md

@@ -103,7 +103,7 @@ The `{{site.data.var.ct}}` 2002.0.22 release changes the structure of the `{{sit
 
    -  {:.new}<!-- MAGECLOUD-3602 -->Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{ site.baseurl }}/cloud/env/variables-deploy.html#force_update_urls) content.
 
-   -  {:.new}<!-- MAGECLOUD-3643 -->Added the **TTFB_TESTED_PAGES** post-deploy variable to configure _Time to First Byte_  page tests to check Magento Commerce application performance on sites deployed to Cloud infrastructure. See the variable description in [post-deploy variables]({{ site.baseurl }}/cloud/env/variables-post-deploy.html).
+   -  {:.new}<!-- MAGECLOUD-3643 -->Added the **TTFB_TESTED_PAGES** post-deploy variable to configure _Time to First Byte_  page tests to check application performance on sites deployed to Cloud infrastructure. See the variable description in [post-deploy variables]({{ site.baseurl }}/cloud/env/variables-post-deploy.html).
 
    -  {:.fix}<!-- MAGECLOUD-3611 -->Fixed an issue with multi-threaded SCD, which caused random failures in static content deployment. The workaround involved setting the **SCD_THREADS** variable to `1`. You can now increase the count as needed. See the definitions in the [deploy variables]({{ site.baseurl }}/cloud/env/variables-deploy.html#scd_threads) and the [build variables]({{ site.baseurl }}/cloud/env/variables-build.html#scd_threads).
 
@@ -256,7 +256,7 @@ The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patc
 
    -  <!-- MAGECLOUD-2888 -->Now the Docker generator uses the services specified in the `.magento.app.yaml` and `.magento/services.yaml` configuration files when [building your Docker environment]({{ site.baseurl }}/cloud/docker/docker-config.html). You can choose a different service version using build parameters.
 
-   -  <!-- MAGECLOUD-2799 -->Added PHP 7.2 image—Added support for PHP 7.2 in Cloud Docker; updated the [Launch Docker configuration]({{ site.baseurl }}/cloud/docker/docker-config.html) to include the `docker:build --php` option to specify the version of PHP compatible with your Magento Commerce version.
+   -  <!-- MAGECLOUD-2799 -->Added PHP 7.2 image—Added support for PHP 7.2 in Cloud Docker; updated the [Launch Docker configuration]({{ site.baseurl }}/cloud/docker/docker-config.html) to include the `docker:build --php` option to specify the version of PHP compatible with your version of Adobe Commerce.
 
    -  <!-- MAGECLOUD-2565 -->Added a [Cron container]({{ site.baseurl }}/cloud/docker/docker-containers-cli.html#cron-container) based on the PHP-CLI image.