Merge pull request #2759 from magento-commerce/1-28_integration

1 28 integration

Author: dobooth

src/cloud/project/ece-tools-upgrade-project.md

@@ -71,14 +71,14 @@ To upgrade project to use ece-tools:
        # We run build hooks before your application has been packaged.
        build: |
            set -e
-           php ./vendor/bin/ece-tools build:generate
-           php ./vendor/bin/ece-tools build:transfer
+           php ./vendor/bin/ece-tools run scenario/build/generate.xml
+           php ./vendor/bin/ece-tools run scenario/build/transfer.xml
        # We run deploy hook after your application has been deployed and started.
        deploy: |
-           php ./vendor/bin/ece-tools deploy
+           php ./vendor/bin/ece-tools run scenario/deploy.xml
        # We run post deploy hook to clean and warm the cache. Available with ECE-Tools 2002.0.10.
        post_deploy: |
-           php ./vendor/bin/ece-tools post-deploy
+           php ./vendor/bin/ece-tools run scenario/post-deploy.xml
    ```
 
 1. Check for and remove the [deprecated packages](#remove-deprecated-packages). The deprecated packages can prevent a successful upgrade.

src/cloud/project/project-upgrade.md

@@ -64,14 +64,14 @@ To update the `.magento.app.yaml` file:
        # We run build hooks before your application has been packaged.
        build: |
            set -e
-           php ./vendor/bin/ece-tools build:generate
-           php ./vendor/bin/ece-tools build:transfer
+           php ./vendor/bin/ece-tools run scenario/build/generate.xml
+           php ./vendor/bin/ece-tools run scenario/build/transfer.xml
        # We run deploy hook after your application has been deployed and started.
        deploy: |
-           php ./vendor/bin/ece-tools deploy
+           php ./vendor/bin/ece-tools run scenario/deploy.xml
        # We run post deploy hook to clean and warm the cache. Available with ECE-Tools 2002.0.10.
        post_deploy: |
-           php ./vendor/bin/ece-tools post-deploy
+           php ./vendor/bin/ece-tools run scenario/post-deploy.xml
    ```
 
 1. Add the following environment variables to the end of the `magento.app.yaml` file.

src/guides/v2.3/extension-dev-guide/build/di-xml-file.md

@@ -263,20 +263,20 @@ The `preference` node specifies the default implementation:
 ```xml
 <!--  File: app/etc/di.xml -->
 <config>
-    <preference for="Magento\Core\Model\UrlInterface" type="Magento\Core\Model\Url" />
+    <preference for="Magento\Framework\UrlInterface" type="Magento\Framework\Url" />
 </config>
 ```
 
-This mapping is in `app/etc/di.xml`, so the object manager injects the `Magento\Core\Model\Url` implementation class wherever there is a request for the `Magento\Core\Model\UrlInterface` in the global scope.
+This mapping is in `app/etc/di.xml`, so the object manager injects the `Magento\Framework\Url` implementation class wherever there is a request for the `Magento\Framework\UrlInterface` in the global scope.
 
 ```xml
 <!-- File: app/code/Magento/Backend/etc/adminhtml/di.xml -->
 <config>
-    <preference for="Magento\Core\Model\UrlInterface" type="Magento\Backend\Model\Url" />
+    <preference for="Magento\Framework\UrlInterface" type="Magento\Backend\Model\UrlInterface" />
 </config>
 ```
 
-This mapping is in `app/code/Magento/Backend/etc/adminhtml/di.xml`, so the object manager injects the `Magento\Backend\Model\Url` implementation class wherever there is a request for the `Magento\Core\Model\UrlInterface` in the [admin](https://glossary.magento.com/admin) area.
+This mapping is in `app/code/Magento/Backend/etc/adminhtml/di.xml`, so the object manager injects the `Magento\Backend\Model\UrlInterface` implementation class wherever there is a request for the `Magento\Framework\UrlInterface` in the [admin](https://glossary.magento.com/admin) area.
 
 ### Override a method using 'preference' nodes
 
@@ -363,7 +363,7 @@ Any descendant can override the parameters configured for its supertype; that is
 <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">
     <type name="Magento\Framework\View\Element\Context">
         <arguments>
-            <argument name="urlBuilder" xsi:type="object">Magento\Core\Model\Url</argument>
+            <argument name="urlBuilder" xsi:type="object">Magento\Framework\Url</argument>
         </arguments>
     </type>
     <type name="Magento\Backend\Block\Context">
@@ -376,7 +376,7 @@ Any descendant can override the parameters configured for its supertype; that is
 
 In the preceding example, [`Magento\Backend\Block\Context`]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Backend/Block/Context.php) is a descendant of [`Magento\Framework\View\Element\Context`]({{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/View/Element/Context.php).
 
-The first entry configures all instances of `Magento\Framework\View\Element\Context` as well as its children to pass in [`Magento\Core\Model\Url`]({{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/Url.php) as `$urlBuilder` in their constructors.
+The first entry configures all instances of `Magento\Framework\View\Element\Context` as well as its children to pass in [`Magento\Framework\Url`]({{ site.mage2bloburl }}/{{ page.guide_version }}/lib/internal/Magento/Framework/Url.php) as `$urlBuilder` in their constructors.
 
 The second entry overrides this and configures all instances of `Magento\Backend\Block\Context` to use [`Magento\Backend\Model\Url`]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Backend/Model/Url.php) as the `$urlBuilder` instead.
 

src/guides/v2.3/extension-dev-guide/build/module-load-order.md

@@ -16,7 +16,7 @@ If you know that your component's logic depends on something in another componen
 You can check your module's load order from the `<magento_root>/app/etc/config.php` file after you've successfully set up Magento. This file is created dynamically at run time during set up.
 
  {:.bs-callout-info}
-If you change the component load order using `<sequence>`, you must regenerate the component list in `config.php`; otherwise, the load order does not take effect. Currently, the only way to do this is to enable the component using [`magento module:enable`]({{ page.baseurl}}/install-gde/install/cli/install-cli-subcommands-enable.html#instgde-cli-subcommands-enable-disable), where `<module-list>` is the component or components to which you added `<sequence>`.
+If you change the component load order using `<sequence>`, you must regenerate the component list in `config.php`; otherwise, the load order does not take effect. Currently, the only way to do this is to enable the component using [`magento module:enable <module-list>`]({{ page.baseurl}}/install-gde/install/cli/install-cli-subcommands-enable.html#instgde-cli-subcommands-enable-disable), where `<module-list>` is the component or components to which you added `<sequence>`.
 
 ### Examples
 

src/guides/v2.3/extension-dev-guide/depend-inj.md

@@ -85,7 +85,7 @@ class Builder
 
 ### Constructor injection
 
-In the code sample, the `Builder` class declares its dependency on the `Factory` and `Menu` classes in its constructor.
+In the code sample, the `Builder` class declares its dependency on the `Factory` class in its constructor.
 Magento uses the `di.xml` file to determine which implementations to inject into the `Builder` class.
 
 #### Optional dependencies