docs: fix typos and grammar (#12278)

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>

docs/user-guide/cli/tutorials/dashboard.mdx

@@ -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

docs/user-guide/cli/tutorials/integrations.mdx

@@ -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.

docs/user-guide/cli/tutorials/logging.mdx

@@ -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
 

docs/user-guide/cli/tutorials/mutelist.mdx

@@ -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):

docs/user-guide/cli/tutorials/parallel-execution.mdx

@@ -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.
 

docs/user-guide/cli/tutorials/quick-inventory.mdx

@@ -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.