docs: fix typos and grammar (#12278)

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
2026-10-05 03:12:14 +00:00 · 2026-08-03 09:35:37 +02:00
parent e0cb18bdbd
commit 137b388df9
31 changed files with 49 additions and 49 deletions
@@ -39,7 +39,7 @@ The AWS provider implementation follows the general [Provider structure](/develo
 - **Key AWS Responsibilities:**
    - Receives an `AwsProvider` instance to access session, identity, and configuration.
    - Manages clients for all services by regions.
-    - Provides `__threading_call__` method to make boto3 calls in parallel. By default, this calls are made by region, but it can be overridden with the first parameter of the method and use by resource.
+    - Provides `__threading_call__` method to make boto3 calls in parallel. By default, these calls are made by region, but it can be overridden with the first parameter of the method and use by resource.
    - Exposes common audit context (`audited_account`, `audited_account_arn`, `audited_partition`, `audited_resources`) to subclasses.

 ### Exception Handling
@@ -59,7 +59,7 @@ The generic service pattern is described in [service page](/developer-guide/serv
 - Directly in the code, in location [`prowler/providers/aws/services/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/aws/services)
 - In the [Prowler Hub](https://hub.prowler.com/). For a more human-readable view.

-The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other services already implemented as reference. In next subsection you can find a list of common patterns that are used accross all AWS services.
+The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other services already implemented as reference. In next subsection you can find a list of common patterns that are used across all AWS services.

 ### AWS Service Common Patterns

@@ -68,7 +68,7 @@ The best reference to understand how to implement a new service is following the
 - The constructor (`__init__`) always calls `super().__init__` with the service name and provider (e.g. `super().__init__(__class__.__name__, provider))`). Ensure that the service name in boto3 is the same that you use in the constructor. Usually is used the `__class__.__name__` to get the service name because it is the same as the class name.
 - Resource containers **must** be initialized in the constructor. They should be dictionaries, with the key being the resource ARN or equivalent unique identifier and the value being the resource object.
 - Resource discovery and attribute collection are parallelized using `self.__threading_call__`, typically by region or resource, for performance. The first parameter of the method is the iterator, if not provided, it will be the region; but if present indicate an array of the resources to be processed.
- Resource filtering is consistently enforced using `self.audit_resources` attribute and `is_resource_filtered` function, it is used to see if user has provided some resource that is not in the audit scope, so we can skip it in the service logic. Normally it is used befor storing the resource in the service container as follows: `if not self.audit_resources or (is_resource_filtered(resource["arn"], self.audit_resources)):`.
+- Resource filtering is consistently enforced using `self.audit_resources` attribute and `is_resource_filtered` function, it is used to see if user has provided some resource that is not in the audit scope, so we can skip it in the service logic. Normally it is used before storing the resource in the service container as follows: `if not self.audit_resources or (is_resource_filtered(resource["arn"], self.audit_resources)):`.
 - All AWS resources are represented as Pydantic `BaseModel` classes, providing type safety and structured access to resource attributes.
 - AWS API calls are wrapped in try/except blocks, with specific handling for `ClientError` and generic exceptions, always logging errors.
 - If ARN is not present for some resource, it can be constructed using string interpolation, always including partition, service, region, account, and resource ID.
@@ -162,7 +162,7 @@ When you instantiate `Check_Report_AWS`, you must provide the check metadata and

 If the resource object does not contain the required attributes, you must set them manually in the check logic.

-Other attributes are inherited from the `Check_Report` class, from that ones you **always** have to set the `status` and `status_extended` attributes in the check logic.
+Other attributes are inherited from the `Check_Report` class, from those you **always** have to set the `status` and `status_extended` attributes in the check logic.

 #### Example Usage

@@ -57,7 +57,7 @@ The generic service pattern is described in [service page](/developer-guide/serv
 - Directly in the code, in location [`prowler/providers/azure/services/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/azure/services)
 - In the [Prowler Hub](https://hub.prowler.com/) for a more human-readable view.

-The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other services already implemented as reference. In next subsection you can find a list of common patterns that are used accross all Azure services.
+The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other services already implemented as reference. In next subsection you can find a list of common patterns that are used across all Azure services.

 ### Azure Service Common Patterns

@@ -172,7 +172,7 @@ else:

 ### Resource Identification in Prowler

-Each check **must** populate the report with an unique identifier for the audited resource. This identifier or identifiers are going to depend on the provider and the resource that is being audited. Here are the criteria for each provider:
+Each check **must** populate the report with a unique identifier for the audited resource. This identifier or identifiers are going to depend on the provider and the resource that is being audited. Here are the criteria for each provider:

 - AWS
    - Amazon Resource ID — `report.resource_id`.
@@ -102,7 +102,7 @@ The generic service pattern is described in [service page](/developer-guide/serv
 - Directly in the code, in location [`prowler/providers/gcp/services/`](https://github.com/prowler-cloud/prowler/tree/master/prowler/providers/gcp/services)
 - In the [Prowler Hub](https://hub.prowler.com/) for a more human-readable view.

-The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other services already implemented as reference. In next subsection you can find a list of common patterns that are used accross all GCP services.
+The best reference to understand how to implement a new service is following the [service implementation documentation](/developer-guide/services#adding-a-new-service) and taking other services already implemented as reference. In next subsection you can find a list of common patterns that are used across all GCP services.

 ### GCP Service Common Patterns

@@ -113,7 +113,7 @@ The best reference to understand how to implement a new service is following the
 - Only projects with the API enabled are included in the audit scope.
 - Resource discovery and attribute collection can be parallelized using `self.__threading_call__`, typically by region/zone or resource.
 - All GCP resources are represented as Pydantic `BaseModel` classes, providing type safety and structured access to resource attributes.
- Each GCP API calls are wrapped in try/except blocks, always logging errors.
+- Each GCP API call is wrapped in try/except blocks, always logging errors.
 - **Retry Configuration**: All `request.execute()` calls must include `num_retries=DEFAULT_RETRY_ATTEMPTS` for automatic retry on rate limiting errors (HTTP 429).
 - Tags and additional attributes that cannot be retrieved from the default call should be collected and stored for each resource using dedicated methods and threading.

@@ -161,7 +161,7 @@ When you instantiate `Check_Report_GCP`, you must provide the check metadata and
    - Defaults to "global" if none are available.

 All these attributes can be overridden by passing the corresponding argument to the constructor. If the resource object does not contain the required attributes, you must set them manually.
-Others attributes are inherited from the `Check_Report` class, from that ones you **always** have to set the `status` and `status_extended` attributes in the check logic.
+Other attributes are inherited from the `Check_Report` class, from those you **always** have to set the `status` and `status_extended` attributes in the check logic.

 #### Example Usage

@@ -352,7 +352,7 @@ result = await self.api_client.poll_task_until_complete(

 ### Tool Docstrings

-Tool docstrings become description that is going to be read by the LLM. Provide clear usage instructions and common workflows:
+Tool docstrings become the description that is going to be read by the LLM. Provide clear usage instructions and common workflows:

 ```python
 async def search_items(self, status: str = Field(...)) -> dict:
@@ -31,7 +31,7 @@ Before implementing a new provider, you need to determine which type it belongs

 #### Decision Criteria

-Once you have decided the provider you want or need to add to Prowler, the next step is to study how to retrieve data from it. Based on that, the provider will fall into one of the following types: SDK, API or Tool/Wrapper (maybe in the future there will be new types but for now this are the only ones).
+Once you have decided the provider you want or need to add to Prowler, the next step is to study how to retrieve data from it. Based on that, the provider will fall into one of the following types: SDK, API or Tool/Wrapper (maybe in the future there will be new types but for now these are the only ones).

 **Choose SDK Provider if:**

@@ -9,7 +9,7 @@ First ensure that the provider you want to add the service is already created. I
 </Note>
 ## Introduction

-In Prowler, a **service** represents a specific solution or resource offered by one of the supported [Prowler Providers](/developer-guide/provider), for example, [EC2](https://aws.amazon.com/ec2/) in AWS, or [Microsoft Exchange](https://www.microsoft.com/en-us/microsoft-365/exchange/exchange-online) in M365. Services are the building blocks that allow Prowler interact directly with the various resources exposed by each provider.
+In Prowler, a **service** represents a specific solution or resource offered by one of the supported [Prowler Providers](/developer-guide/provider), for example, [EC2](https://aws.amazon.com/ec2/) in AWS, or [Microsoft Exchange](https://www.microsoft.com/en-us/microsoft-365/exchange/exchange-online) in M365. Services are the building blocks that allow Prowler to interact directly with the various resources exposed by each provider.

 Each service is implemented as a class that encapsulates all the logic, data models, and API interactions required to gather and store information about that service's resources. All of this data is used by the [Prowler checks](/developer-guide/checks) to generate the security findings.

@@ -21,9 +21,9 @@ Within this folder the following files are also to be created:

 - `__init__.py` (empty) – Ensures Python recognizes this folder as a package.
 - `<new_service_name>_service.py` – Contains all the logic and API calls of the service.
- `<new_service_name>_client_.py` – Contains the initialization of the freshly created service's class so that the checks can use it.
+- `<new_service_name>_client.py` – Contains the initialization of the freshly created service's class so that the checks can use it.

-Once the files are create, you can check that the service has been created by running the following command: `uv run python prowler-cli.py <provider> --list-services | grep <new_service_name>`.
+Once the files are created, you can check that the service has been created by running the following command: `uv run python prowler-cli.py <provider> --list-services | grep <new_service_name>`.

 ## Service Structure and Initialisation

@@ -31,7 +31,7 @@ The Prowler's service structure is as outlined below. To initialise it, just imp

 ### Service Base Class

-All Prowler provider service should inherit from a common base class to avoid code duplication. This base class handles initialization and storage of functions and objects needed across services. The exact implementation depends on the provider's API requirements, but the following are the most common responsibilities:
+All Prowler provider services should inherit from a common base class to avoid code duplication. This base class handles initialization and storage of functions and objects needed across services. The exact implementation depends on the provider's API requirements, but the following are the most common responsibilities:

 - Initialize/store clients to interact with the provider's API.
 - Store the audit and fixer configuration.
@@ -16,7 +16,7 @@ prowler <provider>
 ![Prowler Execution](/images/short-display.png)

 <Note>
-Running the `prowler` command without options will uses environment variable credentials. Refer to the Authentication section of each provider for credential configuration details.
+Running the `prowler` command without options will use environment variable credentials. Refer to the Authentication section of each provider for credential configuration details.

 </Note>
 ## Verbose Output
@@ -178,9 +178,9 @@ The available versions of Prowler Local Server are the following:
 - `v4-latest`: in sync with `v4` branch (please note that it is not a stable version)
 - `v3-latest`: in sync with `v3` branch (please note that it is not a stable version)
 - `<x.y.z>` (release): you can find the releases [here](https://github.com/prowler-cloud/prowler/releases), those are stable releases.
- `stable`: this tag always point to the latest release.
- `v4-stable`: this tag always point to the latest release for v4.
- `v3-stable`: this tag always point to the latest release for v3.
+- `stable`: this tag always points to the latest release.
+- `v4-stable`: this tag always points to the latest release for v4.
+- `v3-stable`: this tag always points to the latest release for v3.

 The container images are available here:

@@ -234,9 +234,9 @@ The available versions of Prowler CLI are the following:
 - `v4-latest`: in sync with `v4` branch (please note that it is not a stable version)
 - `v3-latest`: in sync with `v3` branch (please note that it is not a stable version)
 - `<x.y.z>` (release): you can find the releases [here](https://github.com/prowler-cloud/prowler/releases), those are stable releases.
- `stable`: this tag always point to the latest release.
- `v4-stable`: this tag always point to the latest release for v4.
- `v3-stable`: this tag always point to the latest release for v3.
+- `stable`: this tag always points to the latest release.
+- `v4-stable`: this tag always points to the latest release for v4.
+- `v3-stable`: this tag always points to the latest release for v3.

 The container images are available here:

@@ -20,11 +20,11 @@ To get to the **Prowler Cloud** product listing in the AWS Marketplace, and clic

 After you have subscribed to the **Prowler Cloud** product, you will need to set up your **Prowler Cloud** account:

-1. Click the `Set up  your account` button:
+1. Click the `Set up your account` button:

    ![](/images/aws-marketplace/marketplace-message.png)

-2. You will be redirected to **Prowler Cloud Sign In** page. You can sign in with an exsiting account or sign up with a new account.:
+2. You will be redirected to **Prowler Cloud Sign In** page. You can sign in with an existing account or sign up with a new account:

    ![](/images/aws-marketplace/marketplace-sign-up.png)

@@ -4,7 +4,7 @@ title: "Overview"

 [Prowler Cloud](https://prowler.com) makes Cloud Security easy and enables your team to build trust in their deployed services and applications.

-Prowler Cloud Automates scanning single or multiple accounts and has all of the benefits of Prowler Open Source, plus hands-off continuous monitoring, auto-scaling workers for faster execution, integrations, personalized support options and out of the box social authentication.
+Prowler Cloud automates scanning single or multiple accounts and has all of the benefits of Prowler Open Source, plus hands-off continuous monitoring, auto-scaling workers for faster execution, integrations, personalized support options and out of the box social authentication.

 ![](/images/products/overview.png)

@@ -96,7 +96,7 @@ Lighthouse AI supports three providers:

 For detailed configuration instructions, see [Using Multiple LLM Providers with Lighthouse](/user-guide/tutorials/prowler-app-lighthouse-multi-llm).

-**2. Why some models don't appear in Lighthouse AI?**
+**2. Why don't some models appear in Lighthouse AI?**

 LLM providers offer different types of models. Not every model can be integrated with Lighthouse AI (for example, text-to-speech, vision, embedding, computer use, etc.).

@@ -168,7 +168,7 @@ A `.codex/config.toml` inside a project is loaded **only when the project is tru

 ### Tools Do Not Appear After Editing the Config

-Restart Codex. Configuration is read at startup. In the app, quit completely and reopen it, sometimes just clous the window is not enough.
+Restart Codex. Configuration is read at startup. In the app, quit completely and reopen it, sometimes just closing the window is not enough.

 ## Next Steps

@@ -36,7 +36,7 @@ This page allows for multiple functions:

 - Apply filters:

-  - Assesment Date
+  - Assessment Date
  - Account
  - Region
  - Severity
@@ -45,7 +45,7 @@ This page allows for multiple functions:
  - Status
  - Category

- See which files has been scanned to generate the dashboard by placing your mouse on the `?` icon:
+- See which files have been scanned to generate the dashboard by placing your mouse on the `?` icon:

  {" "}
  <img src="/images/cli/dashboard/dashboard-files-scanned.png" />
@@ -67,7 +67,7 @@ This page shows all the info related to the compliance selected. Multiple filter

 To add your own compliance to compliance page, add a file with the compliance name (using `_` instead of `.`) to the path `/dashboard/compliance`.

-In this file use the format present in the others compliance files to create the table. Example for CIS 2.0:
+In this file use the format present in the other compliance files to create the table. Example for CIS 2.0:

 ```python
 import warnings
@@ -37,5 +37,5 @@ To configure the Slack Integration, follow the next steps:
    ![Slack App Channel Integration](/images/cli/integrate-slack-app.png)

 4. Set the following environment variables that Prowler will read:
-    - `SLACK_API_TOKEN`: the *Slack App OAuth Token* that was previously get.
+    - `SLACK_API_TOKEN`: the *Slack App OAuth Token* that was previously obtained.
    - `SLACK_CHANNEL_NAME`: the name of your Slack Channel where Prowler will send the message.
@@ -2,7 +2,7 @@
 title: 'Logging'
 ---

-Prowler has a logging feature to be as transparent as possible, so that you can see every action that is being performed whilst the tool is being executing.
+Prowler has a logging feature to be as transparent as possible, so that you can see every action that is being performed whilst the tool is being executed.

 ## Set Log Level

@@ -318,7 +318,7 @@ The DynamoDB Table must have the following String keys:

 The Mutelist Table must have the following columns:

-  - Accounts (String): This field can contain either an Account ID or an `*` (which applies to all the accounts that use this table as an mutelist).
+  - Accounts (String): This field can contain either an Account ID or an `*` (which applies to all the accounts that use this table as a mutelist).

  - Checks (String): This field can contain either a Prowler Check Name or an `*` (which applies to all the scanned checks).

@@ -358,7 +358,7 @@ Make sure that the credentials that Prowler uses can invoke the Lambda Function:
        Resource: arn:aws:lambda:REGION:ACCOUNT_ID:function:FUNCTION_NAME
 ```

-The Lambda Function can then generate an Mutelist dynamically. Here is the code an example Python Lambda Function that generates an Mutelist:
+The Lambda Function can then generate a Mutelist dynamically. Here is the code of an example Python Lambda Function that generates a Mutelist:

 ```
 def handler(event, context):
@@ -135,7 +135,7 @@ Output will be stored in `C:\Users\YOUR-USER\Documents\output\`

 ## Combining the Output Files

-Guidance is provided for the CSV file format. From the ouput directory, execute either the following Bash or PowerShell script. The script will collect the output from the CSV files, only include the header from the first file, and then output the result as CombinedCSV.csv in the current working directory.
+Guidance is provided for the CSV file format. From the output directory, execute either the following Bash or PowerShell script. The script will collect the output from the CSV files, only include the header from the first file, and then output the result as CombinedCSV.csv in the current working directory.

 There is no logic implemented in terms of which CSV files it will combine. If you have additional CSV files from other actions, such as running a quick inventory, you will need to move that out of the current (or any nested) directory, or move the output you want to combine into its own folder and run the script from there.

@@ -18,7 +18,7 @@ Currently, it is only available for AWS provider.
 By default, it extracts resources from all the regions, you could use `-f`/`--filter-region` to specify the regions to execute the analysis.

 </Note>
- This feature specify both the number of resources for each service and for each resource type.
+- This feature specifies both the number of resources for each service and for each resource type.

 - Also, it creates by default a CSV and JSON to see detailed information about the resources extracted.

@@ -49,6 +49,6 @@ For testing or modifying Prowler's behavior, use the following steps to confirm
 * Run prowler with `--log-level DEBUG` and `--log-file debuglogs.txt`
 * Search for retry attempts using `grep -i 'Retry needed' debuglogs.txt`

-This approach follows the [AWS documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/retries.html#checking-retry-attempts-in-your-client-logs), which states that if a retry is performed, a message starting with "Retry needed” will be prompted.
+This approach follows the [AWS documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/retries.html#checking-retry-attempts-in-your-client-logs), which states that if a retry is performed, a message starting with "Retry needed" will be prompted.

 It is possible to determine the total number of calls made using `grep -i 'Sending http request' debuglogs.txt | wc -l`
@@ -16,7 +16,7 @@ To scan specific accounts one at a time:
 ACCOUNTS_LIST='11111111111 2222222222 333333333'
 ```

- Run Prowler with an IAM role that exists in all target accounts: (replace the `<role_name>` with to yours, that is to be consistent throughout all accounts):
+- Run Prowler with an IAM role that exists in all target accounts: (replace the `<role_name>` with yours, that is to be consistent throughout all accounts):

 ```
 ROLE_TO_ASSUME=<role_name>
@@ -35,7 +35,7 @@ Define the AWS accounts to be scanned with a variable:
 ACCOUNTS_LIST='11111111111 2222222222 333333333'
 ```

- Run Prowler with an IAM role that exists in all target accounts: (replace the `<role_name>` with to yours, that is to be consistent throughout all accounts). The following example executes scanning across three accounts in parallel:
+- Run Prowler with an IAM role that exists in all target accounts: (replace the `<role_name>` with yours, that is to be consistent throughout all accounts). The following example executes scanning across three accounts in parallel:

 ```
 ROLE_TO_ASSUME=<role_name>
@@ -78,7 +78,7 @@ aws securityhub enable-import-findings-for-product --region eu-west-1 --product-
 ```

 <Note>
-Specify the AWS region where you want to enable the integration. Ensure the region is correctly set within the ARN value. This command requires the`securityhub:securityhub:EnableImportFindingsForProduct` permission.
+Specify the AWS region where you want to enable the integration. Ensure the region is correctly set within the ARN value. This command requires the `securityhub:EnableImportFindingsForProduct` permission.

 </Note>
 ## Sending Findings to AWS Security Hub
@@ -100,7 +100,7 @@ prowler --security-hub --region eu-west-1
 <Note>
 It is recommended to send only fails to Security Hub and that is possible adding `--status FAIL` to the command. You can use, instead of the `--status FAIL` argument, the `--send-sh-only-fails` argument to save all the findings in the Prowler outputs but just to send FAIL findings to AWS Security Hub.

-Since Prowler perform checks to all regions by default you may need to filter by region when running Security Hub integration, as shown in the example above. Remember to enable Security Hub in the region or regions you need by calling `aws securityhub enable-security-hub --region <region>` and run Prowler with the option `-f/--region <region>` (if no region is used it will try to push findings in all regions hubs). Prowler will send findings to the Security Hub on the region where the scanned resource is located.
+Since Prowler performs checks to all regions by default you may need to filter by region when running Security Hub integration, as shown in the example above. Remember to enable Security Hub in the region or regions you need by calling `aws securityhub enable-security-hub --region <region>` and run Prowler with the option `-f/--region <region>` (if no region is used it will try to push findings in all regions hubs). Prowler will send findings to the Security Hub on the region where the scanned resource is located.

 To have updated findings in Security Hub you have to run Prowler periodically. Once a day or every certain amount of hours.

@@ -19,7 +19,7 @@ checks_v4_v3_to_v2_mapping = {
    "apigateway_restapi_public": "extra745",
    "apigateway_restapi_logging_enabled": "extra722",
    "apigateway_restapi_waf_acl_attached": "extra744",
-    “apigatewayv2_api_access_logging_enabled": "extra7156",
+    "apigatewayv2_api_access_logging_enabled": "extra7156",
    "apigatewayv2_api_authorizers_enabled": "extra7157",
    "appstream_fleet_default_internet_access_disabled": "extra7193",
    "appstream_fleet_maximum_session_duration": "extra7190",
@@ -145,7 +145,7 @@ The checks requiring this `ProwlerRole` can be found in this [section](/user-gui
    1. To create a new custom role, open a terminal and execute the following command:

    ```console
-    az role definition create --role-definition '{                                                                                                                   640ms  lun 16 dic 17:04:17 2024
+    az role definition create --role-definition '{
                        "Name": "ProwlerRole",
                        "IsCustom": true,
                        "Description": "Role used for checks that require read-only access to Azure resources and are not covered by the Reader role.",
@@ -551,7 +551,7 @@ Installing PowerShell is different depending on your OS:

  </Tab>
  <Tab title="Docker">
-    [Docker](https://learn.microsoft.com/es-es/powershell/scripting/install/powershell-in-docker?view=powershell-7.5#use-powershell-in-a-container): The following command download the latest stable versions of PowerShell:
+    [Docker](https://learn.microsoft.com/es-es/powershell/scripting/install/powershell-in-docker?view=powershell-7.5#use-powershell-in-a-container): The following command downloads the latest stable versions of PowerShell:

    ```console
    docker pull mcr.microsoft.com/dotnet/sdk:9.0
@@ -13,4 +13,4 @@ To learn more about how to install PowerShell and which versions are supported,
 ## Required Modules

 The necessary modules will not be installed automatically by Prowler. Nevertheless, if you want Prowler to install them for you, you can execute the provider with the flag `--init-modules`, which will run the script to install and import them.
-If you want to learn more about this process or you are running some issues with this, click [here](/user-guide/providers/microsoft365/authentication#required-powershell-modules).
+If you want to learn more about this process or you are running into some issues with this, click [here](/user-guide/providers/microsoft365/authentication#required-powershell-modules).
@@ -166,7 +166,7 @@ Mutelist:
            - "*"
          Resources:
            - "app-vnet-peering-*"
-          Description: "Mute App Function Vnet findings related with the reources pattern"
+          Description: "Mute App Function Vnet findings related with the resources pattern"
 ```

 #### Azure Resource Group Muting
@@ -69,7 +69,7 @@ To remove **another** user from your organization, use the [_Expel from organiza
 #### Inviting Users

 <Note>
-Please be aware that at this time, an email address can only be associated with a single Prowler account_.
+Please be aware that at this time, an email address can only be associated with a single Prowler account.

 </Note>
 Follow these steps to invite a user to your account:
@@ -142,7 +142,7 @@ To download these files, click the **Download** button. This button becomes avai

 <img src="/images/download_output.png" alt="Download output" width="700" />

-The `zip` file unpacks into a folder named like `prowler-output-<provider_id>-<timestamp>`, which includes all of the above outputs. In the example below, you can see the `.csv`, .`json`, and `.html` reports alongside a subfolder for detailed compliance checks.
+The `zip` file unpacks into a folder named like `prowler-output-<provider_id>-<timestamp>`, which includes all of the above outputs. In the example below, you can see the `.csv`, `.json`, and `.html` reports alongside a subfolder for detailed compliance checks.

 <img src="/images/output_folder.png" alt="Output folder" width="700" />

@@ -17,7 +17,7 @@ checks_v4_v3_to_v2_mapping = {
    "apigateway_restapi_public": "extra745",
    "apigateway_restapi_logging_enabled": "extra722",
    "apigateway_restapi_waf_acl_attached": "extra744",
-    “apigatewayv2_api_access_logging_enabled": "extra7156",
+    "apigatewayv2_api_access_logging_enabled": "extra7156",
    "apigatewayv2_api_authorizers_enabled": "extra7157",
    "appstream_fleet_default_internet_access_disabled": "extra7193",
    "appstream_fleet_maximum_session_duration": "extra7190",