enhance: fix broken links

crowdsec-docs/docs/intro.mdx

@@ -29,7 +29,7 @@ The crowd-sourced aspect allows the sharing of attacks they detected and blocked
 
 In addition to the core "detect and react" mechanism, CrowdSec is committed to several other key aspects:
 
--   **Easy Installation**: Effortless out-of-the-box installation on all [supported platforms](/getting_started/versions_matrix.md).
+-   **Easy Installation**: Effortless out-of-the-box installation on all [supported platforms](/u/getting_started/intro).
 -   **Simplified Daily Operations**: You have access to our Web UI administration via [CrowdSec's console](http://app.crowdsec.net) or the powerful [Command line tool cscli](/cscli/cscli.md) for effortless maintenance and keeping your detection mechanisms up-to-date.
 -   **Reproducibility**: The Security Engine can analyze not only live logs but also [cold logs](/u/user_guides/replay_mode), making it easier to detect potential false triggers, conduct forensic analysis, or generate reports.
 -   **Versatile**: The Security Engine can analyze [system logs](/docs/data_sources/intro) and [HTTP Requests](/docs/next/appsec/intro) to exhaustively protect your perimeter.

crowdsec-docs/unversioned/blocklists/intro.md

@@ -28,7 +28,7 @@ CrowdSec Blocklists are available in three tiers:
 
 - Community:
     - Limited number of Blocklists (Third-party and Free).
-    - You are limited to 3 Blocklists across [Integrations](integrations/intro.mdx) and [Security Engines](getting_started/introduction.md).
+    - You are limited to 3 Blocklists across [Integrations](integrations/intro.mdx) and [Security Engines](getting_started/introduction.mdx).
 - Premium (Included in paid plans):
     - Includes free tier
     - Removes the limit on the number of Blocklists you can use.

crowdsec-docs/unversioned/console/getting_started.mdx

@@ -32,4 +32,4 @@ Depending on your use case you may want to start with the following guides:
     link="/u/blocklists/getting_started/"
 />
 <br/>
-If you're new to CrowdSec, we recommend starting with the [Security Engine](/getting_started/introduction.md) guide, however, if you are unsure where to start, feel free to browse our [main website for more information](https://www.crowdsec.net/).
+If you're new to CrowdSec, we recommend starting with the [Security Engine](/getting_started/introduction.mdx) guide, however, if you are unsure where to start, feel free to browse our [main website for more information](https://www.crowdsec.net/).

crowdsec-docs/unversioned/console/notification_integrations/rule.mdx

@@ -14,15 +14,15 @@ By setting up specific rules, you can ensure that you are only notified about ev
 This guide will walk you through the process of creating a notification rule for your linked integration.
 
 > You need at least one integration linked to your CrowdSec Console to create a notification rule.
-> If you haven't linked an integration yet, please refer to the [Integrations Overview](/u/console/notification_integrations/overview) for more information on how to do so.
+> If you haven't linked an integration yet, please refer to the [Integrations Overview](overview.mdx) for more information on how to do so.
 
 ## Create a notification rule
 
 1. In the [CrowdSec Console](https://app.crowdsec.net), navigate to **Settings > Notifications** or **Settings > Integrations > (integration of your choice)** and click on add rule.
 
 ![](/img/console/notification_integrations/notification-rule-list.png)
 
-2. Select the events you want to be notified about. You can only select one of the three category at the time (Threat Hunting, Stack or Admin). Each of these categories contains a list of [events](/notification_integrations/overview.mdx) that you can choose from. (Threat hunting category let you select only one event due to its conditions variance).
+2. Select the events you want to be notified about. You can only select one of the three category at the time (Threat Hunting, Stack or Admin). Each of these categories contains a list of [events](overview.mdx) that you can choose from. (Threat hunting category let you select only one event due to its conditions variance).
 
 ![](/img/console/notification_integrations/events-selection.png)
 

crowdsec-docs/unversioned/console/notification_integrations/webhook.mdx

@@ -87,7 +87,7 @@ Only one option may be checked under this category
 
 #### `Is Attacked`
 
-Your organization is under attack, known as the `am I under attack` feature [documentation](console/security_engines/am_i_under_attack.md)
+Your organization is under attack, known as the `am I under attack` feature [documentation](console/security_engines/am_i_under_attack.mdx)
 
 ```json
 {

crowdsec-docs/unversioned/getting_started/introduction.mdx

@@ -74,8 +74,6 @@ We support the following operating systems:
 * [pfSense](/getting_started/installation/pfsense.mdx)
 * [WHM](/getting_started/installation/whm.mdx)
 
-[See version matrix for detailed breakdown](/docs/next/getting_started/versions_matrix)
-
 ### Ports
 
 CrowdSec Security Engine uses the following default ports (bound to localhost/loopback by default) - these can be altered after installation:

crowdsec-docs/unversioned/getting_started/post_installation/acquisition.mdx

@@ -60,7 +60,7 @@ Collections are a group of [Parsers](https://docs.crowdsec.net/docs/next/parsers
 
 ## Next steps?
 
-If you already see all services you want covered by the then you can [head back to the post installation steps.](/getting_started/next_steps.md#3-acquisitions)
+If you already see all services you want covered by the then you can [head back to the post installation steps.](/getting_started/next_steps.mdx#3-acquisitions)
 
 Follow the [how to setup a new acquisition](/getting_started/post_installation/acquisition_new.mdx) section if you see some log sources are not being monitored.
 

crowdsec-docs/unversioned/getting_started/post_installation/console.mdx

@@ -146,4 +146,4 @@ Now that you have enrolled your first engine, you can start exploring the consol
 - [Third-Party Blocklists](/getting_started/post_installation/console_blocklists.mdx)
 - [CrowdSec Hub](/getting_started/post_installation/console_hub.mdx)
 
-If not head back to the [post installation steps](/getting_started/next_steps.md#1-crowdsec-console) to follow the rest of the steps.
+If not head back to the [post installation steps](/getting_started/next_steps.mdx#1-crowdsec-console) to follow the rest of the steps.

crowdsec-docs/unversioned/getting_started/post_installation/console_blocklists.mdx

@@ -107,4 +107,4 @@ Now that you have subscribed your engine to a list, you can continue exploring t
 
 - [CrowdSec Hub](/getting_started/post_installation/console_hub.mdx)
 
-If not head back to the [post installation steps](/getting_started/next_steps.md#1-crowdsec-console) to follow the rest of the steps.
+If not head back to the [post installation steps](/getting_started/next_steps.mdx#1-crowdsec-console) to follow the rest of the steps.

crowdsec-docs/unversioned/getting_started/post_installation/console_hub.mdx

@@ -140,4 +140,4 @@ These rules are defined and loaded by [AppSec Configurations](/docs/next/appsec/
 
 ## Next Steps?
 
-Now that you have viewed the CrowdSec Hub, you can head back to the [post installation steps](/getting_started/next_steps.md#1-crowdsec-console) to follow the rest of the steps.
+Now that you have viewed the CrowdSec Hub, you can head back to the [post installation steps](/getting_started/next_steps.mdx#1-crowdsec-console) to follow the rest of the steps.

crowdsec-docs/unversioned/getting_started/post_installation/troubleshoot.mdx

@@ -47,7 +47,7 @@ Please update the above commands to match your log location if it is different.
 level=fatal msg="while serving local API: listen tcp 127.0.0.1:8080: bind: address already in use"
 ```
 
-By default as outlined in the [prerequisites](/unversioned/getting_started/prerequisites.md) page, CrowdSec uses ports `6060` and `8080`. If you have another service using these ports you will need to alter CrowdSec configuration to use different ports.
+By default as outlined in the [prerequisites](/unversioned/getting_started/introduction.mdx) page, CrowdSec uses ports `6060` and `8080`. If you have another service using these ports you will need to alter CrowdSec configuration to use different ports.
 
 This can be achieved by modifying two configuration files here are the locations of the files:
 
@@ -91,4 +91,4 @@ After you have made the changes you will need to restart the CrowdSec service.
 
 If the above hasn't resolved the issue you are facing, you can find more detailed troubleshooting documentation [here](/troubleshooting/intro.md).
 
-If you have resolved the issue you can continue with the [post installation steps](/getting_started/next_steps.md#1-crowdsec-console).
+If you have resolved the issue you can continue with the [post installation steps](/getting_started/next_steps.mdx#1-crowdsec-console).

crowdsec-docs/unversioned/getting_started/post_installation/whitelists.mdx

@@ -91,7 +91,7 @@ If you are unsure if you need a whitelist, you can monitor the logs and see if t
 
 However, please note if you should get a decision made agaisnt your IP address and using remediation components such as `iptables` or `nftables` then this will prevent you from accessing **ANY** service on the server.
 
-Within our enterprise offering we have a feature called [Decision Management](console/decisions/decisions_management.md) that allows you to manage decisions via the [console](https://app.crowdsec.net/).
+Within our enterprise offering we have a feature called [Decision Management](console/decisions/decisions_management.mdx) that allows you to manage decisions via the [console](https://app.crowdsec.net/).
 
 ## Creating your first whitelist.
 
@@ -298,4 +298,4 @@ sudo cscli decisions delete --ip 192.168.1.1
 
 If you are still looking for examples on how to create a whitelist, you can find more detailed documentation [here](/docs/next/whitelist/intro).
 
-If you have created your first whitelist, tested it and happy to continue then [click here](getting_started/next_steps.md#2-whitelists).
+If you have created your first whitelist, tested it and happy to continue then [click here](getting_started/next_steps.mdx#2-whitelists).

crowdsec-docs/unversioned/user_guides/consuming_fastly_logs.md

@@ -57,7 +57,7 @@ We configure rsyslog to ignore local syslogs and keep only remote syslog. Then w
 
 ## Install crowdsec with fastly collection
 
-On the same machine, install crowdsec following as mentioned [here](/getting_started/introduction.md)
+On the same machine, install crowdsec following as mentioned [here](/getting_started/introduction.mdx)
 
 ### Setup  acquisition
 
@@ -82,4 +82,4 @@ sudo cscli collections install crowdsecurity/fastly
 ### Reload crowdec
 ```
 sudo systemctl reload crowdsec.service
-```
+```