Minor fixes

Author: pavangudiwada

docs/configuration/holmesgpt/index.rst

@@ -362,7 +362,7 @@ Builtin toolsets
 
 Built-in toolsets cover essential areas like pod status inspection, node health analysis,
 application diagnostics, and resource utilization monitoring. These toolsets include access to
-Kubernetes events and logs, AWS, Grafana, Opensearch, etc. See the full list :doc:`here <builtin_toolsets>`.
+Kubernetes events and logs, AWS, Grafana, OpenSearch, etc. See the full list :doc:`here <builtin_toolsets>`.
 
 Custom toolsets
 ----------------

docs/configuration/holmesgpt/toolsets/coralogix_logs.rst

@@ -3,7 +3,7 @@
 Coralogix logs
 ==============
 
-By enabling this toolset, HolmesGPT will fetch pods logs from `Coralogix <https://coralogix.com/>`_.
+By enabling this toolset, HolmesGPT will fetch pod logs from `Coralogix <https://coralogix.com/>`_.
 
 You **should** enable this toolset to replace the default :ref:`kubernetes/logs <toolset_kubernetes_logs>`
 toolset if all your kubernetes pod logs are consolidated inside Coralogix. It will make it easier for HolmesGPT

docs/configuration/holmesgpt/toolsets/grafanaloki.rst

@@ -3,7 +3,7 @@
 Loki
 ====
 
-By enabling this toolset, HolmesGPT will fetch pods logs from `Loki <https://grafana.com/oss/loki/>`_.
+By enabling this toolset, HolmesGPT will fetch pod logs from `Loki <https://grafana.com/oss/loki/>`_.
 Loki can be accessed directly or by proxying through a `Grafana <https://grafana.com/oss/grafana/>`_ instance.
 
 You **should** enable this toolset to replace the default :ref:`kubernetes/logs <toolset_kubernetes_logs>`

docs/configuration/holmesgpt/toolsets/opensearch_logs.rst

@@ -1,12 +1,12 @@
 .. _toolset_opensearch_logs:
 
-Opensearch logs
+OpenSearch logs
 ==============
 
-By enabling this toolset, HolmesGPT will fetch pod logs from `Opensearch <https://opensearch.org/>`_.
+By enabling this toolset, HolmesGPT will fetch pod logs from `OpenSearch <https://opensearch.org/>`_.
 
 You **should** enable this toolset to replace the default :ref:`kubernetes/logs <toolset_kubernetes_logs>`
-toolset if all your kubernetes pod logs are consolidated inside Opensearch/Elastic. It will make it easier for HolmesGPT
+toolset if all your kubernetes pod logs are consolidated inside OpenSearch/Elastic. It will make it easier for HolmesGPT
 to fetch incident logs, including the ability to precisely consult past logs.
 
 

docs/configuration/holmesgpt/toolsets/opensearch_status.rst

@@ -1,4 +1,4 @@
-Opensearch status
+OpenSearch status
 =================
 
 By enabling this toolset, HolmesGPT will be able to access cluster metadata information
@@ -8,11 +8,11 @@ with one or more opensearch clusters.
 Configuration
 -------------
 
-The configuration for Opensearch is passed through to the underlying
+The configuration for OpenSearch is passed through to the underlying
 `opensearch-py library <https://github.com/opensearch-project/opensearch-py>`_. Consult this
 library's `user guide <https://github.com/opensearch-project/opensearch-py/blob/main/USER_GUIDE.md>`_ or
 `reference documentation <https://opensearch-project.github.io/opensearch-py/api-ref/clients/opensearch_client.html>`_
-for configuring the connection to Opensearch, including how to authenticate this toolset to an opensearch cluster.
+for configuring the connection to OpenSearch, including how to authenticate this toolset to an opensearch cluster.
 
 .. code-block:: yaml
 
@@ -35,7 +35,7 @@ for configuring the connection to Opensearch, including how to authenticate this
                             username: <basic auth username>
                             password: <basic auth password>
 
-Here is an example of an insecure Opensearch configuration for local development using a bearer token:
+Here is an example of an insecure OpenSearch configuration for local development using a bearer token:
 
 .. code-block:: yaml