Unified admonitions (#3208)

Author: mnocon

docs/administration/back_office/configure_product_tour.md

@@ -112,7 +112,7 @@ product_tour:
 When creating new [back office user groups](user_registration.md#user-types), decide whether the existing product tour scenarios should be available for these new user groups.
 If not, add the new group to the exclusion list.
 
-!!! warning
+!!! caution
 
     If a scenario contains information meant only for specific group of users, always use the `user_groups_excluded` setting to exclude other groups.
     Don't rely only on UI access restrictions to control the access to scenarios, as a malicious internal user could trigger and preview them outside of the intended place.

docs/administration/dashboard/customize_dashboard.md

@@ -6,7 +6,7 @@ edition: experience
 
 # Customize dashboard
 
-!!! info
+!!! note
 
      The Dashboard Builder is available only in the Experience and Commerce editions.
      The dashboard from the Headless edition can be customized using [Twig Components](components.md).

docs/commerce/transactional_emails/transactional_emails.md

@@ -75,7 +75,7 @@ Create campaigns of transactional email type, one for each notification type tha
 When you build a campaign template, make sure that you use the variables supported by [[= product_name =]].
 For a complete list of parameters, see [Transactional email variables reference](transactional_emails_parameters.md).
 
-!!! Tip
+!!! tip
 
     When you invent names for your campaigns, keep them simple, and don't use special characters or spaces.
 

docs/infrastructure_and_maintenance/background_tasks.md

@@ -139,7 +139,7 @@ php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenge
 
 In [multi-repository setups](repository_configuration.md), the worker process always works for a [SiteAccess](multisite_configuration.md#siteaccess-configuration) that you indicate by using the `--siteaccess` option, therefore you may need to run multiple workers, one for each SiteAccess.
 
-!!! warning "Multi-repository setups"
+!!! caution "Multi-repository setups"
 
     Doctrine transport works across multiple repositories without issues, but other transports may need to be adjusted, so that queues across different repositories are not accidentally shared.
 

docs/personalization/legacy_recommendation_api.md

@@ -72,7 +72,7 @@ It fetches 8 recommendations for user Smith, who is watching the item 123 and th
 The recommendation request returns a list of item IDs that are JSON, JSONP or XML-formatted.
 The result can be integrated into any webpage by using some lines of script code. 
 
-!!! tips
+!!! tip
 
     See the [Quickstart Guide](integrate_recommendation_service.md) for a simple example written in PHP.
 

docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md

@@ -35,7 +35,7 @@ You can then proceed with consecutive upgrades to further versions: v1.13 LTS an
         See [ezpublish-kernel:doc/bc/changes-6.0.md](https://github.com/ezsystems/ezpublish-kernel/blob/v6.7.0/doc/bc/changes-6.0.md)
 
 
-!!! warning "Unsupported legacy sorting methods"
+!!! caution "Unsupported legacy sorting methods"
 
     In older eZ Publish versions, sub-items of content items could be sorted by Class identifier (option value 6) or Class name (option value 7).
     These sorting methods are no longer supported in [[= product_name =]].