Small changes

src/_includes/config/es-elasticsearch-magento-24.md

@@ -14,8 +14,8 @@ Unless you changed Elasticsearch server settings, the defaults should work. Skip
 
 |Option|Description|
 |--- |--- |
-|**Elasticsearch Server Hostname**|Enter the fully qualified hostname or IP address of the machine running Elasticsearch.</br>{{site.data.var.ece}}: Get this value from your integration system.|
-|**Elasticsearch Server Port**|Enter the Elasticsearch web server proxy port. The default is 9200.</br>{{site.data.var.ece}}: Get this value from your integration system.|
+|**Elasticsearch Server Hostname**|Enter the fully qualified hostname or IP address of the machine running Elasticsearch. <br/> {{site.data.var.ece}}: Get this value from your integration system.|
+|**Elasticsearch Server Port**|Enter the Elasticsearch web server proxy port. The default is 9200.<br/>{{site.data.var.ece}}: Get this value from your integration system.|
 |**Elasticsearch Index Prefix**|Enter the Elasticsearch index prefix. If you use a single Elasticsearch instance for more than one Magento installation (Staging and Production environments), you must specify a unique prefix for each installation. Otherwise, you can use the default prefix magento2.|
 |**Enable Elasticsearch HTTP Auth**|Click **Yes** only if you enabled authentication for your Elasticsearch server. If so, provide a username and password in the provided fields.|
 

src/_includes/webapi/services23.md

@@ -81,15 +81,15 @@ bundleProductOptionTypeListV1
 ```http
 catalogAttributeSetManagementV1
 catalogAttributeSetRepositoryV1
-catalogBasePriceStorageV1 *
+catalogBasePriceStorageV1
 catalogCategoryAttributeOptionManagementV1
 catalogCategoryAttributeRepositoryV1
 catalogCategoryLinkManagementV1
 catalogCategoryLinkRepositoryV1
-catalogCategoryListV1 *
+catalogCategoryListV1
 catalogCategoryManagementV1
 catalogCategoryRepositoryV1
-catalogCostStorageV1 *
+catalogCostStorageV1
 catalogProductAttributeGroupRepositoryV1
 catalogProductAttributeManagementV1
 catalogProductAttributeMediaGalleryManagementV1
@@ -102,13 +102,13 @@ catalogProductLinkManagementV1
 catalogProductLinkRepositoryV1
 catalogProductLinkTypeListV1
 catalogProductMediaAttributeManagementV1
-catalogProductRenderListV1 *
+catalogProductRenderListV1
 catalogProductRepositoryV1
 catalogProductTierPriceManagementV1
 catalogProductTypeListV1
 catalogProductWebsiteLinkRepositoryV1
-catalogSpecialPriceStorageV1 *
-catalogTierPriceStorageV1 *
+catalogSpecialPriceStorageV1
+catalogTierPriceStorageV1
 ```
 
 ### CatalogInventory

src/_includes/webapi/services24.md

@@ -75,15 +75,15 @@ bundleProductOptionTypeListV1
 ```http
 catalogAttributeSetManagementV1
 catalogAttributeSetRepositoryV1
-catalogBasePriceStorageV1 *
+catalogBasePriceStorageV1
 catalogCategoryAttributeOptionManagementV1
 catalogCategoryAttributeRepositoryV1
 catalogCategoryLinkManagementV1
 catalogCategoryLinkRepositoryV1
-catalogCategoryListV1 *
+catalogCategoryListV1
 catalogCategoryManagementV1
 catalogCategoryRepositoryV1
-catalogCostStorageV1 *
+catalogCostStorageV1
 catalogProductAttributeGroupRepositoryV1
 catalogProductAttributeManagementV1
 catalogProductAttributeMediaGalleryManagementV1
@@ -96,13 +96,13 @@ catalogProductLinkManagementV1
 catalogProductLinkRepositoryV1
 catalogProductLinkTypeListV1
 catalogProductMediaAttributeManagementV1
-catalogProductRenderListV1 *
+catalogProductRenderListV1
 catalogProductRepositoryV1
 catalogProductTierPriceManagementV1
 catalogProductTypeListV1
 catalogProductWebsiteLinkRepositoryV1
-catalogSpecialPriceStorageV1 *
-catalogTierPriceStorageV1 *
+catalogSpecialPriceStorageV1
+catalogTierPriceStorageV1
 ```
 
 ### CatalogInventory

src/cloud/project/magento-app-workers.md

@@ -37,5 +37,3 @@ workers:
 ```
 
 This example defines a single worker named queue, with a "small" container, and runs the command `php worker.php` on startup. If `worker.php` exits, it is automatically restarted.
-
-For {{site.data.var.ece}} 2.1.x, you can use only workers and [cron jobs]({{ site.baseurl }}/cloud/project/magento-app-properties.html#crons). For {{site.data.var.ece}} 2.2.x, cron jobs launch consumers to process batches of messages, and does not require additional configuration.

src/guides/v2.3/config-guide/deployment/pipeline/technical-details.md

@@ -39,7 +39,7 @@ Set the shared configuration in the Magento Admin in your development (or {{site
 
 ### Manage the system-specific configuration
 
-The system-specific configuration is stored in `app/config/env.php`, which should _not_ be in source control.
+The system-specific configuration is stored in `app/etc/env.php`, which should _not_ be in source control.
 
 Set the system-specific configuration in the Magento Admin in your development (or {{site.data.var.ece}} integration) system and write the configuration to `env.php` using the [`magento app:config:dump` command]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-config-mgmt-export.html).
 

src/guides/v2.3/frontend-dev-guide/themes/theme-inherit.md

@@ -134,8 +134,8 @@ The layouts processing mechanism does not involve fallback. The system collects
 1. Ancestor theme layouts, starting from the most distant ancestor, recursively until a theme with no parent is reached: `<parent_theme_dir>/<Vendor>_<Module>/layout/`
 
 1. All module layout files in sequence, defined in `app/etc/config.php` respecting the component load order. For each module:
-    *  Layout files for the `base` area: `<module_dir>/view/base/layout/`
-    *  Layout files for the `frontend` area: `<module_dir>/view/frontend/layout/`
+   *  Layout files for the `base` area: `<module_dir>/view/base/layout/`
+   *  Layout files for the `frontend` area: `<module_dir>/view/frontend/layout/`
 
 Unlike templates or images, layout can be not only overridden, but also extended. And the recommended way to customize layout is to extend it by creating theme extending layout files.
 

src/guides/v2.3/howdoi/customize-modifier-class.md

@@ -22,7 +22,7 @@ To add your custom modifier, you need to do the following:
 
 ## Add your modifier {#modifier}
 
-In your custom module directory, add the modifier class that implements the `Magento\UI\DataProvider\ModifierInterface` interface or extends the `Magento\Catalog\Ui\DataProvider\Product\Form\Modifier\AbstractModifier`class. In your modifier, the `modifyData()` and the `modifyMeta()` methods must be implemented.
+In your custom module directory, add the modifier class that implements the `Magento\UI\DataProvider\Modifier\ModifierInterface` interface or extends the `Magento\Catalog\Ui\DataProvider\Product\Form\Modifier\AbstractModifier`class. In your modifier, the `modifyData()` and the `modifyMeta()` methods must be implemented.
 
 In the modifier class, you can add UI elements using the same structure as in the [XML](https://glossary.magento.com/xml) configuration.
 

src/guides/v2.3/javascript-dev-guide/widgets/widget_gallery_mg.md

@@ -7,6 +7,8 @@ title: Magnifier widget
 Magnifier is a [widget](https://glossary.magento.com/widget) that allows displaying images in 100% scaled size in a separate dedicated layer.
 In Magento it is used by the [gallery]({{ page.baseurl }}/javascript-dev-guide/widgets/widget_gallery.html) widget for zooming the product images on product pages. It must be enabled in your local theme `view.xml` configuration file.
 
+The Magnifier widget source is located in `lib/web/magnifier/magnify.js`.
+
 ## Initialize magnifier {#magnifier_init}
 
 The magnifier widget is initialized as described in [JavaScript initialization]({{ page.baseurl }}/javascript-dev-guide/javascript/js_init.html#init_phtml).