Merge branch 'gm_Fix-Git-ref' of github.com:magento-devdocs/devdocs into gm_Fix-Git-ref

gamarshall · gamarshall · commit 35eca68257b9 · 2022-03-15T15:10:10.000-07:00
diff --git a/src/_includes/contributor/2-4-submission.md b/src/_includes/contributor/2-4-submission.md
@@ -1,3 +1,3 @@
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 **v2.4 Contribution Notice:**
 Magento is focusing development efforts on v2.4, so we are no longer accepting pull requests to the v2.3, v2.2, v2.1, and v2.0 release lines.
diff --git a/src/cloud/docker/docker-manage-database.md b/src/cloud/docker/docker-manage-database.md
@@ -154,7 +154,7 @@ To import a database dump into the Docker environment:
    magento-cloud db:dump
    ```
 
-   {: .bs-callout-note }
+   {: .bs-callout-info }
    The `magento-cloud db:dump` command runs the [mysqldump][] command with the `--single-transaction` flag, which allows you to back up your database without locking the tables.
 
 1. Place the resulting SQL file into the `.docker/mysql/docker-entrypoint-initdb.d` folder.
diff --git a/src/cloud/env/variables-build.md b/src/cloud/env/variables-build.md
@@ -167,7 +167,7 @@ stage:
     SCD_MAX_EXECUTION_TIME: 3600
 ```
 
-{% include cloud/note-increase-scd-max-execution-time-variable.md%}
+{% include cloud/note-increase-scd-max-execution-time-variable.md %}
 
 ### `SCD_STRATEGY`
 
@@ -260,7 +260,7 @@ stage:
 
 Enable or disable the [Symfony](https://symfony.com/doc/current/console/verbosity.html) debug verbosity level for `bin/magento` CLI commands performed during the deployment phase.
 
-{:.bs-callout}
+{: .bs-callout-info }
 To use VERBOSE_COMMANDS to control the detail in command output for both successful and failed `bin/magento` CLI commands, you must set [MIN_LOGGING_LEVEL]({{ site.baseurl }}/cloud/env/variables-global.html#min_logging_level) `debug`.
 
 Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`.
diff --git a/src/cloud/env/variables-deploy.md b/src/cloud/env/variables-deploy.md
@@ -486,7 +486,7 @@ stage:
     SCD_MAX_EXECUTION_TIME: 3600
 ```
 
-{% include cloud/note-increase-scd-max-execution-time-variable.md%}
+{% include cloud/note-increase-scd-max-execution-time-variable.md %}
 
 ### `SCD_NO_PARENT`
 
@@ -640,7 +640,7 @@ stage:
 
 Enable or disable the [Symfony](https://symfony.com/doc/current/console/verbosity.html) debug verbosity level for `bin/magento` CLI commands performed during the deployment phase.
 
-{:.bs-callout}
+{: .bs-callout-info }
 To use the VERBOSE_COMMANDS setting to control the detail in command output for both successful and failed `bin/magento` CLI commands, you must set [MIN_LOGGING_LEVEL]({{ site.baseurl }}/cloud/env/variables-global.html#min_logging_level) `debug`.
 
 Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`.
diff --git a/src/cloud/env/variables-global.md b/src/cloud/env/variables-global.md
@@ -29,7 +29,7 @@ stage:
     MIN_LOGGING_LEVEL: debug
 ```
 
-{: .bs-callout .bs-callout-warning }
+{: .bs-callout-warning }
 The setting for the `MIN_LOGGING_LEVEL` variable does not change the log level configuration for the file handler, which is set to `debug` by default.
 
 ### `SCD_ON_DEMAND`
diff --git a/src/cloud/project/project-enable-mfa-enforcement.md b/src/cloud/project/project-enable-mfa-enforcement.md
@@ -15,7 +15,7 @@ For added security, {{site.data.var.ece}} provides multi-factor authentication (
 
 When MFA is enabled on a project, all {{site.data.var.ece}} accounts with SSH access must follow an authentication workflow that requires either a two-factor authentication (TFA) code or API token and an SSH certificate to access the environment.
 
-{:.bs.callout-important}
+{:.bs-callout-info}
 MFA is not enabled on Cloud projects by default. The Account owner for the {{ site.data.var.ece }} project must submit a {{site.data.var.ee}} support request to enable it. As soon as MFA is turned on, all users must have two-factor authentication (TFA) enabled on their {{ site.data.var.ece }} account for SSH access to the project environments.
 
 ## Certificates for SSH access
@@ -211,7 +211,7 @@ To connect using SSH with an API token credential:
 ### Example automated SSH script
 
 There are two options for storing the API token.
-{:.bs.callout-important}
+{:.bs-callout-info}
 If an API token is stored, the `magento-cloud` CLI will automatically authenticate and there is no need to perform the `mgc login` command
 
 #### Create an environment variable to store the API token.
diff --git a/src/extensions/amazon-sales/index.md b/src/extensions/amazon-sales/index.md
@@ -3,7 +3,7 @@ group: extensions
 title: Install Amazon Sales Channel
 ---
 
-{:.bs-callout .bs-callout-warning}
+{: .bs-callout-warning }
 Amazon Sales Channel versions 4.0+ are only supported when integrated with Magento 2.3.x versions.
 
 The Amazon Sales Channel extension installs and adds features to integrate your Magento catalog with Amazon Seller Accounts to sell through the Amazon Marketplace. To review additional information, see the [Amazon Sales Channel Marketplace](http://marketplace.magento.com/magento-module-amazon.html) page.
diff --git a/src/extensions/amazon-sales/release-notes/index.md b/src/extensions/amazon-sales/release-notes/index.md
@@ -2,7 +2,7 @@
 group: extensions
 title: Amazon Sales Channel Release Notes
 ---
-{:.bs-callout .bs-callout-warning}
+{: .bs-callout-warning }
 Amazon Sales Channel versions 4.0.0 and 4.1.0 are only supported for {{site.data.var.ee}} 2.3.x versions.<br/>Amazon Sales Channel version 4.2.0 is compatible with {{site.data.var.ee}} 2.3.x versions but is only supported for {{site.data.var.ee}} 2.4.x versions.
 
 **Amazon Sales Channel** can be installed on instances with {{site.data.var.ce}}, {{site.data.var.ee}}, and {{site.data.var.ece}} versions 2.3.x and 2.4.x. We no longer support the extension on {{site.data.var.ee}} 2.1, Magento 2.2, or Magento 1. Merchants can use Amazon Sales Channel to integrate with an Amazon Seller account to list and sell products from your Magento catalog on Amazon.
@@ -134,7 +134,7 @@ Amazon Sales Channel 4.1.0 is compatible with {{site.data.var.ee}} 2.3.x of {{si
 
 Amazon Sales Channel 4.0.0 is compatible with {{site.data.var.ee}} versions 2.3.0, 2.3.1, 2.3.2, 2.3.3, and 2.3.4 of {{site.data.var.ce}}, {{site.data.var.ee}}, and {{site.data.var.ece}}. This version of Amazon Sales Channel includes many user-interface upgrades, along with minor bug fixes.
 
-{:.bs-callout .bs-callout-warning}
+{: .bs-callout-warning }
 Amazon Sales Channel 4.0.0 is not supported for {{site.data.var.ee}} 2.3.5. For support with {{site.data.var.ee}} 2.3.5, upgrade to Amazon Sales Channel 4.1.0.
 
 -  {:.new}Introduced a new [Amazon Sales Channel](https://docs.magento.com/m2/ee/user_guide/sales-channels/asc/amazon-sales-channel-home.html) home page with improved "card view" for your store information.
diff --git a/src/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.md b/src/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.md
@@ -107,7 +107,7 @@ Sample result:
 {:.bs-callout-info}
 Enabling a [cache type](https://glossary.magento.com/cache-type) automatically clears that cache type.
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 As of version 2.3.4, Magento caches all system EAV attributes as they are retrieved. Caching EAV attributes in this manner improves performance, because it decreases the amount of insert/select requests to the DB. However, it increases cache network size as well. Developers can cache custom EAV attributes by running the `bin/magento config:set dev/caching/cache_user_defined_attributes 1` command. This can also be done from the Admin while in [Developer mode]({{ page.baseurl }}/config-guide/bootstrap/magento-modes.html) by setting **Stores** > Settings **Configuration** > **Advanced** > **Developer** > **Caching Settings** > **Cache User Defined Attributes** to **Yes**.
 
 ## Clean and flush cache types {#config-cli-subcommands-cache-clean}
diff --git a/src/guides/v2.3/extension-dev-guide/attributes.md b/src/guides/v2.3/extension-dev-guide/attributes.md
@@ -36,7 +36,7 @@ In this case, when `getCustomAttributes()` is called, the system returns only cu
 
 The `Customer` module provides a `system` option for its attributes. As a result, the `getCustomAttributes()` method only returns those EAV attributes that are not defined as `system` attributes. If you create custom attributes programmatically, set the `system` option to 'false' if you want to include the attribute in the `custom_attributes` array.
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 As of version 2.3.4, Magento caches all system EAV attributes as they are retrieved. This behavior is defined in each affected module's `di.xml` file as the `attributesForPreload` argument for `<type name="Magento\Eav\Model\Config">`. Developers can cache custom EAV attributes by running the `bin/magento config:set dev/caching/cache_user_defined_attributes 1` command. This can also be done from the Admin while in Develop mode by setting **Stores** > Settings **Configuration** > **Advanced** > **Developer** > **Caching Settings** > **Cache User Defined Attributes** to **Yes**. Caching EAV attributes while retrieving improves performance as it decreases the amount of insert/select requests to the DB, but it increases the cache network size.
 
 ### Adding Customer EAV attribute for backend only {#customer-eav-attribute}
diff --git a/src/guides/v2.3/extension-dev-guide/events-and-observers.md b/src/guides/v2.3/extension-dev-guide/events-and-observers.md
@@ -168,7 +168,7 @@ The `observer` [xml](https://glossary.magento.com/xml) element has the following
 *  `disabled` - Determines whether this observer is active or not. Default value is false.
 *  `shared` - Determines the [lifestyle]({{ page.baseurl }}/extension-dev-guide/build/di-xml-file.html#object-lifestyle-configuration) of the class. Default is `true`.
 
-{: .bs-callout .bs-callout-warning}
+{: .bs-callout-warning}
 The observer name must be unique, or an override will occur.
 
 Below is an example of how to assign observers to watch certain events:
diff --git a/src/guides/v2.3/frontend-dev-guide/templates/template-email.md b/src/guides/v2.3/frontend-dev-guide/templates/template-email.md
@@ -400,7 +400,7 @@ Incorrect:
 {% raw %}{{trans "Thank you for your order from %store_name." store_name = $store.getFrontendName()}}{% endraw %}
 ```
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 Exception: argument value can contain spaces if it is enclosed in brackets.
 
 ## Supported email clients and devices {#supported-clients}
diff --git a/src/guides/v2.3/graphql/mutations/redeem-giftcard-balance.md b/src/guides/v2.3/graphql/mutations/redeem-giftcard-balance.md
@@ -6,7 +6,7 @@ ee_only: True
 
 The `redeemGiftCardBalanceAsStoreCredit` mutation converts the entire balance of a gift card to store credit. The gift card must be redeemable and cannot have a balance of 0 at the time you run the mutation. After successfully running the mutation, the value of the gift card changes to 0.
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 Run this mutation on behalf of logged-in customers only. [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) describes how to send a request as a customer.
 
 ## Syntax
diff --git a/src/guides/v2.3/graphql/tutorials/checkout/checkout-add-product-to-cart.md b/src/guides/v2.3/graphql/tutorials/checkout/checkout-add-product-to-cart.md
@@ -26,7 +26,7 @@ GraphQL supports all product types, but this tutorial only demonstrates how to a
 
 Use the `updateCartItems` mutation to update shopping cart items and `removeItemFromCart` to remove a product from the shopping cart.
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 If you add a product to the shopping cart as a registered customer, be sure to send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more details.
 
 ## Add a simple product into the shopping cart
diff --git a/src/guides/v2.3/graphql/tutorials/checkout/checkout-shipping-method.md b/src/guides/v2.3/graphql/tutorials/checkout/checkout-shipping-method.md
@@ -22,7 +22,7 @@ The `setShippingMethodsOnCart` mutation defines the shipping methods for your or
 
 `{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 For logged-in customers, send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
 
 **Request:**
diff --git a/src/guides/v2.3/install-gde/install/cli/install-cli-install.md b/src/guides/v2.3/install-gde/install/cli/install-cli-install.md
@@ -238,7 +238,7 @@ bin/magento setup:install --base-url=http://127.0.0.1/magento2/ \
 --sales-order-increment-prefix="ORD$" --session-save=db --use-rewrites=1
 ```
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 You must enter the command either on a single line or, as in the preceding example, with a `\` character at the end of each line.
 
 Messages like the following display if the installation is successful:
diff --git a/src/guides/v2.3/javascript-dev-guide/javascript/custom_js.md b/src/guides/v2.3/javascript-dev-guide/javascript/custom_js.md
@@ -92,7 +92,7 @@ Where the following notation is used:
 -  `<your_namespace>.<your_widget_name>` - the name of your custom [widget](https://glossary.magento.com/widget). According to the jQuery widgets naming convention, this value must contain a [namespace](https://glossary.magento.com/namespace) and name.
 -  `mage.<widget.name>` - the name of the Magento widget that you extend.
 
-{:.bs-callout-note}
+{:.bs-callout-info}
 When using custom JS, try to keep dependencies to a minimum. Additional dependencies demand more web requests, which can slow rendering.
 
 {:.bs-callout-tip}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-install.md b/src/guides/v2.4/install-gde/install/cli/install-cli-install.md
@@ -269,7 +269,7 @@ magento setup:install --base-url=http://127.0.0.1/magento2/ \
 --elasticsearch-port=9200
 ```
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 You must enter the command either on a single line or, as in the preceding example, with a `\` character at the end of each line.
 
 Messages like the following display if the installation is successful:
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli.md b/src/guides/v2.4/install-gde/install/cli/install-cli.md
@@ -287,7 +287,7 @@ magento setup:install --base-url=http://127.0.0.1/magento2/ \
 --elasticsearch-port=9200
 ```
 
-{:.bs-callout .bs-callout-info}
+{:.bs-callout-info}
 You must enter the command either on a single line or, as in the preceding example, with a `\` character at the end of each line.
 
 Messages like the following display if the installation is successful:
diff --git a/src/guides/v2.4/migration/migration-manually.md b/src/guides/v2.4/migration/migration-manually.md
@@ -27,7 +27,7 @@ This section discusses how to manually migrate media files.
 
 ### Media files stored in the database
 
-{:.bs-class-warning}
+{:.bs-callout-warning}
 The database media storage method is deprecated as of Magento 2.4.3.4
 
 This section applies to you *only* if you store media files in the Magento database. This step should be performed before <a href="{{ page.baseurl }}/migration/migration-migrate-data.html">migration of data</a>:
diff --git a/src/marketplace/sellers/developer-register.md b/src/marketplace/sellers/developer-register.md
@@ -25,7 +25,7 @@ If you already have a Magento account, log in as a registered user.
 
 1. Under _Personal Information_, enter your **First Name**, **Last Name**, **Email Address**, and **Country**.
 
-    {: .bs-callout .bs-callout-info}
+    {: .bs-callout-info}
     If there is already a Magento account with this email address, click the link to access your account.
 
 1. Under _My Company Primarily_, choose the best description of your company’s primary focus. Then, set **My Role** to the option that best describes what you do for the company.
diff --git a/src/marketplace/sellers/extension-create.md b/src/marketplace/sellers/extension-create.md
@@ -14,7 +14,7 @@ Before you can submit your extension to Commerce Marketplace, the code must be c
 ![]({{ site.baseurl }}/marketplace/sellers/images/extension-prep.png){: .zoom}
 _Building and Submitting an Extension_
 
-{: .bs-callout .bs-callout-info}
+{: .bs-callout-info}
 Commerce Marketplace does not support encrypted extensions at this time.
 
 ## Build your extension
diff --git a/src/marketplace/sellers/extension-update-information.md b/src/marketplace/sellers/extension-update-information.md
@@ -20,5 +20,5 @@ You can then do one of the following:
 -  Update the extension price, support tier price, or installation price ONLY, and then submit. These changes will bypass marketing review and update the information in the store.
 -  Update any other field (or pricing and any other field) and submit. This will put the extension back into the queue for marketing review.
 
-{: .bs-callout .bs-callout-info}
+{: .bs-callout-info}
 You do NOT have to remove your product from the store in order to update its marketing information.
diff --git a/src/marketplace/sellers/profile-company.md b/src/marketplace/sellers/profile-company.md
@@ -81,7 +81,7 @@ _Social Networks_
 
 1. When prompted, enter your **PayPal Email** address.
 
-   {: .bs-callout .bs-callout-info}
+   {: .bs-callout-info}
    **Important:** This payment information is required of all developers, even those who make their extensions available at no charge. Magento sends your revenue share on a monthly basis to PayPal account.
 
 1. Watch for a confirmation email sent to the email address associated with the account.
diff --git a/src/marketplace/sellers/profile-information.md b/src/marketplace/sellers/profile-information.md
@@ -39,7 +39,7 @@ _Contact Information_
 
 Commerce Marketplace uses a pair of public and private 32-character tokens to authenticate access to the repository of third-party extensions and themes. You can create multiple sets of access keys for others who install extensions for your store. Marketplace access keys can be generated, disabled or enabled, and deleted from your account.
 
-{: .bs-callout .bs-callout-info}
+{: .bs-callout-info}
 The access key pair that is generated for Marketplace is not the same as the [Encryption Key][1]{: target="_blank"} that is associated with the Magento 2.x setup.
 
 For more technical information, see [Get your authentication keys][2] in the developer documentation.
diff --git a/src/marketplace/sellers/profile-personal.md b/src/marketplace/sellers/profile-personal.md
@@ -43,7 +43,7 @@ Prepare an image for your personal profile that is 255 pixels square, and saved
 
    `Name: <vendor-name> / <package-name>`
 
-   {: .bs-callout .bs-callout-info}
+   {: .bs-callout-info}
    This unique identifier is used to identify your Marketplace vendor account, and must exactly match the Vendor Name in your personal profile.
 
 ![Contact information]({{ site.baseurl }}/marketplace/sellers/images/account-company-profile-contact-info.png){: .zoom}
@@ -82,7 +82,7 @@ _Social Networks_
 
 1. When prompted, enter your **PayPal Email** address.
 
-   {: .bs-callout .bs-callout-info}
+   {: .bs-callout-info}
    **Important:** This payment information is required of all developers, even those who make their extensions available at no charge. Magento sends your revenue share on a monthly basis to PayPal account.
 
    Look for the confirmation email that is sent to the email address associated with the account. To activate your account and gain access to the Developer Portal, click the link in the email.
diff --git a/src/marketplace/sellers/submit-for-marketing-review.md b/src/marketplace/sellers/submit-for-marketing-review.md
@@ -156,7 +156,7 @@ Customers are advised to contact you directly for support, using the information
 
 ### Documentation and resources
 
-{: .bs-callout .bs-callout-info}
+{: .bs-callout-info}
 While you can add documentation PDF files during this review, the content is tested during the [Technical Review]({{ site.baseurl }}/marketplace/sellers/submit-for-technical-review.html).
 
 1. On the extension status page, on the left side, under **Marketing Submission**, click <span class="btn">Documentation and Resources</span>.
diff --git a/src/marketplace/sellers/submit-for-review.md b/src/marketplace/sellers/submit-for-review.md
@@ -5,7 +5,7 @@ title: Review Process
 
 After completing development, testing, and creating a new extension entry, you can submit your extension for [Technical]({{ site.baseurl }}/marketplace/sellers/submit-for-technical-review.html) and [Marketing]({{ site.baseurl }}/marketplace/sellers/submit-for-marketing-review.html) review. The extension enters a queue when submitted. We will review your extension code and submitted information according to the queue, sending feedback and confirmation by email. Track the status and progress of your extension submission through your Marketplace account. Our [Extension Quality Program]({{ site.baseurl }}/marketplace/sellers/extension-quality-program.html) (EQP) verifies that all Marketplace extensions meet Magento quality standards and best practices.
 
-{: .bs-callout .bs-callout-info}
+{: .bs-callout-info}
 Before submitting your extension for review, [complete the information]({{ site.baseurl }}/marketplace/sellers/extension-information.html) about the extension through the [developer portal]({{ site.baseurl }}/marketplace/sellers/developer-portal.html).
 
 The extension submission process requires you to do the following:
diff --git a/src/marketplace/sellers/submit-for-technical-review.md b/src/marketplace/sellers/submit-for-technical-review.md
@@ -11,7 +11,7 @@ When your [extension entry]({{ site.baseurl }}/marketplace/sellers/extension-inf
 
 The following instructions show how to submit an extension for Technical Review. The process is essentially the same for [themes]({{ site.baseurl }}/marketplace/sellers/themes.html) and [shared packages]({{ site.baseurl }}/marketplace/sellers/shared-packages.html).
 
-{: .bs-callout .bs-callout-info}
+{: .bs-callout-info}
 **Important - Shared Packages**: If your extension uses [Shared Packages]({{ site.baseurl }}/marketplace/sellers/shared-packages.html) (or components), the packages must be ready and associated with your submission. You will not be able to submit your extension to Technical Review until the shared packages are available in your account.
 
 ## Prepare for Technical Review
@@ -62,7 +62,7 @@ All products and services are subject to the same Commerce Marketplace terms and
 
 1. Add Documentation and Resources for your extension.
 
-    {: .bs-callout .bs-callout-info}
+    {: .bs-callout-info}
     Commerce Marketplace tests and reviews documentation during the Technical Review. You can add additional documentation during the [Marketing Review]({{ site.baseurl }}/marketplace/sellers/submit-for-marketing-review.html).
 
     You must include **at least one** of the following, in PDF format (less than 5MB):
@@ -78,7 +78,7 @@ All products and services are subject to the same Commerce Marketplace terms and
 
 1. If other components are used by an M2 extension, select the relevant **Shared Package**.
 
-    {: .bs-callout .bs-callout-info}
+    {: .bs-callout-info}
     **Important:** Before a shared package can be linked to an extension, it must be submitted for review and receive the status **Ready to Use**.
 
     ![]({{ site.baseurl }}/marketplace/sellers/images/technical-submission-shared.png){: .zoom}
diff --git a/src/tools/site-wide-analysis.md b/src/tools/site-wide-analysis.md
