Merge branch 'docs' of github.com:stackabletech/opensearch-operator into docs

Author: siegfriedweber

docs/modules/opensearch/pages/getting_started/first_steps.adoc

@@ -1,6 +1,6 @@
 = First steps
 
-Once you have followed the steps in  xref:getting_started/installation.adoc[] for the operator and its dependencies, you will now go through the steps to set up and connect to a OpenSearch instance.
+Once you have followed the steps in  xref:getting_started/installation.adoc[] for the operator and its dependencies, you will now go through the steps to set up and connect to an OpenSearch instance.
 
 == Security plugin configuration
 

docs/modules/opensearch/pages/getting_started/index.adoc

@@ -1,7 +1,7 @@
 = Getting started
 
 This guide helps you get started with OpenSearch using the Stackable Operator.
-It covers the installation of the operator and its dependencies, setting up your first OpenSearch instance, connecting to it, and ingest and search for data.
+It covers the installation of the operator and its dependencies, setting up your first OpenSearch instance, connecting to it, and ingesting and searching for data.
 
 == Prerequisites
 

docs/modules/opensearch/pages/usage-guide/configuration-environment-overrides.adoc

@@ -37,7 +37,7 @@ nodes:
 
 All override property values must be strings.
 They are added unchanged to the configuration file.
-So care must be taken to produce a valid configuration.
+Care must be taken to produce a valid configuration.
 
 For a list of configuration options, we refer to the
 https://docs.opensearch.org/docs/latest/install-and-configure/configuring-opensearch/index/[Configuring OpenSearch] section in the OpenSearch documentation.

docs/modules/opensearch/pages/usage-guide/storage-resource-configuration.adoc

@@ -19,7 +19,7 @@ nodes:
 
 In the example above, all OpenSearch nodes in the data role group store data (the location of the property `path.data`) on a `50Gi` volume.
 
-If nothing is configured in the custom resource for a certain role group, then by default each Pod has a `8Gi` large local volume mount for the data location.
+If nothing is configured in the custom resource for a certain role group, then by default each Pod has an `8Gi` large local volume mount for the data location.
 
 On role groups with only the `cluster_manager` node role, you probably want to decrease this value, but increase it on role groups with the `data` node role.