Merge pull request #128 from commerce-docs/gendocs_2.4.6

Updated Module Reference Guide data for the 2.4.6 release

Author: dshevtsov

src/data/navigation/sections/module_reference.js

@@ -739,11 +739,6 @@ module.exports = [
       path: "/module-reference/module-elasticsearch-7/"
     },
 
-    {
-      title: "Elasticsearch8",
-      path: "/module-reference/module-elasticsearch-8/"
-    },
-    
     {
       title: "ElasticsearchCatalogPermissions",
       path: "/module-reference/module-elasticsearch-catalog-permissions/"
@@ -1784,6 +1779,16 @@ module.exports = [
       path: "/module-reference/module-purchase-order-rule-graph-ql/"
     },
 
+    {
+      title: "QuickCheckout",
+      path: "/module-reference/module-quick-checkout/"
+    },
+    
+    {
+      title: "QuickCheckoutAdminPanel",
+      path: "/module-reference/module-quick-checkout-admin-panel/"
+    },
+    
     {
       title: "QuickOrder",
       path: "/module-reference/module-quick-order/"

src/pages/module-reference/module-admin-adobe-ims.md

@@ -244,7 +244,7 @@ By clicking on this button a popup opens with the AdobeIms Login, where the curr
 After successfully validate his identity, we are redirecting to the `Magento/AdminAdobeIms/Controller/Adminhtml/OAuth/ImsReauthCallback.php` Controller and update the `ims_verified` field.
 
 When the form will be submitted, we verify the identity with the `Magento/AdminAdobeIms/Plugin/ReplaceVerifyIdentityWithImsPlugin.php` Plugin.
-Here the existence of the `AdobeAccessToken` and `AdobeReAuthToken` will be checked.
+Here the existens of the `AdobeAccessToken` and `AdobeReAuthToken` will be checked.
 The reauth_token will be used to call the AdobeIms validateToken Endpoint.
 
 When this call is successful, the form will be submitted, otherwise we update the Message of the thrown `AuthenticationException` to return a matching error message, done by the `Magento/AdminAdobeIms/Plugin/PerformIdentityCheckMessagePlugin.php` Plugin.

src/pages/module-reference/module-adobe-io-events-client.md

@@ -25,9 +25,9 @@ This is a two-step process:
     - Enter a unique ID  in the `Adobe Commerce Instance ID` field
 4. Run the following command to create an event provider
 
-   ```bash
-   bin/magento events:create-event-provider --label "<unique_provider_label>" --description "<provider description>"
-   ```
+```bash
+bin/magento events:create-event-provider --label "<unique_provider_label>" --description "<provider description>"
+````
 
 5. Enter the Event Provider ID output by the command in the `Adobe I/O Event Provider ID` field
 

src/pages/module-reference/module-catalog.md

@@ -23,59 +23,57 @@ Catalog module provides API filtering that allows to limit product selection wit
 This module observes the following events:
 
 - `etc/events.xml`
-  - `magento_catalog_api_data_productinterface_save_before` event in
+    - `magento_catalog_api_data_productinterface_save_before` event in
     `Magento\Framework\EntityManager\Observer\BeforeEntitySave` file.
-  - `magento_catalog_api_data_productinterface_save_after` event in
-     `Magento\Framework\EntityManager\Observer\AfterEntitySave` file.
-  - `magento_catalog_api_data_productinterface_delete_before` event in
+    - `magento_catalog_api_data_productinterface_save_after` event in
+    `Magento\Framework\EntityManager\Observer\AfterEntitySave` file.
+    - `magento_catalog_api_data_productinterface_delete_before` event in
     `Magento\Framework\EntityManager\Observer\BeforeEntityDelete` file.
-  - `magento_catalog_api_data_productinterface_delete_after` event in
+    - `magento_catalog_api_data_productinterface_delete_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntityDelete` file.
-  - `magento_catalog_api_data_productinterface_load_after` event in
+    - `magento_catalog_api_data_productinterface_load_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntityLoad` file.
-  - `magento_catalog_api_data_categoryinterface_save_before` event in
+    - `magento_catalog_api_data_categoryinterface_save_before` event in
     `Magento\Framework\EntityManager\Observer\BeforeEntitySave` file.
-  - `magento_catalog_api_data_categoryinterface_save_after` event in
+    - `magento_catalog_api_data_categoryinterface_save_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntitySave` file.
-  - `magento_catalog_api_data_categoryinterface_save_after` event in
+    - `magento_catalog_api_data_categoryinterface_save_after` event in
     `Magento\Catalog\Observer\InvalidateCacheOnCategoryDesignChange` file.
-  - `magento_catalog_api_data_categoryinterface_delete_before` event in
+    - `magento_catalog_api_data_categoryinterface_delete_before` event in
     `Magento\Framework\EntityManager\Observer\BeforeEntityDelete` file.
-  - `magento_catalog_api_data_categoryinterface_delete_after` event in
+    - `magento_catalog_api_data_categoryinterface_delete_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntityDelete` file.
-  - `magento_catalog_api_data_categoryinterface_load_after` event in
+    - `magento_catalog_api_data_categoryinterface_load_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntityLoad` file.
-  - `magento_catalog_api_data_categorytreeinterface_save_before` event in
+    - `magento_catalog_api_data_categorytreeinterface_save_before` event in
     `Magento\Framework\EntityManager\Observer\BeforeEntitySave` file.
-  - `magento_catalog_api_data_categorytreeinterface_save_after` event in
+    - `magento_catalog_api_data_categorytreeinterface_save_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntitySave` file.
-  - `magento_catalog_api_data_categorytreeinterface_delete_before` event in
+    - `magento_catalog_api_data_categorytreeinterface_delete_before` event in
     `Magento\Framework\EntityManager\Observer\BeforeEntityDelete` file.
-  - `magento_catalog_api_data_categorytreeinterface_delete_after` event in
+    - `magento_catalog_api_data_categorytreeinterface_delete_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntityDelete` file.
-  - `magento_catalog_api_data_categorytreeinterface_load_after` event in
+    - `magento_catalog_api_data_categorytreeinterface_load_after` event in
     `Magento\Framework\EntityManager\Observer\AfterEntityLoad` file.
-  - `admin_system_config_changed_section_catalog` event in
+    - `admin_system_config_changed_section_catalog` event in
     `Magento\Catalog\Observer\SwitchPriceAttributeScopeOnConfigChange` file.
-  - `catalog_product_save_before` event in
+    - `catalog_product_save_before` event in
     `Magento\Catalog\Observer\SetSpecialPriceStartDate` file.
-  - `store_save_after` event in
+    - `store_save_after` event in
     `Magento\Catalog\Observer\SynchronizeWebsiteAttributesOnStoreChange` file.
-  - `catalog_product_save_commit_after` event in
+    - `catalog_product_save_commit_after` event in
     `Magento\Catalog\Observer\ImageResizeAfterProductSave` file.
-  - `catalog_category_prepare_save` event in
+    - `catalog_category_prepare_save` event in
     `Magento\Catalog\Observer\CategoryDesignAuthorization` file.
-
 - `/etc/frontend/events.xml`
-  - `customer_login` event in
+    - `customer_login` event in
     `Magento\Catalog\Observer\Compare\BindCustomerLoginObserver` file.
-  - `customer_logout` event in
+    - `customer_logout` event in
     `Magento\Catalog\Observer\Compare\BindCustomerLogoutObserver` file.
-
 - `/etc/adminhtml/events.xml`
-  - `cms_wysiwyg_images_static_urls_allowed` event in
+    - `cms_wysiwyg_images_static_urls_allowed` event in
     `Magento\Catalog\Observer\CatalogCheckIsUsingStaticUrlsAllowedObserver` file.
-  - `catalog_category_change_products` event in
+    - `catalog_category_change_products` event in
     `Magento\Catalog\Observer\CategoryProductIndexer` file.
-  - `category_move` event in
+    - `category_move` event in
     `Magento\Catalog\Observer\FlushCategoryPagesCache`

src/pages/module-reference/module-elasticsearch-8.md

@@ -43,26 +43,26 @@ For information about a typical file structure of a module in Magento 2,
 
 ## Extensibility
 
-Developers can pass custom `msrpPriceCalculators` for `Magento\Msrp\Pricing\MsrpPriceCalculator` using type configuration using  `di.xml`.
-
-For example:
-
-```xml
-    <type name="Magento\Msrp\Pricing\MsrpPriceCalculator">
-        <arguments>
-            <argument name="msrpPriceCalculators" xsi:type="array">
-                <item name="configurable" xsi:type="array">
-                    <item name="productType" xsi:type="const">Magento\ConfigurableProduct\Model\Product\Type\Configurable::TYPE_CODE</item>
-                    <item name="priceCalculator" xsi:type="object">Magento\MsrpConfigurableProduct\Pricing\MsrpPriceCalculator</item>
-                </item>
-            </argument>
-       </arguments>
-   </type>
+ Developers can pass custom `msrpPriceCalculators` for `Magento\Msrp\Pricing\MsrpPriceCalculator` using type configuration using  `di.xml`.
+
+ For example:
+
+ ```xml
+<type name="Magento\Msrp\Pricing\MsrpPriceCalculator">
+    <arguments>
+        <argument name="msrpPriceCalculators" xsi:type="array">
+            <item name="configurable" xsi:type="array">
+                <item name="productType" xsi:type="const">Magento\ConfigurableProduct\Model\Product\Type\Configurable::TYPE_CODE</item>
+                <item name="priceCalculator" xsi:type="object">Magento\MsrpConfigurableProduct\Pricing\MsrpPriceCalculator</item>
+            </item>
+        </argument>
+    </arguments>
+</type>
 ```
 
-More information about [type configuration](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/di-xml-file.html).
+ More information about [type configuration](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/di-xml-file.html).
 
-Extension developers can interact with the Magento_Msrp module. For more information about the Magento extension mechanism, see [Magento plug-ins](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/plugins.html).
+ Extension developers can interact with the Magento_Msrp module. For more information about the Magento extension mechanism, see [Magento plug-ins](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/plugins.html).
 
 [The Magento dependency injection mechanism](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/depend-inj.html) enables you to override the functionality of the Magento_Msrp module.
 
@@ -119,7 +119,7 @@ This module introduces the following layouts and layout handles:
 
 Module provides product admin form modifier:
 
-`Magento\Msrp\Ui\DataProvider\Product\Form\Modifier\Msrp` - removes `msrp_display_actual_price_type` field from the form if config disabled else adds `validate-zero-or-greater` validation to the field.
+`Magento\Msrp\Ui\DataProvider\Product\Form\Modifier\Msrp` - removes `msrp_display_actual_price_type` field from the form if config disabled else adds `validate-zero-or-greater` validation to the fild.
 
 ## Additional information
 

src/pages/module-reference/module-msrp.md

@@ -22,7 +22,7 @@ For information about a typical file structure of a module in Magento 2,
 Developers can interact with the module and change behaviour using type configuration feature.
 
 Namely, we can change `paymentSpecification` for `Magento\Multishipping\Block\Checkout\Billing` and `Magento\Multishipping\Model\Checkout\Type\Multishipping` classes.
-As result, we will get changed behaviour, new logic or something what our business need.
+As result, we will get changed behavior, new logic or something what our business need.
 
 For example:
 
@@ -141,4 +141,4 @@ Module introduces the new pages:
 
 More information about [layout types](https://devdocs.magento.com/guides/v2.4/frontend-dev-guide/layouts/layout-types.html).
 
-For information about significant changes in patch releases, see [2.3.x Release information](http://devdocs.magento.com/guides/v2.3/release-notes/bk-release-notes.html).
+For information about significant changes in patch releases, see [Release information](https://experienceleague.adobe.com/docs/commerce-operations/release/notes/overview.html).

src/pages/module-reference/module-multishipping.md

@@ -23,7 +23,7 @@ For information about a module installation in Magento 2, see [Enable or disable
 
 ## Additional information
 
-For information about significant changes in patch releases, see [2.3.x Release information](http://devdocs.magento.com/guides/v2.3/release-notes/bk-release-notes.html).
+For information about significant changes in patch releases, see [Release information](https://experienceleague.adobe.com/docs/commerce-operations/release/notes/overview.html).
 
 ### cron options
 

src/pages/module-reference/module-mysql-mq.md

@@ -5,10 +5,14 @@ description: README.md contents of the module from the source code
 
 # Magento_PurchaseOrderRuleGraphQl
 
+​
+
 ## Overview
 
+​
 The PurchaseOrderRuleGraphQl module provides GraphQl API coverage for PurchaseOrderRule module functionality.
 
 ## Additional information
 
+​
 Check the [B2B release notes](https://devdocs.magento.com/guides/v2.4/release-notes/b2b-release-notes.html) for more information on new changes.

src/pages/module-reference/module-purchase-order-rule-graph-ql.md

@@ -5,19 +5,26 @@ description: README.md contents of the module from the source code
 
 # Magento_PurchaseOrderRule
 
+​
+
 ## Overview
 
+​
 The PurchaseOrderRule module contains functionality for creating and enforcing approval rules for purchase orders. Companies in a B2B environment can use these rules to enforce purchasing guidelines and limits.
 ​
 With this module installed, you may create rules such as:
+​
 
 -  Purchase orders over $X require approvals from a manager.
 -  Purchase orders containing more than $Y unique products require approval.
 -  Purchase orders with shipping charges greater than $Z require approval.
+​
 
 ## Installation details
 
-The PurchaseOrderRule module has dependencies on the following modules:​
+​
+The PurchaseOrderRule module has dependencies on the following modules:
+​
 
 -  Magento_Company
 -  Magento_Customer
@@ -31,11 +38,15 @@ The PurchaseOrderRule module has dependencies on the following modules:​
 -  Magento_Theme
 -  Magento_Ui
 ​
+
 which must be installed and enabled first. This module does not create any backward incompatible changes. It can be uninstalled or deactivated at any time.
+​
 
 ## Structure
 
+​
 [Learn about a typical file structure for a Magento 2 module](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/module-file-structure.html).
+​
 
 ## Extensibility
 
@@ -51,11 +62,14 @@ This module introduces the following layouts and layout handles in the `view/fro
 - `purchaseorderrule_edit_index`
 - `purchaseorderrule_form`
 - `purchaseorderrule_index_index`
+​
 
 ### UI components
 
+​
 You can extend the purchase order rule listings using the `purchase_order_rule_listing.xml` and `require_my_approval_purchaseorder_listing.xml` configuration files.
 
 ## Additional information
 
+​
 Check the [B2B release notes](https://devdocs.magento.com/guides/v2.4/release-notes/b2b-release-notes.html) for more information on new changes.