Merge pull request magento-commerce/devdocs#2492 from magento-devdocs/DOC-483-rebrand

jeff-matthews · web-flow · commit fd910757d3b6 · 2021-08-30T13:17:48.000-05:00
Updated references to Magento extensions
diff --git a/src/extensions/index.md b/src/extensions/index.md
@@ -3,7 +3,7 @@ group: extensions
 title: Introduction
 ---
 
-Magento extensions allow you to add custom features, functionality, services, and integrations to your Admin and storefront. Extension developers package and install custom code as extensions, modules, components, addons, etc. You can design and develop extensions or purchase and install extensions from the Commerce Marketplace or third-party providers.
+Extensions allow you to add custom features, functionality, services, and integrations to your Admin and storefront. Extension developers package and install custom code as extensions, modules, components, addons, etc. You can design and develop extensions or purchase and install extensions from the Commerce Marketplace or third-party providers.
 
 The [Commerce Marketplace](https://marketplace.magento.com/) is the global eCommerce resource for applications and services that expand Magento solutions with powerful new features and functionality. Marketplace reviews and verifies all submitted extensions, modules, addons, and plugins are stable, supported, with clear documentation and release notes.
 
diff --git a/src/extensions/install/index.md b/src/extensions/install/index.md
@@ -16,7 +16,7 @@ redirect_from:
  - guides/v2.3/comp-mgr/extens-man/step3-parent.html
 ---
 
-Code that extends or customizes Magento behavior is called an extension. You can optionally package and distribute extensions on the [Commerce Marketplace](https://marketplace.magento.com) or another Magento extension distribution system.
+Code that extends or customizes {{site.data.var.ee}} and {{site.data.var.ce}} behavior is called an extension. You can optionally package and distribute extensions on the [Commerce Marketplace](https://marketplace.magento.com) or another extension distribution system.
 
 Extensions include:
 
diff --git a/src/guides/v2.3/coding-standards/code-standard-html.md b/src/guides/v2.3/coding-standards/code-standard-html.md
@@ -9,7 +9,7 @@ functional_areas:
   - Standards
 ---
 
-This style guide defines Magento internal requirements for [HTML](https://glossary.magento.com/html) code style for teams that develop Less and [CSS](https://glossary.magento.com/css) code. We recommend that developers who create Magento extensions and customizations also use these standards.
+This style guide defines Magento internal requirements for [HTML](https://glossary.magento.com/html) code style for teams that develop Less and [CSS](https://glossary.magento.com/css) code. We recommend that developers who create extensions and customizations also use these standards.
 
 The guide is based on the [Google HTML/CSS Style Guide](https://google.github.io/styleguide/htmlcssguide.xml) with certain modifications that are described further.
 
diff --git a/src/guides/v2.3/coding-standards/code-standard-php.md b/src/guides/v2.3/coding-standards/code-standard-php.md
@@ -9,7 +9,7 @@ functional_areas:
   - Standards
 ---
 
-The Magento core development team uses the [Magento Coding Standard](https://github.com/magento/magento-coding-standard){:target="_blank"}. We recommend that developers who create Magento extensions and customizations also use this standard.
+The Magento core development team uses the [Magento Coding Standard](https://github.com/magento/magento-coding-standard){:target="_blank"}. We recommend that developers who create extensions and customizations also use this standard.
 
 The Magento Coding Standard provides a set of rules that covers the following:
 
diff --git a/src/guides/v2.3/coding-standards/technical-guidelines.md b/src/guides/v2.3/coding-standards/technical-guidelines.md
@@ -939,7 +939,7 @@ class SampleEventObserverThatModifiesInputs implements ObserverInterface
 
 ## 17. Services
 
-17.1. New features with limited customization scenarios SHOULD be implemented as a thin Magento extension that will communicate to a service that contains business logic. This allows developers to release features independently of Magento and makes feature upgrades easier.
+17.1. New features with limited customization scenarios SHOULD be implemented as a thin extension that will communicate to a service that contains business logic. This allows developers to release features independently of Magento and makes feature upgrades easier.
 
 <!-- LINKS: DEFINITIONS AND ADDRESSES -->
 
diff --git a/src/guides/v2.3/ext-best-practices/bk-ext-best-practices.md b/src/guides/v2.3/ext-best-practices/bk-ext-best-practices.md
@@ -20,7 +20,7 @@ The table below is data from a recent poll that shows the distribution of the am
 | Community | 10% | 53%   | 26%   | 11% |
 | Enterprise| 9%  | 32%   | 27%   | 32% |
 
-This guide provides best practices, guidelines, and tips for creating Magento extensions.  We encourage you to follow our best practices when developing code for your Magento components.
+This guide provides best practices, guidelines, and tips for creating extensions.  We encourage you to follow our best practices when developing code for your Magento components.
 
 ### Related Content
 
diff --git a/src/guides/v2.3/extension-dev-guide/build/composer-integration.md b/src/guides/v2.3/extension-dev-guide/build/composer-integration.md
@@ -152,7 +152,7 @@ For language packages, you must use the correct [ISO code][4]{:target="_blank"}
 
 ## Magento-specific package types
 
-Magento extensions can be any of the following types:
+Extensions can be any of the following types:
 
 *  `magento2-module` for modules
 *  `magento2-theme` for themes
@@ -195,7 +195,7 @@ The convention for Magento package names is the following
 
 Where:
 
-:`type-prefix` is any of the Magento extension types:
+:`type-prefix` is any of the extension types:
 
 *  `module-` for module extensions
 *  `theme-` for theme extensions
diff --git a/src/guides/v2.3/migration/extend-the-tool.md b/src/guides/v2.3/migration/extend-the-tool.md
@@ -5,7 +5,7 @@ functional_areas:
   - Tools
 ---
 
-Sometimes the data format and structure created by [Magento extensions](https://marketplace.magento.com/extensions.html){:target="_blank"} or custom code is different between Magento 1 and Magento 2. Use extension points within the Data Migration Tool to migrate this data. If the data format and structure are the same, the tool can automatically migrate the data without user intervention.
+Sometimes the data format and structure created by [extensions](https://marketplace.magento.com/extensions.html){:target="_blank"} or custom code is different between Magento 1 and Magento 2. Use extension points within the Data Migration Tool to migrate this data. If the data format and structure are the same, the tool can automatically migrate the data without user intervention.
 
 During migration, the [Map Step]({{ page.baseurl }}/migration/migration-tool-internal-spec.html#map-step) scans and compares all Magento 1 and Magento 2 tables, including those created by extensions. If the tables are the same, the tool automatically migrates the data. If the tables differ, the tool terminates and notifies the user.
 
diff --git a/src/guides/v2.3/release-notes/release-notes-2-3-3-commerce.md b/src/guides/v2.3/release-notes/release-notes-2-3-3-commerce.md
@@ -207,7 +207,7 @@ The [Yotpo](https://www.yotpo.com) user-generated content management platform is
 
 ## Backward-incompatible Changes
 
-This release introduces a new, immutable `EmailMessageInterface` that supports the sending of multi-part MIME-type content in email. The  `Magento\Framework\Mail\Template\TransportBuilder` and `Magento\Newsletter\Model\Queue\TransportBuilder` structures were refactored to use this new `EmailMessageInterface` instead of `MessageInterface`, which was previously used. If you are a Magento extension developer and rely on `\Magento\Email\Model\Transport::getMessage()` or `\Magento\Framework\Mail\TransportInterface::getMessage()`, those methods will now return the new `EmailMessageInterface`.
+This release introduces a new, immutable `EmailMessageInterface` that supports the sending of multi-part MIME-type content in email. The  `Magento\Framework\Mail\Template\TransportBuilder` and `Magento\Newsletter\Model\Queue\TransportBuilder` structures were refactored to use this new `EmailMessageInterface` instead of `MessageInterface`, which was previously used. If you are an extension developer and rely on `\Magento\Email\Model\Transport::getMessage()` or `\Magento\Framework\Mail\TransportInterface::getMessage()`, those methods will now return the new `EmailMessageInterface`.
 
 ## Fixed issues
 
diff --git a/src/guides/v2.3/release-notes/release-notes-2-3-3-open-source.md b/src/guides/v2.3/release-notes/release-notes-2-3-3-open-source.md
@@ -193,7 +193,7 @@ The [Yotpo](https://www.yotpo.com) user-generated content management platform is
 
 ## Backward-incompatible Changes
 
-This release introduces a new, immutable `EmailMessageInterface` that supports the sending of multi-part MIME-type content in email. The  `Magento\Framework\Mail\Template\TransportBuilder` and `Magento\Newsletter\Model\Queue\TransportBuilder` structures were refactored to use this new `EmailMessageInterface` instead of `MessageInterface`, which was previously used. If you are a Magento extension developer and rely on `\Magento\Email\Model\Transport::getMessage()` or `\Magento\Framework\Mail\TransportInterface::getMessage()`, those methods will now return the new `EmailMessageInterface`.
+This release introduces a new, immutable `EmailMessageInterface` that supports the sending of multi-part MIME-type content in email. The  `Magento\Framework\Mail\Template\TransportBuilder` and `Magento\Newsletter\Model\Queue\TransportBuilder` structures were refactored to use this new `EmailMessageInterface` instead of `MessageInterface`, which was previously used. If you are an extension developer and rely on `\Magento\Email\Model\Transport::getMessage()` or `\Magento\Framework\Mail\TransportInterface::getMessage()`, those methods will now return the new `EmailMessageInterface`.
 
 ## Fixed issues
 
diff --git a/src/guides/v2.3/test/integration/integration_test_execution.md b/src/guides/v2.3/test/integration/integration_test_execution.md
@@ -171,7 +171,7 @@ For core tests, it makes sense that the integration tests do not reside within i
 
 Specific integration tests for shop implementation could also be placed within a different subdirectory of `dev/tests/integration/testsuite`, and then would be executed together with the core tests.
 
-However, third-party Magento extensions are contained within a single directory and might supply custom integration tests too.
+However, third-party extensions are contained within a single directory and might supply custom integration tests too.
 These tests usually reside in the `Test/Integration/` subdirectory within the [module](https://glossary.magento.com/module) folder.
 
 These third-party integration tests are not picked up by the default integration test configuration.
diff --git a/src/guides/v2.4/test/integration/integration_test_execution.md b/src/guides/v2.4/test/integration/integration_test_execution.md
@@ -198,7 +198,7 @@ For core tests, it makes sense that the integration tests do not reside within i
 
 Specific integration tests for shop implementation could also be placed within a different subdirectory of `dev/tests/integration/testsuite`, and then would be executed together with the core tests.
 
-However, third-party Magento extensions are contained within a single directory and might supply custom integration tests too.
+However, third-party extensions are contained within a single directory and might supply custom integration tests too.
 These tests usually reside in the `Test/Integration/` subdirectory within the [module](https://glossary.magento.com/module) folder.
 
 These third-party integration tests are not picked up by the default integration test configuration.
diff --git a/src/marketplace/sellers/getting-started.md b/src/marketplace/sellers/getting-started.md
@@ -14,6 +14,6 @@ This next generation application store offers merchants a curated selection of s
 [![]({{ site.baseurl }}/marketplace/sellers/images/assets/code-review.png)]({{ site.baseurl }}/marketplace/sellers/extension-quality-program.html)|[**Submit for Review**]({{ site.baseurl }}/marketplace/sellers/extension-quality-program.html) - Our Extension Quality Program (EQP) verifies that all Marketplace extensions meet Magento quality standards and best practices.|
 [![]({{ site.baseurl }}/marketplace/sellers/images/assets/sales-data.png)]({{ site.baseurl }}/marketplace/sellers/sales.html)|[**Manage Your Sales**]({{ site.baseurl }}/marketplace/sellers/sales.html) - You can use the Sales and Analytics reports to view and manage your extension sales information.|
 [![]({{ site.baseurl }}/marketplace/sellers/images/assets/purchase.png)][1]|[**For Buyers**](https://docs.magento.com/m2/ee/user_guide/magento/magento-marketplace.html) - Take a look at the extension installation process from the standpoint of a customer.|
-[![]({{ site.baseurl }}/marketplace/sellers/images/assets/tools.png)]({{ site.baseurl }}/marketplace/sellers/technical-reference.html)|[**Technical Reference**]({{ site.baseurl }}/marketplace/sellers/technical-reference.html) - There are a number of resources available to Magento extension developers and buyers.|
+[![]({{ site.baseurl }}/marketplace/sellers/images/assets/tools.png)]({{ site.baseurl }}/marketplace/sellers/technical-reference.html)|[**Technical Reference**]({{ site.baseurl }}/marketplace/sellers/technical-reference.html) - There are a number of resources available to extension developers and buyers.|
 
 [1]: https://docs.magento.com/m2/ee/user_guide/magento/magento-marketplace.html
diff --git a/src/marketplace/sellers/semantic-version-check.md b/src/marketplace/sellers/semantic-version-check.md
@@ -11,7 +11,7 @@ The Semantic Version Check (SVC) is a quality check that validates the change le
 
 [Semantic Versioning](https://semver.org/) is a good way to communicate what kind of changes were introduced between software releases. Clients can use this information to estimate the risk level of upgrading a particular software package and to determine how much effort is required to adopt the new version.
 
-Magento follows Semantic Versioning and encourages all third-party vendors to apply this versioning strategy for their Magento extensions as well.
+Magento follows Semantic Versioning and encourages all third-party vendors to apply this versioning strategy for their extensions as well.
 
 Commerce Marketplace uses version information to fast-track the extension validation process for submissions that introduce patch level changes, as these are expected to be backwards compatible bug fixes without any new functionality.
 
diff --git a/src/marketplace/sellers/technical-review-guidelines.md b/src/marketplace/sellers/technical-review-guidelines.md
@@ -10,7 +10,7 @@ During technical review, your code is examined to detect the presence of viruses
 The technical review begins as soon as you upload an extension package at [Developer Portal](https://developer.magento.com/) and consists of two mandatory steps to generate the submission id and trigger further extension testing:
 
 1. [Malware Scan]({{ site.baseurl }}/marketplace/sellers/malware-scan.html) &mdash; Ensures that uploaded packages do not contain viruses or malware software.
-1. Extension Package Verification &mdash; Checks that the uploaded file is a zip archive which is a [Composer](https://getcomposer.org/) package with Magento extension.
+1. Extension Package Verification &mdash; Checks that the uploaded file is a zip archive which is a [Composer](https://getcomposer.org/) package with extension.
 
 ### Extension Package Verification
 
diff --git a/src/release/availability.md b/src/release/availability.md
@@ -17,6 +17,6 @@ The following table describes the status of Magento software availability and wh
 
 Magento modules that have been built to be decoupled from the {{site.data.var.ee}} core release process; this allows us to release iterations of these modules faster to merchants who are willing to accept a little risk in exchange for earlier access to new features.
 
-The following table shows the release status of Magento extension versions relative to {{site.data.var.ee}}.
+The following table shows the release status of extension versions relative to {{site.data.var.ee}}.
 
 {% include compatibility-mde.html data=site.data.mde %}
