[DOCS-10533] Apply Vale updates (#20014)

Author: buraizu

bitdefender/README.md

@@ -53,7 +53,7 @@ For more information, see the [API Key and Authentication Reference Document][3]
 ### Configure a webhook in Datadog
 1. In Datadog, navigate to the **Integrations** tab, and search for the Bitdefender integration.
 2. Click the **Bitdefender** integration. The integration window opens. On the **Configure** tab, select an existing API key, or create a new one.
-3. After selecting an API key, click **Add API key**, then click **Click Here to Copy URL**.
+3. After selecting an API key, click **Add API key**, then **Click Here to Copy URL**.
 4. Make a curl request. Use the template below, putting values into the following fields: 
     - **\<control_center_apis_access_url>**: The URL from the previous section
     - **\<bitdefender-encoded-api-key>**: Your encoded API key

snmp_f5/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-F5 Networks is an application delivery networking and security company. Collect health and performance metrics of your F5 devices, including including the Big IP and LTM platforms.
+F5 Networks is an application delivery networking and security company. Collect health and performance metrics of your F5 devices, including the Big IP and LTM platforms.
 
 ## Setup
 

tibco_ems/README.md

@@ -22,7 +22,7 @@ The TIBCO EMS check is included in the [Datadog Agent][2] package. No additional
 
 ##### Create your Tibco EMS command script
 
-The Tibco EMS integration utilizes the `tibemsadmin` CLI tool provided by Tibco EMS. To reduce the number of calls to the `$sys.admin` queue, Datadog uses a script to batch the queries made to Tibco. To collect your Tibco EMS metrics, pass the the script path and the absolute path of the `tibemsadmin` binary to the integration configuration.
+The Tibco EMS integration utilizes the `tibemsadmin` CLI tool provided by Tibco EMS. To reduce the number of calls to the `$sys.admin` queue, Datadog uses a script to batch the queries made to Tibco. To collect your Tibco EMS metrics, pass the script path and the absolute path of the `tibemsadmin` binary to the integration configuration.
 
 *Note*: The `dd-agent` user needs execute permissions on the `tibemsadmin` binary.
 1. Create a file named `show_commands` with the following contents:

trend_micro_vision_one_endpoint_security/README.md

@@ -46,12 +46,12 @@ Use out-of-the-box dashboards to gain detailed insights into system events, netw
 
 ### Connect your Trend Micro Vision One Endpoint Security Account to Datadog
 
-1. Add your API host, application ID, API key and select the time zone from the dropdown.
+1. Add your API host, application ID, and API key, and select the time zone from the dropdown.
    | Parameters     | Description                                                             |
    | -------------- | ----------------------------------------------------------------------- |
-   | API Host       | The API host of Trend Micro Vision One Endpoint Security console.       |
-   | Application ID | The application ID of Trend Micro Vision One Endpoint Security console. |
-   | API Key        | The API key of of Trend Micro Vision One Endpoint Security console.     |
+   | API Host       | The API host of the Trend Micro Vision One Endpoint Security console.       |
+   | Application ID | The application ID of the Trend Micro Vision One Endpoint Security console. |
+   | API Key        | The API key of the Trend Micro Vision One Endpoint Security console.     |
    | Time Zone      | The time zone of the Trend Micro Vision One console.                    |
 
 2. Click the **Save** button to save your settings.

vsphere/README.md

@@ -66,7 +66,7 @@ To enable property metrics, configure the following option:
 collect_property_metrics: true
 ```
 
-Property metrics are prefixed by the resource name. For example, host property metrics metrics are prefixed with `vsphere.host.*`, and VM property metrics are prefixed with `vsphere.vm.*`. View all the possible property metrics in the [metadata.csv][10].
+Property metrics are prefixed by the resource name. For example, host property metrics are prefixed with `vsphere.host.*`, and VM property metrics are prefixed with `vsphere.vm.*`. View all the possible property metrics in the [metadata.csv][10].
 
 
 ### Events