From fc38ba3acbb1f0b880edb93f8f349b4251c751f8 Mon Sep 17 00:00:00 2001
From: Sergio Garcia <38561120+sergargar@users.noreply.github.com>
Date: Thu, 26 Jan 2023 12:48:58 +0100
Subject: [PATCH] docs(readme): correct compliance link (#1780)

---
 docs/tutorials/aws/v2_to_v3_checks_mapping.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tutorials/aws/v2_to_v3_checks_mapping.md b/docs/tutorials/aws/v2_to_v3_checks_mapping.md
index 874dd854..21f18b89 100644
--- a/docs/tutorials/aws/v2_to_v3_checks_mapping.md
+++ b/docs/tutorials/aws/v2_to_v3_checks_mapping.md
@@ -2,7 +2,7 @@
 
 Prowler v3 comes with different identifiers but we maintained the same checks than v2. The reason of the change is because in previows versions of Prowler, check names were mostly based on CIS Benchmark for AWS, in v3 all checks are independent from any security framework and they have its own name and ID.
 
-If you need more information about how new compliance implementation works in Prowler v3 see [Compliance](/tutorials/compliance/) section.
+If you need more information about how new compliance implementation works in Prowler v3 see [Compliance](../../compliance/) section.
 
 ```
 checks_v3_to_v2_mapping = {