DOCS-2530 Lint Integrations section (part 2) (#10778)

Author: ruthnaebeck

cilium/README.md

@@ -103,7 +103,7 @@ For containerized environments, see the [Autodiscovery Integration Templates][2]
 {{< /site-region >}}
 partial -->
 
-Collecting logs is disabled by default in the Datadog Agent. To enable it, see [Kubernetes log collection documentation][7].
+Collecting logs is disabled by default in the Datadog Agent. To enable it, see [Kubernetes Log Collection][7].
 
 | Parameter      | Value                                     |
 |----------------|-------------------------------------------|

citrix_hypervisor/README.md

@@ -14,7 +14,7 @@ The Citrix Hypervisor check is included in the [Datadog Agent][3] package.
 No additional installation is needed on your server.  
 The recommended way to monitor Citrix hypervisors is to install one Datadog Agent on each hypervisor.
 
-#### Datadog User
+#### Datadog user
 
 The Citrix Hypervisor integration requires a user with at least [`read-only`][4] access to monitor the service.
 

clickhouse/README.md

@@ -78,7 +78,7 @@ For containerized environments, see the [Autodiscovery Integration Templates][2]
 {{< /site-region >}}
 partial -->
 
-Collecting logs is disabled by default in the Datadog Agent. To enable it, see [Kubernetes log collection documentation][6].
+Collecting logs is disabled by default in the Datadog Agent. To enable it, see [Kubernetes log collection][6].
 
 | Parameter      | Value                                     |
 |----------------|-------------------------------------------|

cloud_foundry_api/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-This check queries the [Cloud Foundry API][1] to collect audit events and send them to Datadog via the agent.
+This check queries the [Cloud Foundry API][1] to collect audit events and send them to Datadog through the Agent.
 
 ## Setup
 

cockroachdb/README.md

@@ -78,7 +78,7 @@ For containerized environments, see the [Autodiscovery Integration Templates][6]
 {{< /site-region >}}
 partial -->
 
-Collecting logs is disabled by default in the Datadog Agent. To enable it, see the [Docker log collection documentation][7].
+Collecting logs is disabled by default in the Datadog Agent. To enable it, see the [Docker Log Collection][7].
 
 Then, set [log integrations][7] as Docker labels:
 

consul/README.md

@@ -11,7 +11,7 @@ The Datadog Agent collects many metrics from Consul nodes, including those for:
 - Node health - for a given node, how many of its services are up, passing, warning, critical?
 - Network coordinates - inter- and intra-datacenter latencies
 
-The _Consul_ Agent can provide further metrics via DogStatsD. These metrics are more related to the internal health of Consul itself, not to services which depend on Consul. There are metrics for:
+The _Consul_ Agent can provide further metrics with DogStatsD. These metrics are more related to the internal health of Consul itself, not to services which depend on Consul. There are metrics for:
 
 - Serf events and member flaps
 - The Raft protocol
@@ -186,7 +186,7 @@ partial -->
 
 _Available for Agent versions >6.0_
 
-Collecting logs is disabled by default in the Datadog Agent. To enable it, see the [Kubernetes log collection documentation][10].
+Collecting logs is disabled by default in the Datadog Agent. To enable it, see [Kubernetes Log Collection][10].
 
 | Parameter      | Value                                               |
 | -------------- | --------------------------------------------------- |
@@ -200,7 +200,7 @@ Collecting logs is disabled by default in the Datadog Agent. To enable it, see t
 
 [Run the Agent's status subcommand][11] and look for `consul` under the Checks section.
 
-**Note**: If your Consul nodes have debug logging enabled, you'll see the Datadog Agent's regular polling in the Consul log:
+**Note**: If your Consul nodes have debug logging enabled, the Datadog Agent's regular polling shows in the Consul log:
 
 ```text
 2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/status/leader (59.344us) from=127.0.0.1:53768

consul_connect/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-Monitor your [Consul Connect][1] Envoy sidecar proxies with the [Datadog Envoy Integration][2]. The Consul Connect integration currently only supports [Consul Connect configured with Envoy][3]. 
+Monitor your [Consul Connect][1] Envoy sidecar proxies with the [Datadog Envoy Integration][2]. The Consul Connect integration only supports [Consul Connect configured with Envoy][3]. 
 
 ## Setup
 
@@ -21,7 +21,7 @@ Follow the instructions below to configure this check for an Agent running on a
 To configure this check for an Agent running on a host:
 
 ##### Metric collection
-1. In Consul Connect, enable the config option [`-admin-bind`][5] to configure the port where the Envoy Admin API will be exposed.
+1. In Consul Connect, enable the config option [`-admin-bind`][5] to configure the port where the Envoy Admin API is exposed.
 
 2. Enable the [Envoy integration][6] to configure metric collection.
 

container/README.md

@@ -4,8 +4,7 @@
 
 This check reports a set of metrics about any running containers, regardless of the runtime used to start them.
 
-**NOTE**: The `container` check is different from the `containerd` check. The `container` checks will report standardized metrics for all containers found on the system,
-regardless of the container runtime.
+**NOTE**: The `container` check is different from the `containerd` check. The `container` checks report standardized metrics for all containers found on the system, regardless of the container runtime.
 The `containerd` is dedicated to `containerd` runtime and publishes metrics in the `containerd.*` namespace.
 
 ## Setup
@@ -17,11 +16,11 @@ Configuring access to supported container runtimes (Docker, containerd) may be r
 
 #### Installation on containers
 
-The `container` check requires some folders to be mounted to allow for automatic activation. This is handled by our official Helm Chart, the Datadog Operator, and as documented set ups for Kubernetes, Docker, ECS, and ECS Fargate.
+The `container` check requires some folders to be mounted to allow for automatic activation. This is handled by the official Helm Chart, the Datadog Operator, and as documented set ups for Kubernetes, Docker, ECS, and ECS Fargate.
 
 ### Configuration
 
-Currently, the `container` check does not expose any specific configuration settings. To customize common fields or to force the activation of the `container` check, follow these steps:
+The `container` check does not expose any specific configuration settings. To customize common fields or to force the activation of the `container` check, follow these steps:
 
 1. Create the `container.d/conf.yaml` file in the `conf.d/` folder at the root of your Agent's configuration directory.