Vale suggestions

wajihaparvez · wajihaparvez · commit 57fe4d573284 · 2025-11-27T15:50:23.000-05:00
diff --git a/deploy-manage/monitor/autoops.md b/deploy-manage/monitor/autoops.md
@@ -50,7 +50,7 @@ Depending on your deployment type, AutoOps has been rolled out across various [r
 :::{include} /deploy-manage/monitor/_snippets/autoops-availability.md
 :::
 
-AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
+AutoOps is currently not available for air-gapped environments because it's a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
 
 ## How AutoOps is licensed
 
diff --git a/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-firewalls.md b/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-firewalls.md
@@ -53,7 +53,7 @@ curl -XGET -i $AUTOOPS_ES_URL \
 
 :::::
 
-The command should return a response similar to:
+The command returns a response similar to:
 
 ```json
 {
@@ -75,21 +75,21 @@ The command should return a response similar to:
 }
 ```
 
-If you do not receive a similar response, your system will return an error indicating one or more reasons for failure as outlined in the following table. Use the corresponding proposed solution to fix the issue.
+If you did not receive a similar response, your system returns an error indicating one or more reasons for failure as outlined in the following table. Use the corresponding proposed solution to fix the issue.
 
 | Reason for failure | Proposed solution |
 | :--- | :--- |
-| The {{es}} endpoint URL you specified is incorrect/not reachable | - Make sure you are using `http` or `https` correctly. <br> - Make sure you are providing the correct port. The default port is **9200**. <br> - If you have verified that the URL is correct, your network team may need to open the firewall to allow-list this URL. |
-| Your API key is incorrect | - Recheck for typos. <br> - If your cluster is on versions 9.1.0 through 9.1.3, ensure that you have the base64-decoded version of the key by running the following command: <br><br> `echo $AUTOOPS_ES_API_KEY | base64 -d` <br><br> If your key has a colon (:), it is not base64 encoded. If your key has an equal sign (=), it is base64 coded. <br> For versions 9.1.4 and above, both formats will work.|
-| Your username and/or password are incorrect | - Recheck for typos. <br> - Ensure that your provided user has the [necessary privileges](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#configure-agent). We do not recommend providing a privileged superuser like `elastic` for this purpose.|
+| The {{es}} endpoint URL you specified is incorrect/not reachable | - Make sure you are using `http` or `https` correctly. <br> - Make sure you are providing the correct port. The default port is **9200**. <br> - If you have verified that the URL is correct, your network team might need to open the firewall to allow-list this URL. |
+| Your API key is incorrect | - Recheck for typos. <br> - If your cluster is on versions 9.1.0 through 9.1.3, ensure that you have the base64-decoded version of the key by running the following command: <br><br> `echo $AUTOOPS_ES_API_KEY | base64 -d` <br><br> If your key has a colon (:), it is not base64 encoded. If your key has an equal sign (=), it is base64 coded. <br> For versions 9.1.4 and above, both formats work.|
+| Your username or password is incorrect | - Recheck for typos. <br> - Ensure that your provided user has the [necessary privileges](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#configure-agent). We do not recommend providing a privileged superuser like `elastic` for this purpose.|
 | You are providing both the API key and username/password | Choose one type of authentication only. |
-| A proxy is blocking communication with your {{es}} cluster | You may have to configure `NO_PROXY`. |
+| A proxy is blocking communication with your {{es}} cluster | You might have to configure `NO_PROXY`. |
 | You are using a custom SSL/TLS configuration with {{es}} | Disable SSL/TLS verification so that your system trusts all certificates. We do not recommend disabling verification in production environments. <br><br> If you are using API key authentication, run the following command: <br><br>`curl -XGET --insecure -i $AUTOOPS_ES_URL \ -H "Authorization: ApiKey $AUTOOPS_ES_API_KEY"`. <br><br> If you are using username/password authentication, run the following command: <br><br> `curl -XGET --insecure -i $AUTOOPS_ES_URL \ -u $AUTOOPS_ES_USERNAME` <br><br> If the issue is resolved, you need to configure your custom SSL/TLS settings with {{agent}}. If the issue persists, contact [Elastic support](https://support.elastic.co/).| 
 | You are connecting a local development cluster using Docker without specifying `--network host` | - Make sure you are following all the steps to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md#connect-your-local-development-cluster-to-autoops). <br> - In the [Install agent](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#install-agent) step, make sure you are replacing `docker run -d \` with `docker run -d --network host \`. |
 
 ## 2. Test your cluster's registration with {{ecloud}} 
 
-If there is an issue with the second component, the agent will stop working and your logs might look like: 
+If there is an issue with the second component, the agent stops working and your logs might look like: 
 
 ```sh
 ... failed to register Cloud Connected Mode: ... Post \"https://api.elastic-cloud.com/api/v1/cloud-connected/clusters\": ...
@@ -115,18 +115,18 @@ If you do not receive a similar response, configure your HTTP proxy to allow it
       POST https://api.elastic-cloud.com/api/v1/cloud-connected/clusters
 ```
 :::{note}
-If you are using Docker, you may need to complete this configuration directly via the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
+If you are using Docker, you might need to complete this configuration directly using the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
 :::
 
 ## 3. Test if {{agent}} is able to send metrics
 
-If there is an issue with the third component, the agent will attempt to establish the connection and your logs might look like: 
+If there is an issue with the third component, the agent attempts to establish the connection and your logs might look like: 
     
 ```sh
 ... Exporting failed. Dropping data. ... no more retries left: failed to make an HTTP request: Post \"https://otel-collector.auto-ops.eu-west-1.aws.cloud.elastic.co:4318/v1/logs\": ...
 ```
     
-To test if your organization is not allowing the agent to send metrics from your cluster to {{ecloud}}, run the following command. We will use AWS eu-west-1 as the CSP region, but you should replace it with your chosen CSP region before running the command.
+To test if your organization is not allowing the agent to send metrics from your cluster to {{ecloud}}, run the following command. The command uses AWS eu-west-1 as the CSP (cloud service provider) region, but you should replace it with your chosen CSP region before running the command.
 
 ```json
 curl -XPOST -i \
@@ -146,5 +146,5 @@ If you do not receive a similar response, configure your HTTP proxy to allow it
   POST https://otel-collector.auto-ops.${REGION}.${CSP}.cloud.elastic.co:4318/v1/logs
 ```
 :::{note}
-If you are using Docker, you may need to complete this configuration directly via the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
+If you are using Docker, you might need to complete this configuration directly using the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
 :::
