From 9be753b28148a792aca6f6c441c5d322383bca2a Mon Sep 17 00:00:00 2001 From: Fennerr <41741346+Fennerr@users.noreply.github.com> Date: Mon, 13 Feb 2023 16:20:48 +0200 Subject: [PATCH] docs: Minor changes to the intro paragraph (#1892) --- 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 21f18b89..ab0330c7 100644 --- a/docs/tutorials/aws/v2_to_v3_checks_mapping.md +++ b/docs/tutorials/aws/v2_to_v3_checks_mapping.md @@ -1,6 +1,6 @@ # Check mapping between Prowler v3 and v2 -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. +Prowler v3 comes with different identifiers but we maintained the same checks that were implemented in v2. The reason for this 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](../../compliance/) section.