Merge pull request #2463 from spryker/hotfixes-1

Hotfixes for checkers

Gemfile

@@ -1,7 +1,7 @@
 source "https://rubygems.org"
 
 # Specify the Ruby version for the project.
-ruby '3.2.2'
+ruby '3.2.3'
 
 gem "jekyll", "~> 4.2.0"
 

docs/pbc/all/offer-management/202311.0/unified-commerce/unified-commerce-create-and-edit-product-offers.md

@@ -8,16 +8,18 @@ This document describes how to create and edit product offers in the Merchant Po
 
 ## Prerequisites
 
-To start managing product offers, in the Merchant Portal, go to **Offers**.
+* To start managing product offers, in the Merchant Portal, go to **Offers**.
 
-Review the [reference information](#reference-information-create-and-edit-product-offers) before you start, or look up the necessary information as you go through the process.
+* Review the [reference information](#reference-information-create-and-edit-product-offers) before you start, or look up the necessary information as you go through the process.
 
 ## Create a product offer
 
 1. On the **Offers** page, click **Add Offer**.
     This opens the **Create Offer** page.
+
 2. In the **List of Products** pane, select the product to create an offer for.
-  The **Create Offer** drawer opens.
+    This opens the **Create Offer** drawer.
+
 3. Optional: To make the offer active after creating it, select **Offer is Active**.
 4. Optional: Enter a **Merchant SKU**.
 5. Select one or more **Stores**.
@@ -28,17 +30,19 @@ Review the [reference information](#reference-information-create-and-edit-produc
   2. Select a **STORE**.
   3. Select a **CURRENCY**.
   4. Optional: Enter any of the prices:
-    * **NET DEFAULT**
-    * **GROSS DEFAULT**
-    * **NET ORIGINAL**
-    * **GROSS ORIGINAL**
+      * **NET DEFAULT**
+      * **GROSS DEFAULT**
+      * **NET ORIGINAL**
+      * **GROSS ORIGINAL**
+
   5. Optional: Enter a **VOLUME QUANTITY**.
   6. Repeat steps 1-5 until you add all the needed prices.
 9. Optional: Select **Validity Dates**.
 10. For **SERVICE POINT**, start typing and select a service point.
 11. Select one or more **SERVICES**.
 12. Optional: Select one or more **Shipment Types**.
 13. Scroll up and click **Create**.
+
     This reloads the page with a success message displayed. The created offer is displayed in the list.
 
 ![img](https://spryker.s3.eu-central-1.amazonaws.com/docs/Marketplace/user+guides/Merchant+Portal+user+guides/Offers/creating-product-offers.gif)

docs/pbc/all/service-point-management/202311.0/unified-commerce/manage-using-glue-api/manage-service-points/glue-api-retrieve-service-points.md

@@ -25,7 +25,7 @@ This endpoint lets you retrieve service points.
 
 | QUERY PARAMETER | API TYPE | DESCRIPTION | POSSIBLE VALUES |
 |-|-|-|-|
-| include | Backend | Adds resource relationships to the request. | services service-point-addresses |
+| include | Backend | Adds resource relationships to the request. | services, service-point-addresses |
 
 | REQUEST | API TYPE | USAGE |
 |-|-|-|
@@ -443,7 +443,7 @@ This endpoint lets you retrieve service points.
 
 | QUERY PARAMETER | API TYPE | DESCRIPTION | POSSIBLE VALUES |
 |-|-|-|-|
-| include | Backend | Adds resource relationships to the request. | services service-point-addresses |
+| include | Backend | Adds resource relationships to the request. | services, service-point-addresses |
 
 | REQUEST | API TYPE | USAGE |
 |-|-|-|

docs/pbc/all/service-point-management/202311.0/unified-commerce/service-points-feature-overview.md

@@ -10,11 +10,9 @@ The *Service Points* feature lets you create and manage service points, service
 
 A *service point* is a physical location where services are provided. Depending on the services provided, there can be different kinds of service points, like a warehouse or a physical store. The definition of a service point ultimately depends on the services it provides.
 
-To add service points and service point addresses using Glue API, see [Backend API Marketplace B2C Demo Shop reference](/docs/scos/dev/glue-api-guides/{{page.version}}/backend-glue-infrastructure/backend-api-marketplace-b2c-demo-shop-reference.html).
+To add service points using Glue API, see [Add service points](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/manage-using-glue-api/manage-service-points/glue-api-add-service-points.html). To import service points, see [Import file details: service_point.csv](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/import-and-export-data/import-file-details-service-point.csv.html).
 
-To import service points, see [Import file details: service_point.csv](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/import-and-export-data/import-file-details-service-point.csv.html).
-
-To import service point addresses, see [Import file details: service_point_address.csv](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/import-and-export-data/import-file-details-service-point-address.csv.html)
+To add service point addresses using Glue API, see [Add service point addresses](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/manage-using-glue-api/manage-service-point-addresses/glue-api-add-service-point-addresses.html). To import service point addresses, see [Import file details: service_point_address.csv](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/import-and-export-data/import-file-details-service-point-address.csv.html)
 
 ## Service type
 
@@ -24,7 +22,7 @@ A *service type* is a classification of services that a business offers to its c
 * Rental service
 * Repair service
 
-To add service types using Glue API, see [Backend API Marketplace B2C Demo Shop reference](/docs/scos/dev/glue-api-guides/{{page.version}}/backend-glue-infrastructure/backend-api-marketplace-b2c-demo-shop-reference.html).
+To add service types using Glue API, see [Add service types](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/manage-using-glue-api/manage-service-types/glue-api-add-service-types.html).
 
 To import service types, see [Import file details: service_type.csv](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/import-and-export-data/import-file-details-service-type.csv.html).
 
@@ -33,7 +31,7 @@ To import service types, see [Import file details: service_type.csv](/docs/pbc/a
 
 A *service* represents a specific service type that is provided at a specific service point. Because each service is unique, if two service points provide services with the same service type, like pickup, those services are represented as two separate entities and are managed accordingly. For example, a pickup service at a retail location at Julie-Wolfthorn-Straße 1, 10115, Berlin is a unique service.
 
-To add services using Glue API, see [Backend API Marketplace B2C Demo Shop reference](/docs/scos/dev/glue-api-guides/{{page.version}}/backend-glue-infrastructure/backend-api-marketplace-b2c-demo-shop-reference.html).
+To add services using Glue API, see [Add services](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/manage-using-glue-api/manage-services/glue-api-add-services.html).
 
 To import services, see [Import file details: service.csv](/docs/pbc/all/service-point-management/{{page.version}}/unified-commerce/import-and-export-data/import-file-details-service.csv.html).
 
@@ -44,13 +42,13 @@ To import services, see [Import file details: service.csv](/docs/pbc/all/service
 With the help of service points, types, and services, a store operator can model different use cases depending on their business needs. Here are some examples of services that can be implemented at the project level:
 * Ship from store
 * Car maintenance or installations services
-* Product demonstration at the retail location
-* Repair service at the retail location
+* Product demonstration at a retail location
+* Repair service at a retail location
 
 
 ## Service points on the Storefront
 
-When checking out, customers select a service point they want to process their order at. The feature is shipped with a search widget that lets them search service points by the following:
+When checking out, customers select a service point they want the order to be processes at. The feature is shipped with a search widget that lets them search service points by the following:
 * Service point name
 * Zip code
 * City

docs/scos/dev/front-end-development/202311.0/oryx/architecture/reactivity/key-concepts-of-reactivity.md

@@ -56,7 +56,7 @@ Description:
 2. `ProductController` uses finds out the relevant _context_ for the component and resolves the product qualifier (SKU) in order to make the right request. Whenever the product data is resolved, an update to the DOM is requested. This is actually done in `AsyncStateController`, which is left out on this diagram. The `ProductController` controller uses `ProductService` to resolve the product data.
    `ProductService` is a business service that controls the application state for the product. It makes sure that multiple requests for the same product do not result in multiple requests to the backend. `ProductService` delegates the actual loading of the data to `ProductAdapter`.
 3. `ProductAdapter` integrates with the backend, by creating an HTTP request. The `ProductAdapter` knows the backend endpoint and it's contract so that it can create the right request. The `ProductAdapter` delegates actual HTTP requests to the `HttpService`.  
-   When an alternative backend is integrated, the `ProductAdapter` can be replaced. The adapter converts the API data model to the client-side model in case of a mismatch. This is done by using normalizers. For details, see [Designing the data model](/docs/scos/dev/front-end-development/{{page.version}}/oryx/best-practice.html#designing-the-data-model).
+   When an alternative backend is integrated, the `ProductAdapter` can be replaced. The adapter converts the API data model to the client-side model in case of a mismatch. This is done by using normalizers. <!-- For details, see [Designing the data model](/docs/scos/dev/front-end-development/{{page.version}}/oryx/best-practice.html#designing-the-data-model). -->
 4. `HttpService` is a small wrapper that is used to provide additional features such as support for interceptors.
 
 ## Updating data in the DOM