Merge pull request #323 from magento-kb/Title-change-1

Title change
manavluhar · Jun 16, 2021 · fbaf0f7 · fbaf0f7
2 parents 9494354 + 1d3eaab
commit fbaf0f7
Show file tree

Hide file tree

Showing 6 changed files with 24 additions and 27 deletions.
diff --git a/...ral/display-magento-error-report-number-instead-of-fastly-503-error-on-cloud.md b/...ral/display-magento-error-report-number-instead-of-fastly-503-error-on-cloud.md
@@ -1,5 +1,5 @@
 ---
-title: Display Magento error report number instead of Fastly's 503 error on Cloud
+title: Display Magento error report number instead of Fastly 503 error
 labels: 503,Fastly,Magento Commerce Cloud,Pro,debug,error,how to,production,reports,staging
 ---
 
@@ -26,4 +26,3 @@ Once you see the authentic Magento error and the error report number, you may ge
 ```clike
 {server_IP} {store_domain}
 ```
-
diff --git a/...neral/magento-cloud-reduce-deployment-downtime-with-configuration-management.md b/...neral/magento-cloud-reduce-deployment-downtime-with-configuration-management.md
@@ -1,5 +1,5 @@
 ---
-title: Magento Cloud: reduce deployment downtime with Configuration Management
+title: Reduce deployment downtime on Magento Cloud
 labels: 2.1.4,2.2,2.2.x,Magento Commerce Cloud,cloud,configuration,deployment,downtime,how to,management,pipeline
 ---
 
@@ -31,8 +31,7 @@ We strongly recommend applying the Configuration Management approach in your dep
 
 ## Configuration Management on DevDocs
 
-* [Configuration management for **2.1.X** ](http://devdocs.magento.com/guides/v2.1/cloud/live/sens-data-over.html) and the [example](http://devdocs.magento.com/guides/v2.1/cloud/live/sens-data-initial.html) in the *Magento Commerce (Cloud) Guide* 
-* [Configuration management for **2.2.X** ](http://devdocs.magento.com/guides/v2.2/cloud/live/sens-data-over.html) and the [example](http://devdocs.magento.com/guides/v2.2/cloud/live/sens-data-initial.html) in the *Magento Commerce (Cloud) Guide* 
+* [Configuration management for **2.1.X** ](http://devdocs.magento.com/guides/v2.1/cloud/live/sens-data-over.html) and the [example](http://devdocs.magento.com/guides/v2.1/cloud/live/sens-data-initial.html) in the *Magento Commerce (Cloud) Guide*
+* [Configuration management for **2.2.X** ](http://devdocs.magento.com/guides/v2.2/cloud/live/sens-data-over.html) and the [example](http://devdocs.magento.com/guides/v2.2/cloud/live/sens-data-initial.html) in the *Magento Commerce (Cloud) Guide*
 * [Upgrade from 2.0.X or 2.1.X](http://devdocs.magento.com/guides/v2.2/cloud/project/project-upgrade.html#old-version) section of the *Upgrade Magento Commerce (Cloud)* topic
-* [Pipeline Deployment](http://devdocs.magento.com/guides/v2.2/config-guide/deployment/) in the *Magento Configuration Guide* — For Magento Commerce (Cloud), you do not need to follow the instructions in this guide. The content is strictly for reference. We already provide the build server, integration environments, and more with Cloud. ** 
-
+* [Pipeline Deployment](http://devdocs.magento.com/guides/v2.2/config-guide/deployment/) in the *Magento Configuration Guide* — For Magento Commerce (Cloud), you do not need to follow the instructions in this guide. The content is strictly for reference. We already provide the build server, integration environments, and more with Cloud. **
diff --git a/...l/mdva-22026-magento-patch-unable-to-import-product-images-from-external-url.md b/...l/mdva-22026-magento-patch-unable-to-import-product-images-from-external-url.md
@@ -1,5 +1,5 @@
 ---
-title: MDVA-22026 Magento patch: Unable to import product images from external URL
+title: "MDVA-22026: Unable to import product images from external URL"
 labels: 2.3.2,2.3.2-p2,2.3.3,2.3.3-p1,MQP 1.0.20,MQP patches,Magento Commerce,Magento Commerce Cloud,Magento Quality Patches,external URL,import,product image
 ---
 
@@ -55,4 +55,4 @@ To learn more about Magento Quality Patches, refer to:
 * [Magento Quality Patches released: a new tool to self-serve quality patches](https://support.magento.com/hc/en-us/articles/360047139492) .
 * [Check patch for Magento issue with Magento Quality Patches](https://support.magento.com/hc/en-us/articles/360047125252) .
 
-For info about other patches available in MQP tool, refer to the [Patches available in MQP tool](https://support.magento.com/hc/en-us/sections/360010506631-Patches-available-in-MQP-tool-) section.
+For info about other patches available in MQP tool, refer to the [Patches available in MQP tool](https://support.magento.com/hc/en-us/sections/360010506631-Patches-available-in-MQP-tool-) section.
diff --git a/.../deployment-errors-from-enabling-early-alpha-baler-javascript-bundling-build.md b/.../deployment-errors-from-enabling-early-alpha-baler-javascript-bundling-build.md
@@ -1,5 +1,5 @@
 ---
-title: Deployment errors from enabling early-alpha Baler Javascript bundling build
+title: Deployment errors from enabling early-alpha Baler module
 labels: 2.3.x,2.4.x,Baler,Javascript,Magento Commerce,Magento Commerce Cloud,deploy,deployment,deployment error,deployment fails,github,troubleshooting
 ---
 
@@ -18,12 +18,12 @@ The merchant experiences deployment errors when using the Baler module on a prod
 
 We do not recommend that merchants use Baler module on a production environment, as it is currently in the early alpha development stage. Using it can result in deployment errors.
 
- <span class="wysiwyg-underline">Steps to reproduce</span> 
+ <span class="wysiwyg-underline">Steps to reproduce</span>
 
 1. The merchant tries to insert the **SCD\_USE\_BALER** variable in the build stage of the `.magento.env.yaml` file, which enables the Baler Javascript bundling package.
 1. The merchant also adds the Baler composer dependency: `"magento/module-baler": "1.0.0-alpha"` to `require` section of `composer.json` .
 
- <span class="wysiwyg-underline">Actual result</span> 
+ <span class="wysiwyg-underline">Actual result</span>
 
 The merchant sees the following error message in the deployment logs on the cloud, which is `<project home>/var/log/cloud.log` , upon the static content deploy stage:
 
@@ -32,7 +32,7 @@ The merchant sees the following error message in the deployment logs on the clou
         [2020-08-19 12:06:12] WARNING:  - Path to baler executable could not be found. The Node package may not be installed or may not be linked.
 ```
 
- <span class="wysiwyg-underline">Expected result</span> 
+ <span class="wysiwyg-underline">Expected result</span>
 
 Successful deployment.
 
@@ -45,6 +45,6 @@ The Baler module is currently in the early alpha development stage, and the Bale
 You can review existing Baler Alpha documentation at [Github/Magento/Baler/Getting started with the alpha](https://github.com/magento/baler/blob/master/docs/ALPHA.md) . [ ](https://github.com/magento/baler/blob/master/docs/ALPHA.md) However, it is not ready for production use, and it is used at your own risk.  It is recommended instead that you merge or bundle Javascript (JS) files using Magento’s built-in bundling (basic bundling) for file optimization.
 
 * You can turn on merging or bundling in Magento’s Admin UI (merging and bundling cannot be enabled at the same time): **Stores** > **Settings** > **Configuration** > **Advanced** > **Developer** > **JavaScript Settings** .
-* You can also enable Magento’s built-in bundling (basic bundling) from the command line: `php -f bin/magento config:set dev/js/enable_js_bundling 1` 
+* You can also enable Magento’s built-in bundling (basic bundling) from the command line: `php -f bin/magento config:set dev/js/enable_js_bundling 1`
 
-To learn more, refer to [CSS and Javascript file optimization on Magento Commerce Cloud and Magento](https://support.magento.com/hc/en-us/articles/360044482152) .
+To learn more, refer to [CSS and Javascript file optimization on Magento Commerce Cloud and Magento](https://support.magento.com/hc/en-us/articles/360044482152) .
diff --git a/...l/magento-2.4.1-known-issue-unable-to-change-amazon-account-in-google-chrome.md b/...l/magento-2.4.1-known-issue-unable-to-change-amazon-account-in-google-chrome.md
@@ -1,5 +1,5 @@
 ---
-title: Magento 2.4.1 known issue: unable to change Amazon account in Google Chrome
+title: "Magento 2.4.1 issue: unable to change Amazon account in Chrome"
 labels: 2.4.1,Amazon Pay,Javascript,Magento Commerce,Magento Commerce Cloud,browser,cookies,known issues,troubleshooting
 ---
 
@@ -14,7 +14,7 @@ This article describes a known Magento 2.4.1 issue where customers get signed in
 
 Customers get signed in to the previously used Amazon accounts instead of being suggested to log in, when using Amazon Pay during checkout.
 
- <span class="wysiwyg-underline">Steps to reproduce:</span> 
+ <span class="wysiwyg-underline">Steps to reproduce:</span>
 
 1. On storefront, add any item to the shopping cart and proceed to guest checkout.
 1. Click the **Amazon Pay** button. Amazon.com sign in pop-up appears.
@@ -40,4 +40,4 @@ The issue might happen in one of the following situations:
 
 ## Solution
 
-Make sure Amazon Pay iframe requests are not blocked by browsers.
+Make sure Amazon Pay iframe requests are not blocked by browsers.
diff --git a/...l/when-pushed-from-git-environments-placed-under-production-on-magento-cloud.md b/...l/when-pushed-from-git-environments-placed-under-production-on-magento-cloud.md
@@ -1,5 +1,5 @@
 ---
-title: When pushed from git environments placed under production on Magento Cloud
+title: New environments placed under production when pushed from Git
 labels: 2.3,2.3.x,2.4,2.4.x,Magento Cloud CLI,Magento Commerce Cloud,command line,develop,git,production,staging,troubleshooting
 ---
 
@@ -11,21 +11,21 @@ This article provides a solution for the issue where new environments are placed
 
 ## Issue
 
- <span class="wysiwyg-underline">Steps to reproduce:</span> 
+ <span class="wysiwyg-underline">Steps to reproduce:</span>
 
  <span class="wysiwyg-underline">Prerequisites</span> : Have a local git controlled clone of the project.
 
 You need to create an integration branch from the staging branch:
 
-1. Switch to the staging branch by running the following command in the local shell: `git checkout staging` 
-1. Create an integration branch from the staging branch by running the following command in the local shell: `git checkout -b <branch>` 
-1. Push the branch to the remote repository and set up an upstream branch by running the following command in the local shell: `git push --set-upstream origin <branch>` 
+1. Switch to the staging branch by running the following command in the local shell: `git checkout staging`
+1. Create an integration branch from the staging branch by running the following command in the local shell: `git checkout -b <branch>`
+1. Push the branch to the remote repository and set up an upstream branch by running the following command in the local shell: `git push --set-upstream origin <branch>`
 
- <span class="wysiwyg-underline">Actual result:</span> 
+ <span class="wysiwyg-underline">Actual result:</span>
 
 The new branch was created under the production branch.
 
- <span class="wysiwyg-underline">Expected result:</span> 
+ <span class="wysiwyg-underline">Expected result:</span>
 
 The new branch is created under the staging branch.
 
@@ -41,11 +41,10 @@ To update a parent for the existing branch on the server, please use the `magent
 
 Example of usage:
 
- `magento-cloud environment:info parent Staging` 
+ `magento-cloud environment:info parent Staging`
 
 This will set the parent branch to "Staging" for the currently checked out branch.
 
 ## Related reading
 
 * DevDocs [Magento Commerce Cloud > Magento Cloud CLI](https://devdocs.magento.com/cloud/reference/cli-ref-topic.html) .
-