Vale

Author: mnocon

docs/administration/back_office/configure_product_tour.md

@@ -8,7 +8,7 @@ month_change: false
 
 You can configure the product tour scenarios to adapt it to your project needs, covering different onboarding scenarios.
 
-Product tour scenarios are configured using YAML configuration files.
+Product tour scenarios are configured with YAML configuration files.
 Configuration is SiteAccess-aware, allowing you to create separate onboarding experiences for different back offices in [multisite setups](multisite.md).
 
 For more advanced customization cases that require PHP code, see [Customize product tour](customize_product_tour.md).
@@ -272,7 +272,7 @@ The following example showcases all the built-in block types for a `general` sce
 
 ### Example 2: Targeted feature tour with interactive steps
 
-The following example showcases the 3 interaction modes of a `targetable` scenario building an onboarding scenario for the [customizable dashboard](customize_dashboard.md):
+The following example showcases the three interaction modes of a `targetable` scenario building an onboarding scenario for the [customizable dashboard](customize_dashboard.md):
 
 ```yaml
 [[= include_file('code_samples/back_office/product_tour/config/targetable_scenario.yaml') =]]

docs/administration/back_office/customize_product_tour.md

@@ -9,10 +9,10 @@ month_change: true
 You can customize the product tour scenarios with the [`RenderProductTourScenarioEvent`](integrated_help_events.md) event.
 This event is dispatched before rendering a product tour scenario and you can use it to:
 
-- Modify tour steps based on user permissions or roles
-- Add or remove steps dynamically
-- Change block content based on runtime conditions
-- Integrate custom data into tour scenarios
+- modify tour steps based on user permissions or roles
+- add or remove steps dynamically
+- change block content based on runtime conditions
+- integrate custom data into tour scenarios
 
 With the following example, a custom onboarding scenario is built.
 It starts only when the current user has a pending [notification]([[= user_doc =]]/getting_started/notifications/).