OpenAEV-Platform · RomuDeuxfois · Mar 3, 2026 · Mar 3, 2026
diff --git a/docs/deployment/breaking-changes/2.1.0-encrypting-password.md b/docs/deployment/breaking-changes/2.1.0-encrypting-password.md
@@ -8,7 +8,7 @@
 
 With the introduction of the composer catalog, built-in connectors are managed through the OpenAEV UI. Those connectors have their configuration saved in database.
 
-For security reasons, the properties of type password need to be encrypted inside the database. This means that we need to introduce two new mandatory properties (as you can see here in the page dedicated to [configuration](../../configuration/#basic-parameters)) :
+For security reasons, the properties of type password need to be encrypted inside the database. This means that we need to introduce two new mandatory properties (as you can see here in the page dedicated to [configuration](../configuration.md#basic-parameters)) :
 
 | Parameter                          | Environment variable               | Default value         | Description                                                                                                              |
 |:-----------------------------------|:-----------------------------------|:----------------------|:-------------------------------------------------------------------------------------------------------------------------|

diff --git a/docs/deployment/certificate-validation.md b/docs/deployment/certificate-validation.md
@@ -126,5 +126,4 @@ When enabled, OpenAEV respects the standard `HTTP_PROXY`, `HTTPS_PROXY`, and `NO
 
 ## What's next?
 
-- [Configuration reference](../configuration.md) — Full list of OpenAEV platform parameters.
-- [Deployment overview](../overview.md) — Architecture and deployment options.
+- [Configuration reference](configuration.md) — Full list of OpenAEV platform parameters.
diff --git a/docs/usage/payloads/payloads.md b/docs/usage/payloads/payloads.md
@@ -85,9 +85,9 @@ To create a new payload, follow these steps:
 
 | Status                                                                     | Description                                                                                                              |
 |----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
-| <span style="color: #00f1bd"> Rules written by Human</span>                | The rules have been written by a human                                                                                    |
-| <span style="color: #9575cd"> Rules generated by AI </span>                | The rules have been generated by AI                                                                                       |
-| <span style="color: #ffa726"> Payload changed since rule was edited</span> | The payload has been edited since last AI rules generation **[(relevant fields)](#Fields-used-for-AI-rules-generation)** |
+| <span style="color: #00f1bd"> Rules written by Human</span>                | The rules have been written by a human                                                                                   |
+| <span style="color: #9575cd"> Rules generated by AI </span>                | The rules have been generated by AI                                                                                      |
+| <span style="color: #ffa726"> Payload changed since rule was edited</span> | The payload has been edited since last AI rules generation **[(relevant fields)](#fields-used-for-ai-rules-generation)** |
 
 ### Fields used for AI rules generation
 

diff --git a/docs/usage/scenario.md b/docs/usage/scenario.md
@@ -27,15 +27,15 @@ XTM Hub provides access to a library of pre-built OpenAEV scenarios that you can
 
 From the XTM Hub, you can effortlessly deploy your desired scenario with just a single click.
 
-To get started, simply register your OpenAEV platform following the instructions in our [OpenAEV registration documentation](/administration/hub/).
+To get started, simply register your OpenAEV platform following the instructions in our [OpenAEV registration documentation](../administration/hub.md).
 Next, navigate to your preferred scenario and click the ```Deploy in OpenAEV``` button located in the top right corner.
 
 If you have multiple OpenAEV platforms registered, choose the platform in which you wish to deploy the scenario.
 
 You will then be redirected to the OpenAEV platform, where the process will continue automatically. 
 Within a few seconds, you'll be taken to the scenarios list, where your newly created scenario will appear.
 
-![Import scenario option](/usage/assets/one-click-deploy.png)
+![Import scenario option](assets/one-click-deploy.png)
 
 ## Scenario overview
 

diff --git a/docs/usage/xtm-suite-connector.md b/docs/usage/xtm-suite-connector.md
@@ -24,7 +24,7 @@ Once the OpenCTI instance is up and running, make sure to obtain these two setti
 * A valid API Token associated with an account with sufficient privileges (refer to: [Configuring the Connector API token](https://docs.opencti.io/latest/deployment/connectors/#connector-token))
 
 ### Enabling the Security Coverage connector in OpenAEV
-Make sure you set a value for all mandatory configuration keys, following the [Configuration documentation for the Security Coverage Connector](../../deployment/configuration#xtm-suite-opencti).
+Make sure you set a value for all mandatory configuration keys, following the [Configuration documentation for the Security Coverage Connector](../deployment/configuration.md#xtm-suite-opencti).
 
 ### Use OpenCTI to trigger security coverage enrichments seamlessly
 The connector is now up and running and should be visible in OpenCTI as _OpenAEV Coverage_.

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -173,6 +173,7 @@ nav:
       - Importing injects into a Scenario: usage/scenario-import.md
       - Assets: usage/assets.md
       - People: usage/people.md
+      - Expectation: usage/expectations.md
       - Components:
         - Documents: usage/components/documents.md
         - Custom variables: usage/components/variables.md

diff --git a/overrides/main.html b/overrides/main.html
@@ -9,7 +9,7 @@
 
 {% block announce %}
 Breaking Changes in OpenAEV 2.2.0 — Resolved in 2.2.1
-<a href="{{ '/2.1.X/deployment/breaking-changes/2.2.0-opencti-security-coverage/' }}">
+<a href="{{ '/2.2.X/deployment/breaking-changes/2.2.0-opencti-security-coverage/' }}">
   <strong>Click here to go to the migration guide.</strong>
 </a>
 {% endblock %}