Merge pull request magento-commerce/devdocs#2489 from magento-devdocs/DOC-480-rebrand

Rebranding: Updated references to Magento Marketplace

Author: jeff-matthews

src/_data/main-nav.yml

@@ -202,7 +202,7 @@
       url: /live-search/overview.html
       versionless: true
 
-    - label: Magento Marketplace
+    - label: Commerce Marketplace
       url: /marketplace/sellers/getting-started.html
       versionless: true
 

src/_data/toc/php-developer-guide.yml

@@ -73,7 +73,7 @@ pages:
         - label: Package a component
           url: /extension-dev-guide/package/package_module.html
 
-        - label: Upload your component to the Magento Marketplace
+        - label: Upload your component to the Commerce Marketplace
           url: /extension-dev-guide/package/package_mktpl.html
 
     - label: Validate

src/_data/whats-new.yml

@@ -629,7 +629,7 @@ entries:
   - Major Update
   - 'Progress: done'
 - description: Added a new topic describing [Extension Footprint Analysis](https://devdocs.magento.com/marketplace/sellers/extension-footprint.html)
-    on the Magento Marketplace.
+    on the Commerce Marketplace.
   versions: 2.x
   type: New Topic
   date: May 27, 2021
@@ -2023,7 +2023,7 @@ entries:
 - description: Updated the [Submit for Technical Review](https://devdocs.magento.com/marketplace/sellers/submit-for-technical-review.html)
     topic in the _Marketplace Developer Guide_ with detailed information about the
     technical review guidelines, tests, tools, and processes that Magento uses to
-    verify and validate third-party extensions submitted to the Magento Marketplace
+    verify and validate third-party extensions submitted to the Commerce Marketplace
     Developer Portal.
   versions: 2.x
   type: Major Update

src/_includes/cloud/error-codes.md

@@ -33,7 +33,7 @@ Critical errors indicate a problem with the {{ site.data.var.ece }} project conf
 | 23 |  | Unable to create a logger object |  |
 | 24 | backup-data: static-content | Failed to clean the `./init/pub/static/` directory | Failed to clean `./init/pub/static` folder. Check your filesystem permissions. |
 | 25 |  | Cannot find the Composer package | If you installed the Magento application version directly from the Magento git repository, verify that the `DEPLOYED_MAGENTO_VERSION_FROM_GIT` environment variable is configured. |
-| 26 | validate-config | Remove Magento Braintree module configuration which is no longer supported in Magento 2.4 and later versions. | Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree payment support, use an official extension from the Magento Marketplace instead. |
+| 26 | validate-config | Remove Magento Braintree module configuration which is no longer supported in Magento 2.4 and later versions. | Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree payment support, use an official extension from the Commerce Marketplace instead. |
 
 ### Deploy stage
 
@@ -72,7 +72,7 @@ Critical errors indicate a problem with the {{ site.data.var.ece }} project conf
 | 130 | install-update: cache_type | Command failed: `php ./bin/magento cache:enable` | Command `php ./bin/magento cache:enable` runs only when Magento was installed but `./app/etc/env.php` file was absent or empty at the beginning of the deployment. Check the `cloud.log` for more information. Add `VERBOSE_COMMANDS: '-vvv'` into `.magento.env.yaml` for more detailed command output. |
 | 131 | install-update | The `crypt/key`  key value does not exist in the `./app/etc/env.php` file or the `CRYPT_KEY` cloud environment variable | This error occurs if the `./app/etc/env.php` file is not present when Magento deployment begins, or if the `crypt/key` value is undefined. If you migrated the database from another environment, retrieve the crypt key value from that environment. Then, add the value to the [CRYPT_KEY](https://devdocs.magento.com/cloud/env/variables-deploy.html#crypt_key) cloud environment variable in your current environment. See [Add the Magento encryption key](https://devdocs.magento.com/cloud/setup/first-time-setup-import-import.html#encryption-key). If you accidentally removed the `./app/etc/env.php` file, use the following command to restore it from the backup files created from a previous deployment: `./vendor/bin/ece-tools backup:restore` CLI command ." |
 | 132 |  | Can not connect to the Elasticsearch service | Check for valid Elasticsearch credentials and verify that the service is running |
-| 133 | validate-config | Remove Magento Braintree module configuration which is no longer supported in Magento 2.4 and later versions. | Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree support, use an official Braintree Payments extension from the Magento Marketplace instead. |
+| 133 | validate-config | Remove Magento Braintree module configuration which is no longer supported in Magento 2.4 and later versions. | Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree support, use an official Braintree Payments extension from the Commerce Marketplace instead. |
 | 134 | validate-config | Magento 2.4.0 requires Elasticsearch service to be installed | Install Elasticsearch service |
 | 135 | validate-config | The search engine must be set to Elasticsearch for Magento >= 2.4.0 | Check the SEARCH_CONFIGURATION variable for the `engine` option. If it is configured, remove the option, or set the value to "elasticsearch". |
 | 136 | validate-config | Split Database was removed starting from Magento 2.5.0. | If you use split database you have to revert to or migrate to a single database or use an alternative approach. |

src/_includes/config/split-deploy/split-deploy-overview.md

@@ -11,7 +11,7 @@ Because you deploy static assets and compile code on a machine separate from you
 We use the following terms to describe the systems involved with deployment.
 
 Development system
-: Machine on which developers work to customize code; and install extensions, themes, and language packages from Magento Marketplace. In addition, you make all configuration changes on your development system. You can have many development systems.
+: Machine on which developers work to customize code; and install extensions, themes, and language packages from Commerce Marketplace. In addition, you make all configuration changes on your development system. You can have many development systems.
 
 Build system
 : One system on which you deploy static assets and compile code for your production system. Because you build these assets on a system not in production, your production system's downtime is minimized.

src/_includes/install/auth-tokens-get.md

@@ -1,16 +1,16 @@
-The `repo.magento.com` repository is where Magento 2 and third-party Composer packages are stored and requires authentication. Use your Magento Marketplace account to generate a pair of 32-character *authentication keys* to access the repository.
+The `repo.magento.com` repository is where Magento 2 and third-party Composer packages are stored and requires authentication. Use your Commerce Marketplace account to generate a pair of 32-character *authentication keys* to access the repository.
 
 {:.bs-callout-info}
 For access to {{site.data.var.ee}} and {{site.data.var.ece}} packages, you must use keys associated with a MAGEID that has been granted access to those packages. If you encounter errors, you may not be authorized to access the package. Contact [Magento support](https://magento.com/support) for assistance with your MAGEID.
 
 To create authentication keys:
 
-1. Log in to the [Magento Marketplace](https://marketplace.magento.com){:target="_blank"}. If you don't have an account, click **Register**.
+1. Log in to the [Commerce Marketplace](https://marketplace.magento.com){:target="_blank"}. If you don't have an account, click **Register**.
 1. Click your account name in the top-right of the page and select **My Profile**.
 
 1. Click **Access Keys** in the Marketplace tab.
 
-   ![Get your secure access keys on Magento Marketplace]({{ site.baseurl }}/common/images/cloud/cloud_access-key.png){:width="500px"}
+   ![Get your secure access keys on Commerce Marketplace]({{ site.baseurl }}/common/images/cloud/cloud_access-key.png){:width="500px"}
 
 1. Click **Create a New Access Key**. Enter a specific name for the keys (e.g., the name of the developer receiving the keys) and click **OK**.
 

src/_includes/php-dev/composer-types.md

@@ -1,9 +1,9 @@
-The following table discusses the component types that Magento Marketplace supports. The composer `type` column in the following table specifies the value of the `type` field you must add to `composer.json` for that type of component.
+The following table discusses the component types that Commerce Marketplace supports. The composer `type` column in the following table specifies the value of the `type` field you must add to `composer.json` for that type of component.
 
 |Friendly name|composer.json type|Description|
 |--- |--- |--- |
 |Metapackage|metapackage|Technically, a Composer package type, not a Magento component type. A metapackage consists of only a `composer.json` file that specifies a list of components and their dependencies. For example, both {{site.data.var.ce}} and {{site.data.var.ee}} are metapackages.|
-|Module|magento2-module|Code that modifies Magento application behavior. You can upload a single module to the Magento Marketplace or your module can be dependent on some parent package.|
+|Module|magento2-module|Code that modifies Magento application behavior. You can upload a single module to the Commerce Marketplace or your module can be dependent on some parent package.|
 |Theme|magento2-theme|Code that modifies the look and feel of the storefront or Magento Admin.|
 |Language package|magento2-language|Translations for the storefront or Admin.|
 |Library|magento2-library|Support for libraries located in `lib/internal` instead of in the `vendor` directory.|

src/cloud/before/before-setup-env-install.md

@@ -52,7 +52,7 @@ You need authentication keys to install {{site.data.var.ee}} in your local devel
 {:.procedure}
 To create authentication keys:
 
-1. Log in to the [Magento Marketplace](https://marketplace.magento.com). If you do not have an account, click **Register**.
+1. Log in to the [Commerce Marketplace](https://marketplace.magento.com). If you do not have an account, click **Register**.
 
 1. Click your account name in the top-right and select **My Profile**.
 

src/cloud/before/before-workspace.md

@@ -39,7 +39,7 @@ Developing code for {{site.data.var.ee}} requires working in Git branches. Not e
 Have the following prepared to complete your initial workspace and project setup:
 
 *  {{site.data.var.ece}} account with an added user account
-*  Authentication keys from the Magento Marketplace. If the License Owner or Technical Lead created the project according to these instructions, the [Authentication keys]({{ site.baseurl }}/guides/v2.3/install-gde/prereq/connect-auth.html) should already be installed and available in the auth.json file in the code repository.
+*  Authentication keys from the Commerce Marketplace. If the License Owner or Technical Lead created the project according to these instructions, the [Authentication keys]({{ site.baseurl }}/guides/v2.3/install-gde/prereq/connect-auth.html) should already be installed and available in the auth.json file in the code repository.
 
 ## Get started
 

src/community/best-practices.md

@@ -27,7 +27,7 @@ The DevDocs and Magento teams verified and provide the following best practices
 *  [Best Practices for Extension Development]({{ site.baseurl }}/guides/v2.4/ext-best-practices/bk-ext-best-practices.html)
 *  [Upgrade Best Practices]({{ site.baseurl }}/guides/v2.4/comp-mgr/upgrade-best-practices.html)
 
-   We also recommend the [Magento Marketplace Help Center](https://marketplacesupport.magento.com/hc/en-us) for extension questions.
+   We also recommend the [Commerce Marketplace Help Center](https://marketplacesupport.magento.com/hc/en-us) for extension questions.
 
 *  [Programming Best Practices]({{ site.baseurl }}/guides/v2.4/ext-best-practices/extension-coding/common-programming-bp.html)
 *  [Observers Best Practices]({{ site.baseurl }}/guides/v2.4/ext-best-practices/extension-coding/observers-bp.html)