Merge branch 'master' into IBX-9609-upgrade-mkdocs

Author: adriendupuis

docs/ai_actions/img/ai_actions_list.png

@@ -24,7 +24,7 @@ It may happen that a set of sample AI actions has been [installed with the AI Ac
 !!! note "Custom action types"
 
     In your specific case, the types available can be different, and your organization's development team can create custom AI action types.
-    For more information, see [developer documentation]([[= developer_doc =]]/ai_actions/ai_actions).
+    For more information, see [developer documentation]([[= developer_doc =]]/ai_actions/ai_actions/).
 
 ### View AI action details
 
@@ -101,3 +101,10 @@ For a list of available settings, see [Edit existing AI actions](#edit-existing-
 
 1. Click **Save and close** to apply the changes or **Discard** to discard them and close the window.
 
+## Duplicate AI actions
+
+You can duplicate existing actions, for example, to create a variant version of an action with slightly different settings.
+To do so, in the **AI actions** list, click the **Duplicate** icon next to a name of the AI action that you want to duplicate.
+
+You can then modify the duplicated action (for example, change its name or fine-tine the instructions), enable it and save your changes.
+If you discard your changes, the duplicated action will appear on the actions list with status Disabled.

docs/ai_actions/img/ai_assistant.png

@@ -21,7 +21,7 @@ Available filters are:
 
 !!! note "Order statuses"
 
-    Order statuses visible in the **Status** filter field are defined in the [Order workflow]([[= developer_doc =]]/commerce/order_management/configure_order_management/#order-processing-workflow).
+    Order statuses visible in the **Status** filter field are defined in the [Order workflow]([[= developer_doc =]]/commerce/order_management/configure_order_management/#configure-order-processing-workflow).
 
 - Created - a range of dates between which the order was created
 - Client type - either B2B or B2C client

docs/ai_actions/img/ai_assistant_online_editor.png

@@ -99,7 +99,7 @@ To do it, in the **Select Editor launch mode** section, select one of the availa
 
 When you add or modify a **[Content relation](create_edit_content_items.md#relation_field)** or **Content relation (multiple)** field in a content type, you can decide:
 
-- which content tree location opens in the [content browser](content_model.md#content-browser) when the user browses to a related content item
+- which content tree location opens in the [content browser](discover_ui.md#content-browser) when the user browses to a related content item
 - whether relations can be to content items of a specific type only, or any content type
 
 #### Relation starting location

docs/ai_actions/img/ai_assistant_textline.png

@@ -11,7 +11,7 @@ These fields can differ depending on what kind of content you're dealing with.
 An *article* content item may consist of fields, for example, *title*, *name*, *author*, *body*, *image*, or *subscriber teaser*.
 A *product* content item may have, for example, *product name*, *category*, *price*, *size*, or *color*, as fields.
 
-In [[= product_name =]], you create content items based on templated called [content types](content_model.md#content_types).
+In [[= product_name =]], you create content items based on templated called [content types](content_model.md#content-types).
 
 ## Access content in the UI
 

docs/ai_actions/work_with_ai_actions.md

@@ -53,7 +53,7 @@ Click **Bookmarks** in the left menu to view a list of all of them.
 
 With segments you can target content at specific groups of your users.
 You can use them to display different content to different page visitors.
-To do it, use the [Targeting block](create_edit_pages.md#targeting-block).
+To do it, use the [Targeting block](block_reference.md#targeting-block).
 
 You can create and configure segments and segment groups in the **Admin** section of the back office.
 

docs/commerce/order_management/work_with_orders.md

@@ -82,13 +82,13 @@ This is different from [hiding locations](manage_locations_urls.md#hide-location
 
 !!! caution "Visibility and permissions"
 
-    The [visibility switcher](https://doc.ibexa.co/projects/userguide/en/latest/content_management/content_organization/manage_locations_urls/#hide-locations) is a convenient feature for withdrawing content from the frontend.
+    The [visibility switcher](manage_locations_urls.md#hide-locations) is a convenient feature for withdrawing content from the frontend.
     It acts as a filter in the frontend by default. You can choose to respect it or ignore it in your code.
     It's not permission-based, and **doesn't restrict access to content**.
     Hidden content can be read through other means, like the REST API.
 
     If you need to restrict access to a given content item, you could create a role that grants read access for a given
-    [**Section**](https://doc.ibexa.co/projects/userguide/en/latest/content_management/content_organization/classify_content/#sections)
-    or [**Object State**](https://doc.ibexa.co/projects/userguide/en/latest/content_management/content_organization/classify_content/#object-states),
+    [**Section**](classify_content.md#sections)
+    or [**Object State**](classify_content.md#object-states),
     and set a different section or object state for the given content.
-    Or use other permission-based [**Limitations**](https://doc.ibexa.co/projects/userguide/en/latest/permission_management/work_with_permissions/).
+    Or use other permission-based [**Limitations**](work_with_permissions.md).