Apply suggestions from code review

Co-authored-by: Mike Birnstiehl <[email protected]>

Author: emilioalvap

reference/fleet/elastic-agent-container.md

@@ -69,9 +69,9 @@ docker pull docker.elastic.co/elastic-agent/elastic-agent-wolfi:{{version.stack}
 
 ### Complete flavor
 
-In case you need to run {{agent}} as a Synthetic Private Location and you'll use only Lightweight monitors, you can use the `elastic-agent` (and the `wolfi` variant).
+To run {{agent}} as a Synthetic Private Location using only lightweight monitors, use the `elastic-agent` (and the `wolfi` variant).
 
- In case you need to run {{agent}} as a Synthetic Private Location and you'll use both Lightweight monitors and Synthetics Browser tests, run the docker pull command to fetch the `elastic-agent-complete` image:
+To run {{agent}} as a Synthetic Private Location using both lightweight monitors and Synthetics Browser tests, run the following docker pull command to fetch the `elastic-agent-complete` image:
 
 ```terminal subs=true
 docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}}

solutions/observability/synthetics/migrate-from-elastic-synthetics-integration.md

@@ -84,14 +84,14 @@ Find more details in [Use the {{synthetics-app}}](/solutions/observability/synth
 
 ## Where monitors run [synthetics-migrate-integration-location]
 
-If you want to continue hosting on your infrastructure, you will need to create a {{private-location}} before creating monitors. If you already have an {{agent}} running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}.
+If you want to continue hosting on your infrastructure, create a {{private-location}} before creating monitors. If you already have an {{agent}} running using `elastic-agent` or any of its variants, you can [add it as a new {{private-location}}](/solutions/observability/synthetics/monitor-resources-on-private-networks.md#synthetics-private-location-add) in the {{synthetics-app}}.
 
 ::::{note}
-Only the `elastic-agent-complete` image (and its `wolfi` variant) allows to run Synthetic Browser tests.
+Only the `elastic-agent-complete` image (and its `wolfi` variant) allows you to run Synthetic Browser tests.
 
 ::::
 
-To create a new {{private-location}} from scratch, follow all instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md).
+To create a new {{private-location}} from scratch, follow the instructions in [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md).
 
 Alternatively, you can start hosting on Elastic’s global managed infrastructure. With Elastic’s global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you.
 

solutions/observability/synthetics/monitor-resources-on-private-networks.md

@@ -58,7 +58,7 @@ After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your
 
 Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. Additional installation methods can be found on the [{{agent}} installation guide](/reference/fleet/install-elastic-agents.md). 
 ::::{important}
-For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants in a containerized environment. The standard {{agent}} variant only supports TCP, ICMP and HTTP monitors.
+For running browser monitors on {{private-location}}s, you *must* use one of the `elastic-agent-complete` Docker image variants in a containerized environment. The standard {{agent}} variant only supports TCP, ICMP, and HTTP monitors.
 
 ::::
 

solutions/observability/synthetics/support-matrix.md

@@ -43,8 +43,8 @@ There are various components that make up the Synthetics solution, which are sup
 
     * Shipped as multiple `elastic-agent` variants:
 
-        * `elastic-agent-complete`, exclusively provided as a Docker image which includes all dependencies required to run browser, TCP, HTTP and ICMP monitors.
-        * `elastic-agent` which only supports TCP, HTTP and ICMP monitors. 
+        * `elastic-agent-complete`, exclusively provided as a Docker image which includes all dependencies required to run browser, TCP, HTTP, and ICMP monitors.
+        * `elastic-agent` which only supports TCP, HTTP, and ICMP monitors. 
 
     * Must have a direct connection to {{es}}