Update package name for require command

Author: keharper

src/guides/v2.4/comp-mgr/cli/cli-upgrade.md

@@ -18,13 +18,13 @@ You can upgrade your Magento application from the command line if you installed
 {:.bs-callout-info}
 Do not use this method to upgrade if you cloned the Magento 2 GitHub repository. Instead, see [Update Magento][] for upgrade instructions.
 
-The following instructions show you how to upgrade Magento using Composer. Magento 2.4.2 introduced support for Composer 2. If you are attempting to upgrade from Magento <2.4.1, you must first upgrade to a version of Magento that is compatible with Composer 2 (for example, 2.4.2) using Composer 1 _before_ upgrading to Composer 2 for Magento >2.4.2 upgrades.
+The following instructions show you how to upgrade Magento using Composer. Magento 2.4.2 introduced support for Composer 2. If you are attempting to upgrade from Magento <2.4.1, you must first upgrade to a version of Magento that is compatible with Composer 2 (for example, 2.4.2) using Composer 1 _before_ upgrading to Composer 2 for Magento >2.4.2 upgrades. In addition, you must be running a [supported version]({{page.baseurl}}/install-gde/system-requirements.html) of PHP.
 
 ## Before you begin {#prerequisites}
 
 Complete the following prerequisites to prepare your environment before starting the upgrade process:
 
--  **Determine whether your current catalog search engine is supported**-Avoid significant upgrade errors by ensuring your search engine complies with 2.3 requirements. See [Check the catalog search engine] for more details.
+-  **Determine whether your current catalog search engine is supported**-Avoid significant upgrade errors by ensuring your search engine complies with 2.4 requirements. See [Check the catalog search engine] for more details.
 -  **Complete the Update and upgrade checklist**—To avoid possible errors during installation or upgrading, complete the [Update and upgrade checklist].
 -  **Set the `pub/` directory root**—See [Modify docroot to improve security][] for more details.
 -  **Check PHP and environment settings**—Verify that your PHP and other environment settings are compatible with the [system requirements].
@@ -46,7 +46,7 @@ Complete the following prerequisites to prepare your environment before starting
    To install the plugin:
 
    ```bash
-   composer require magento/composer-root-update-plugin=~1.0 --no-update
+   composer require magento/composer-root-update-plugin=~2.0 --no-update
    ```
 
    Update the dependencies:
@@ -76,24 +76,24 @@ See the examples at the end of this section for help specifying different releas
 
    {:.bs-callout-info}
    The first time you upgrade using the plugin, you can interactively view and update any out-of-date values that may be remaining from previous versions.
-   To enable this, use the `--interactive-magento-conflicts` option on the `composer require` commands.
+   To enable this, use the `--interactive-root-conflicts` option on the `composer require-commerce` commands.
 
-   To override all conflicting custom values with the expected Magento values, re-run the `composer require` command with the `--use-default-magento-values` option.
+   To override all conflicting custom values with the expected Magento values, re-run the `composer require-commerce` command with the `--use-default-project-values` option.
 
    {:.bs-callout-tip}
-   Use `composer require --help` to learn more about available options.
+   Use `composer require-commerce --help` to learn more about available options.
    To learn more about usage of the plugin, refer to the [Plugin Usage](https://github.com/magento/composer-root-update-plugin/blob/0.1/src/Magento/ComposerRootUpdatePlugin/README.md#usage).
 
    _{{ ce }}_:
 
    ```bash
-   composer require magento/product-community-edition={{ page.guide_version }}.0 --no-update
+   composer require-commerce magento/product-community-edition={{ page.guide_version }}.0 --no-update
    ```
 
    _{{ ee }}_:
 
    ```bash
-   composer require magento/product-enterprise-edition={{ page.guide_version }}.0 --no-update
+   composer require-commerce magento/product-enterprise-edition={{ page.guide_version }}.0 --no-update
    ```
 
    <div class="bs-callout-tip" markdown="1">
@@ -115,28 +115,28 @@ See the examples at the end of this section for help specifying different releas
 
 ### Example - Minor release
 
-Minor releases contain new features, quality fixes, and security fixes. Use Composer to specify a minor release. For example, to specify the {{site.data.var.ee}} 2.3.7 metapackage:
+Minor releases contain new features, quality fixes, and security fixes. Use Composer to specify a minor release. For example, to specify the {{site.data.var.ee}} 2.4.3 metapackage:
 
 ```bash
-composer require magento/product-community-edition=2.3.7 --no-update
+composer require-commerce magento/product-community-edition=2.4.3 --no-update
 ```
 
 ### Example - Quality patch
 
-Quality patches primarily contain functional _and_ security fixes. However, they can also sometimes contain new, backward-compatible features. Use Composer to download a quality patch. For example, to specify the {{site.data.var.ee}} 2.3.7 metapackage:
+Quality patches primarily contain functional _and_ security fixes. However, they can also sometimes contain new, backward-compatible features. Use Composer to download a quality patch. For example, to specify the {{site.data.var.ee}} 2.4.1 metapackage:
 
 ```bash
-composer require magento/product-community-edition=2.3.7 --no-update
+composer require-commerce magento/product-community-edition=2.4.1 --no-update
 ```
 
 ### Example - Security patch
 
 Security patches contain security fixes only. They are designed to make the upgrade process faster and easier.
 
-Security patches use the Composer naming convention `2.3.6-px`. Use Composer to specify a patch. For example, to download the {{site.data.var.ce}} 2.3.6-p1 metapackage:
+Security patches use the Composer naming convention `2.4.3-px`. Use Composer to specify a patch. For example, to download the {{site.data.var.ce}} 2.4.3-p1 metapackage:
 
 ```bash
-composer require magento/product-community-edition=2.3.6-p1 --no-update
+composer require-commerce magento/product-community-edition=2.4.3-p1 --no-update
 ```
 
 ## Update metadata