Merge pull request magento-devdocs/devdocs#2654 from magento-devdocs/hg-Nov21-imports

Nov21 fixes and imports

Author: hguthrie

src/_includes/install/patch/quality-patch-intro.md

@@ -2,4 +2,4 @@ The [Quality Patches Tool](https://github.com/magento/quality-patches) delivers
 
 {:.bs-callout-info}
 See [Apply patches]({{ site.baseurl }}/quality-patches/usage.html) for instructions on applying patches to your {{ site.data.var.ee }} or {{ site.data.var.ce }} projects.
-See [Patches available in the Quality Patches Tool](https://support.magento.com/hc/en-us/sections/360010506631-Patches-available-in-MQP-tool-) for additional patch details.
+See [Available Patches]({{ site.baseurl }}/quality-patches/tool.html#patch-grid) in the _Software Update Guide_ to review a full list of released patches.

src/cloud/project/manage-disk-space.md

@@ -135,7 +135,7 @@ The `.magento/services.yaml` file controls the disk space available to each serv
 {:.procedure}
 To increase disk space for a service:
 
-1. In your local development environment, open the `.magento/service.yaml` configuration file.
+1. In your local development environment, open the `.magento/services.yaml` configuration file.
 
 1. Add or find a service in the file. See [more about configuring services]({{ site.baseurl }}/cloud/project/services.html).
 

src/cloud/project/project-multi-sites.md

@@ -34,6 +34,18 @@ https://store.com/second/
 {:.bs-callout-tip}
 To add a store view to the site base URL, you do not have to create multiple directories. See [Add the store code to the base URL][addstorecode] in the _Config Guide_.
 
+## Add New Domains
+
+The process to add a new domain depends on the type of Cloud account:
+
+-  For Pro
+
+   You must open a Support ticket to request new domains to be added to the cluster.
+
+-  For Starter
+
+   You can add the new domain to Fastly for Production, or you can create a support ticket to request assistance. You must add the new domain to the **Domains** tab in the Program UI: `https://<zone>.magento.cloud/projects/<project-ID>/edit`
+
 ## Configure local installation
 
 To configure your local installation to use multiple stores, see [Multiple websites or stores][config-multiweb] in the _Config Guide_.

src/cloud/project/project-patch.md

@@ -9,7 +9,9 @@ functional_areas:
 [{{ site.data.var.mcp-prod }}](https://github.com/magento/magento-cloud-patches) and the [Quality Patches Tool](https://github.com/magento/quality-patches) deliver patches to your installed {{site.data.var.ee}} application.
 
 -  {{ site.data.var.mcp-prod }} delivers required patches with critical fixes
--  Quality Patches deliver optional, low-impact quality fixes as [individual patches]({{ site.baseurl }}/release/policy/#individual-patch), which do not contain backward incompatible changes.
+-  Quality Patches deliver optional, low-impact quality fixes as [individual patches]({{ site.baseurl }}/release/policy/#individual-patch) that do not contain backward incompatible changes
+
+See [Available Patches]({{ site.baseurl }}/quality-patches/tool.html#patch-grid) in the _Software Update Guide_ to review a full list of released patches.
 
 Both packages improve the integration of all {{site.data.var.ee}} versions with Cloud environments and support quick delivery of critical, optional, and custom fixes. You can use these packages to apply, revert, and view general information about all individual patches that are available for Magento.
 

src/guides/v2.3/config-guide/cache/two-level-cache.md

@@ -16,6 +16,9 @@ To reduce the network bandwidth to Redis, we can store cache data locally on eac
 
 Magento stores the hashed data version in Redis, with the suffix ':hash' appended to the regular key. In case of an outdated local cache, the data is transferred to the local machine with a cache adapter.
 
+{:.bs-callout-info}
+For {{ site.data.var.ece }}, consider the best practices in the [Extended Redis cache implementation](https://support.magento.com/hc/en-us/articles/360049292532) support article.
+
 ## Configuration example
 
 ```php

src/guides/v2.4/config-guide/cache/two-level-cache.md

@@ -16,6 +16,9 @@ To reduce the network bandwidth to Redis, we can store cache data locally on eac
 
 Magento stores the hashed data version in Redis, with the suffix ':hash' appended to the regular key. In case of an outdated local cache, the data is transferred to the local machine with a cache adapter.
 
+{:.bs-callout-info}
+For {{ site.data.var.ece }}, consider the best practices in the [Extended Redis cache implementation](https://support.magento.com/hc/en-us/articles/360049292532) support article.
+
 ## Configuration example
 
 Use the following example to modify or replace the existing cache section in the `app/etc/env.php` file.

src/quality-patches/tool.md

@@ -16,9 +16,10 @@ It allows you to:
 
 **{{site.data.var.ee}} support** and the **{{site.data.var.ce}} community** develop quality patches.
 
-{: .bs-callout-note}
-The Quality Patches Tool is for quality patches only. Security patches
-are available in the [Magento Security Center][security] .
+The Quality Patches Tool is for quality patches only. Security patches are available in the [Magento Security Center][security] .
+
+{:.bs-callout-warning}
+We do not recommend using the Quality Patches Tool to apply large numbers of patches, because it increases the complexity of your code, which makes upgrading to a new version of {{ site.data.var.ee }} or {{ site.data.var.ce }} more difficult.
 
 ## Available patches   {#patch-grid}