Merge pull request magento#7050 from magento/em_prex-modulerename

Update product recommendations module names

Author: erikmarr

src/recommendations/events.md

@@ -4,7 +4,7 @@ title: Recommendation Events
 ee_only: True
 ---
 
-When you deploy the `product-recommendations` module, the module tracks the following user events. These events enable  behavioral data collection.
+When you deploy the `magento/product-recommendations` module, the module tracks the following user events. These events enable behavioral data collection.
 
 {:.bs-callout-info}
 If [Cookie Restriction Mode](https://docs.magento.com/m2/ce/user_guide/stores/compliance-cookie-restriction-mode.html) is enabled, Magento does not collect behavioral data until the shopper consents. If Cookie Restriction Mode is disabled, Magento collects behavioral data by default.

src/recommendations/images/filter-tp2.png

@@ -18,16 +18,16 @@ Install the `magento/product-recommendations` module with Composer:
 
 The `magento/product-recommendations` module requires the following dependencies:
 
--  **module-data-services** — This module enables behavioral data collection by tracking [user events on the page]({{ page.baseurl }}/recommendations/events.html). This type of data is required by Adobe Sensei to compute product affinities based on production shopper behavior like product views, products added to a cart, and checkouts. Adobe Sensei then uses this information to create and train machine learning models for each website and storeview. This unlocks recommendation types like "Customers who viewed this, also viewed...", which automatically adjusts with shopper behavior over time. Magento and Adobe Sensei do not collect personally identifiable information.
+-  **data-services** — This module enables behavioral data collection by tracking [user events on the page]({{ page.baseurl }}/recommendations/events.html). This type of data is required by Adobe Sensei to compute product affinities based on production shopper behavior like product views, products added to a cart, and checkouts. Adobe Sensei then uses this information to create and train machine learning models for each website and store view. This unlocks recommendation types like "Customers who viewed this, also viewed...", which automatically adjusts with shopper behavior over time. Magento and Adobe Sensei do not collect personally identifiable information.
 
 -  **saas-export** — This module syncs catalog data. This type of data provides product information to the Product Recommendations service so it can accurately return product names, pricing, images, URLs, inventory and availability, and other attributes.
 
    {:.bs-callout-info}
-   If you prefer, you can install the above modules explicitly using Composer: `composer require magento/module-data-services` and `composer require magento/saas-export`
+   If you prefer, you can install the above modules explicitly using Composer: `composer require magento/data-services` and `composer require magento/saas-export`
 
 ### Update your Product Recommendations installation
 
-If for any reason you need to update the `product-recommendations` module, run the following:
+If for any reason you need to update the `magento/product-recommendations` module, run the following:
 
 ```bash
 composer update magento/product-recommendations --with-dependencies

src/recommendations/install-configure.md

@@ -24,7 +24,7 @@ Product Recommendations require the following data:
 
 -  **Catalog** - Product metadata, such as name, price, availability, and so on.
 
-When you install the `product-recommendations` module, Adobe Sensei aggregates the behavioral and catalog data, creating Product Recommendations for each recommendation type. The Product Recommendations service then deploys those recommendations to your storefront.
+When you install the `magento/product-recommendations` module, Adobe Sensei aggregates the behavioral and catalog data, creating Product Recommendations for each recommendation type. The Product Recommendations service then deploys those recommendations to your storefront.
 
 ## Next steps
 

src/recommendations/product-recs.md

@@ -17,7 +17,7 @@ The following recommendation types are listed in the recommended order when test
 
 ## Testing recommendations on a non-production environment
 
-1. Deploy the `product-recommendations` module to a non-production environment where the catalog data is similar to your production catalog.
+1. Deploy the `magento/product-recommendations` module to a non-production environment where the catalog data is similar to your production catalog.
 
 1. Use one of the non-production SaaS Environment IDs for [configuration](https://docs.magento.com/m2/ce/user_guide/configuration/services/saas.html) in the Magento Admin.
 

src/recommendations/test.md

@@ -4,7 +4,7 @@ title: Verify Event Collection
 ee_only: True
 ---
 
-After you [install]({{ page.baseurl }}/recommendations/product-recs.html) and [configure]({{ page.baseurl }}/recommendations/install-configure.html) the product recommendations module, you can verify that the behavioral data is being sent to Magento. Magento uses the `DataServices.js` file to collect and send behavioral data. You can use developer tools available in Chrome, or you can install the Snowplow Chrome extension.
+After you [install]({{ page.baseurl }}/recommendations/product-recs.html) and [configure]({{ page.baseurl }}/recommendations/install-configure.html) the `magento/product-recommendations` module, you can verify that the behavioral data is being sent to Magento. Magento uses the `DataServices.js` file to collect and send behavioral data. You can use developer tools available in Chrome, or you can install the Snowplow Chrome extension.
 
 ## Verify using developer tools in Chrome