error fixed

Signed-off-by: Bonusree <[email protected]>

Author: Bonusree

docs/guides/elasticsearch/reconfigure_tls/es-tls.png

@@ -12,43 +12,43 @@ section_menu_id: guides
 
 > New to KubeDB? Please start [here](/docs/README.md).
 
-# Reconfiguring TLS of Kafka
+# Reconfiguring TLS of Elasticsearch
 
-This guide will give an overview on how KubeDB Ops-manager operator reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of `Kafka`.
+This guide will give an overview on how KubeDB Ops-manager operator reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of `Elasticsearch`.
 
 ## Before You Begin
 
 - You should be familiar with the following `KubeDB` concepts:
-- [Kafka](/docs/guides/kafka/concepts/kafka.md)
-- [KafkaOpsRequest](/docs/guides/kafka/concepts/kafkaopsrequest.md)
+- [Elasticsearch](/docs/guides/Elasticsearch/concepts/elasticsearch.md)
+- [ElasticsearchOpsRequest](/docs/guides/Elasticsearch/concepts/elasticsearch-ops-request.md)
 
-## How Reconfiguring Kafka TLS Configuration Process Works
+## How Reconfiguring Elasticsearch TLS Configuration Process Works
 
-The following diagram shows how KubeDB Ops-manager operator reconfigures TLS of a `Kafka`. Open the image in a new tab to see the enlarged version.
+The following diagram shows how KubeDB Ops-manager operator reconfigures TLS of a `Elasticsearch`. Open the image in a new tab to see the enlarged version.
 
 <figure align="center">
-      <img alt="Reconfiguring TLS process of Kafka" src="/docs/images/day-2-operation/kafka/kf-reconfigure-tls.svg">
-    <figcaption align="center">Fig: Reconfiguring TLS process of Kafka</figcaption>
+      <img alt="Reconfiguring TLS process of Elasticsearch" src="/docs/guides/elasticsearch/reconfigure_tls/es-tls.png">
+    <figcaption align="center">Fig: Reconfiguring TLS process of Elasticsearch</figcaption>
 </figure>
 
-The Reconfiguring Kafka TLS process consists of the following steps:
+The Reconfiguring Elasticsearch TLS process consists of the following steps:
 
-1. At first, a user creates a `Kafka` Custom Resource Object (CRO).
+1. At first, a user creates a `Elasticsearch` Custom Resource Object (CRO).
 
-2. `KubeDB` Provisioner  operator watches the `Kafka` CRO.
+2. `KubeDB` Provisioner  operator watches the `Elasticsearch` CRO.
 
-3. When the operator finds a `Kafka` CR, it creates required number of `PetSets` and related necessary stuff like secrets, services, etc.
+3. When the operator finds a `Elasticsearch` CR, it creates required number of `PetSets` and related necessary stuff like secrets, services, etc.
 
-4. Then, in order to reconfigure the TLS configuration of the `Kafka` database the user creates a `KafkaOpsRequest` CR with desired information.
+4. Then, in order to reconfigure the TLS configuration of the `Elasticsearch` database the user creates a `ElasticsearchOpsRequest` CR with desired information.
 
-5. `KubeDB` Ops-manager operator watches the `KafkaOpsRequest` CR.
+5. `KubeDB` Ops-manager operator watches the `ElasticsearchOpsRequest` CR.
 
-6. When it finds a `KafkaOpsRequest` CR, it pauses the `Kafka` object which is referred from the `KafkaOpsRequest`. So, the `KubeDB` Provisioner  operator doesn't perform any operations on the `Kafka` object during the reconfiguring TLS process.
+6. When it finds a `ElasticsearchOpsRequest` CR, it pauses the `Elasticsearch` object which is referred from the `ElasticsearchOpsRequest`. So, the `KubeDB` Provisioner  operator doesn't perform any operations on the `Elasticsearch` object during the reconfiguring TLS process.
 
 7. Then the `KubeDB` Ops-manager operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.
 
-8. Then the `KubeDB` Ops-manager operator will restart all the Pods of the database so that they restart with the new TLS configuration defined in the `KafkaOpsRequest` CR.
+8. Then the `KubeDB` Ops-manager operator will restart all the Pods of the database so that they restart with the new TLS configuration defined in the `ElasticsearchOpsRequest` CR.
 
-9. After the successful reconfiguring of the `Kafka` TLS, the `KubeDB` Ops-manager operator resumes the `Kafka` object so that the `KubeDB` Provisioner  operator resumes its usual operations.
+9. After the successful reconfiguring of the `Elasticsearch` TLS, the `KubeDB` Ops-manager operator resumes the `Elasticsearch` object so that the `KubeDB` Provisioner  operator resumes its usual operations.
 
-In the next docs, we are going to show a step by step guide on reconfiguring TLS configuration of a Kafka database using `KafkaOpsRequest` CRD.
+In the next docs, we are going to show a step by step guide on reconfiguring TLS configuration of a Elasticsearch database using `ElasticsearchOpsRequest` CRD.

docs/guides/elasticsearch/reconfigure_tls/overview.md

@@ -22,7 +22,8 @@ This guide will demonstrate how to restart an Elasticsearch cluster using an Ops
 
 ## Before You Begin
 
-- You need a running Kubernetes cluster and a properly configured `kubectl` command-line tool. If you don’t have a cluster, you can create one using [kind](https://kind.sigs.k8s.io/docs/user/quick-start/).
+- You need a running Kubernetes cluster and a properly configured `kubectl` command-line tool. If you don’t
+have a cluster, you can create one using [kind](https://kind.sigs.k8s.io/docs/user/quick-start/).
 
 - Install the KubeDB CLI on your workstation and the KubeDB operator in your cluster by following the [installation steps](/docs/setup/README.md).
 

docs/guides/elasticsearch/restart/index.md

@@ -405,7 +405,9 @@ $ kubectl get elasticsearch -n demo es-hscale-topology -o json | jq '.spec.topol
 $ kubectl get elasticsearch -n demo es-hscale-topology -o json | jq '.spec.topology.ingest.replicas'
 2
 ```
-**Only ingest nodes after scaling down:**
+From all the above outputs we can see that the replicas of the Topology cluster is `2`. That means we have successfully scaled down the replicas of the Elasticsearch Topology cluster.
+
+Only one node can be scaling down at a time. So we are scaling down the `ingest` node.
 ```bash
 apiVersion: ops.kubedb.com/v1alpha1
 kind: ElasticsearchOpsRequest
@@ -420,7 +422,6 @@ spec:
     topology:
       ingest: 2
 ```
-From all the above outputs we can see that the replicas of the Topology cluster is `2`. That means we have successfully scaled down the replicas of the Elasticsearch Topology cluster.
 
 
 
@@ -589,8 +590,7 @@ $ kubectl get elasticsearch -n demo es-hscale-topology -o json | jq '.spec.topol
 
 From all the above outputs we can see that the brokers of the Topology Elasticsearch is `3`. That means we have successfully scaled up the replicas of the Elasticsearch Topology cluster.
 
-
-**Only ingest nodes after scaling up:**
+Only one node can be scaling up at a time. So we are scaling up the `ingest` node.
 ```yaml
 apiVersion: ops.kubedb.com/v1alpha1
 kind: ElasticsearchOpsRequest

docs/guides/elasticsearch/scaling/horizontal/topology.md

@@ -689,6 +689,4 @@ kubectl delete ns demo
 - Detail concepts of [Elasticsearch object](/docs/guides/Elasticsearch/concepts/Elasticsearch.md).
 - Different Elasticsearch topology clustering modes [here](/docs/guides/Elasticsearch/clustering/_index.md).
 - Monitor your Elasticsearch database with KubeDB using [out-of-the-box Prometheus operator](/docs/guides/Elasticsearch/monitoring/using-prometheus-operator.md).
-
-[//]: # (- Monitor your Elasticsearch database with KubeDB using [out-of-the-box builtin-Prometheus](/docs/guides/Elasticsearch/monitoring/using-builtin-prometheus.md).)
 - Want to hack on KubeDB? Check our [contribution guidelines](/docs/CONTRIBUTING.md).

docs/guides/elasticsearch/scaling/vertical/topology.md

@@ -38,7 +38,7 @@ namespace/demo created
 
 ## Prepare Elasticsearch
 
-Now, we are going to deploy a `Elasticsearch` replicaset database with version `xpack-8.11.1`.
+Now, we are going to deploy a `Elasticsearch` replicaset database with version `xpack-9.1.3`.
 
 ### Deploy Elasticsearch
 
@@ -110,7 +110,7 @@ Here,
 
 - `spec.databaseRef.name` specifies that we are performing operation on `es-demo` Elasticsearch.
 - `spec.type` specifies that we are going to perform `UpdateVersion` on our database.
-- `spec.updateVersion.targetVersion` specifies the expected version of the database `xpack-8.16.4`.
+- `spec.updateVersion.targetVersion` specifies the expected version of the database `xpack-9.1.4`.
 
 > **Note:** If you want to update combined Elasticsearch, you just refer to the `Elasticsearch` combined object name in `spec.databaseRef.name`. To create a combined Elasticsearch, you can refer to the [Elasticsearch Combined](/docs/guides/elasticsearch/clustering/combined-cluster/index.md) guide.
 

docs/guides/elasticsearch/update-version/elasticsearch.md

@@ -59,7 +59,7 @@ Now, we are going to deploy a `Elasticsearch` combined cluster with version `xpa
 
 ### Deploy Elasticsearch
 
-In this section, we are going to deploy a Elasticsearch topology cluster for broker and controller with 1GB volume. Then, in the next section we will expand its volume to 2GB using `ElasticsearchOpsRequest` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create,
+In this section, we are going to deploy a Elasticsearch topology cluster for broker and controller with 1Gi volume. Then, in the next section we will expand its volume to 2Gi using `ElasticsearchOpsRequest` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create,
 
 ```yaml
 apiVersion: kubedb.com/v1
@@ -140,7 +140,7 @@ pvc-bd4b7d5a-8494-4ee2-a25c-697a6f23cb79   1Gi        RWO            Delete
 pvc-c9057b3b-4412-467f-8ae5-f6414e0059c3   1Gi        RWO            Delete           Bound    demo/data-es-cluster-master-2   standard     <unset>                          22h
 ```
 
-You can see the petsets have 1GB storage, and the capacity of all the persistent volumes are also 1GB.
+You can see the petsets have 1Gi storage, and the capacity of all the persistent volumes are also 1Gi.
 
 We are now ready to apply the `ElasticsearchOpsRequest` CR to expand the volume of this database.