adriendupuis · Aug 18, 2026 · Aug 18, 2026 · Aug 18, 2026
diff --git a/docs/commerce/order_management/configure_order_management.md b/docs/commerce/order_management/configure_order_management.md
@@ -13,7 +13,7 @@ When you work with your Commerce implementation, you can modify and customize th
 
 ## Configure order processing workflow
 
-Order processing workflow relies on a [Symfony Workflow]([[= symfony_doc =]]/components/workflow.html).
+Order processing workflow relies on a [Symfony Workflow]([[= symfony_doc =]]/workflow.html).
 Each transition represents a separate order processing step.
 
 ### Default order processing configuration

diff --git a/docs/commerce/payment/configure_payment.md b/docs/commerce/payment/configure_payment.md
@@ -13,7 +13,7 @@ When you work with your Commerce implementation, you can review and modify the p
 
 ## Configure payment workflow
 
-Payment workflow relies on a [Symfony Workflow]([[= symfony_doc =]]/components/workflow.html).
+Payment workflow relies on a [Symfony Workflow]([[= symfony_doc =]]/workflow.html).
 Each transition represents a separate payment step.
 
 ### Default payment workflow configuration

diff --git a/docs/commerce/shipping_management/configure_shipment.md b/docs/commerce/shipping_management/configure_shipment.md
@@ -13,7 +13,7 @@ When you work with your Commerce implementation, you can review and modify the s
 
 ## Configure shipment workflow
 
-Shipment workflow relies on a [Symfony Workflow]([[= symfony_doc =]]/components/workflow.html).
+Shipment workflow relies on a [Symfony Workflow]([[= symfony_doc =]]/workflow.html).
 Each transition represents a separate shipment step.
 
 The default fallback workflow is `ibexa_shipment`, which is prepended at bundle level.

diff --git a/docs/commerce/transactional_emails/transactional_emails.md b/docs/commerce/transactional_emails/transactional_emails.md
@@ -5,7 +5,7 @@
 
 # Transactional emails
 
-Transactional emails are messages that [[= product_name =]] can send through [Actito](https://www.actito.com/en-BE/) gateway to your end-users to notify them about changes in the status of various actions taken in relation to your commerce presence.
+Transactional emails are messages that [[= product_name =]] can send through [Actito](https://actito.com/en) gateway to your end-users to notify them about changes in the status of various actions taken in relation to your commerce presence.
 
 By default, notifications are sent in relation to the following events, to an email address of the end-user who has originated these events:
 
@@ -40,7 +40,7 @@
 
 ### Configure Actito integration
 
-Before you can start configuring the notifier engine to process and dispatch notifications to be forwarded as transactional emails, you must first obtain and configure an [Actito license](https://www.actito.com/en-BE/pricing/nk).
+Before you can start configuring the notifier engine to process and dispatch notifications to be forwarded as transactional emails, you must first obtain and configure an [Actito license](https://actito.com/en/pricing/).
 
 Once you gain access to the Actito dashboard:
 

diff --git a/docs/discounts/discounts_api.md b/docs/discounts/discounts_api.md
@@ -29,7 +29,7 @@ Discounts are applied in two places, listed in the [`DiscountType`](/api/php_api
 Regardless of activation place, discounts always apply to products and reduce their base price.
 
 To define when a discount activates and how the price is reduced, use rules and conditions.
-They use the [Symfony Expression language]([[= symfony_doc=]]/components/expression_language.html) to express their logic.
+They use the [Symfony Expression language]([[= symfony_doc=]]/expression_language.html) to express their logic.
 
 ### Rules
 

diff --git a/docs/discounts/extend_discounts.md b/docs/discounts/extend_discounts.md
@@ -20,7 +20,7 @@ Together with the existing [events](event_reference.md) and the [Discounts PHP A
 
 With custom [conditions](discounts_api.md#conditions) and [rules](discounts_api.md#rules) you can create more advanced discounts that apply only in specific scenarios.
 
-For both of them, you need to specify their logic with [Symfony's expression language](https://symfony.com/doc/current/components/expression_language.html).
+For both of them, you need to specify their logic with [Symfony's expression language]([[= symfony_doc =]]/expression_language.html).
 
 ### Available expressions
 

diff --git a/docs/ibexa_products/ibexa_commerce.md b/docs/ibexa_products/ibexa_commerce.md
@@ -87,7 +87,7 @@ You can set up your search engine using [[= product_name_com =]] to help clients
 
 #### Transactional emails
 
-Commerce allows you to send transactional emails - messages that [[= product_name_base =]] can send through the [Actito](https://www.actito.com/en-BE/) gateway to your end-users.
+Commerce allows you to send transactional emails - messages that [[= product_name_base =]] can send through the [Actito](https://actito.com/en) gateway to your end-users.
 These emails include notifications about changes in the status of various actions taken in relation to your commerce presence.
 With this feature you can also [create email campaigns](transactional_emails.md#create-email-campaigns) to engage users and increase sales.
 

diff --git a/docs/infrastructure_and_maintenance/cache/persistence_cache.md b/docs/infrastructure_and_maintenance/cache/persistence_cache.md
@@ -46,7 +46,7 @@ To see where and how to contribute additional caches, refer to the [source code]
 !!! note
 
     Current implementation uses [Symfony application cache]([[= symfony_doc =]]/cache.html#system-cache-and-application-cache).
-    It technically supports the following cache backends: [APCu, Array, Chain, Doctrine, Filesystem, PDO & Doctrine DBAL, Php Array, Proxy, Redis]([[= symfony_doc =]]/components/cache/cache_pools.html#creating-cache-pools).
+    It technically supports the following cache backends: [APCu, Array, Chain, Doctrine, Filesystem, PDO & Doctrine DBAL, Php Array, Proxy, Redis]([[= symfony_doc =]]/cache.html#available-cache-adapters).
     [[= product_name =]] officially supports only using Filesystem for single server and Redis/Valkey for clustered setups.
 
 Use of [Redis/Valkey](#redisvalkey) as shared cache backend is a requirement for use in clustering setup.
@@ -267,7 +267,7 @@ $pool->save($cacheItem);
 return $myObject;
 ```
 
-For more info on usage, see [Symfony Cache's documentation]([[= symfony_doc =]]/components/cache.html).
+For more info on usage, see [Symfony Cache's documentation]([[= symfony_doc =]]/cache.html).
 
 ### Clearing persistence cache
 

diff --git a/docs/templating/templates/templates.md b/docs/templating/templates/templates.md
@@ -93,7 +93,7 @@ twig_variables:
 {{ custom_variable.nested_variable }}
 ```
 
-You can use [Symfony Expression language]([[= symfony_doc =]]/components/expression_language.html) to access other values, for example:
+You can use [Symfony Expression language]([[= symfony_doc =]]/expression_language.html) to access other values, for example:
 
 ``` yaml
 params:

diff --git a/docs/update_and_migration/from_2.5/to_3.3.md b/docs/update_and_migration/from_2.5/to_3.3.md
@@ -10,7 +10,7 @@ Before you start this procedure, make sure you have completed the previous step,
 
 ## 5. Update to v3.3
 
-[[= product_name =]] v3.3 uses [Symfony Flex]([[= symfony_doc =]]/quick_tour/flex_recipes.html).
+[[= product_name =]] v3.3 uses [Symfony Flex](https://symfony.com/tour/flex-recipes).
 When updating from v3.2 to v3.3, you need to follow a special update procedure.
 
 !!! note