link fix

Bonusree · Bonusree · commit 7b7464dda709 · 2025-12-10T15:42:54.000+06:00
Signed-off-by: Bonusree &lt;bonusree@appscode.com&gt;
diff --git a/docs/guides/elasticsearch/reconfigure_tls/elasticsearch.md b/docs/guides/elasticsearch/reconfigure_tls/elasticsearch.md
@@ -177,7 +177,7 @@ Here,
 - `spec.databaseRef.name` specifies that we are performing reconfigure TLS operation on `es-demo` cluster.
 - `spec.type` specifies that we are performing `ReconfigureTLS` on Elasticsearch.
 - `spec.tls.issuerRef` specifies the issuer name, kind and api group.
-- `spec.tls.certificates` specifies the certificates. You can learn more about this field from [here](/docs/guides/elasticsearch/concepts/Elasticsearch.md#spectls).
+- `spec.tls.certificates` specifies the certificates. You can learn more about this field from [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 Let's create the `ElasticsearchOpsRequest` CR we have shown above,
 
@@ -1007,7 +1007,7 @@ kubectl delete ns demo
 
 ## Next Steps
 
-- Detail concepts of [Elasticsearch object](/docs/guides/elasticsearch/concepts/elasticsearch.md).
+- Detail concepts of [Elasticsearch object](/docs/guides/elasticsearch/concepts/elasticsearch/index.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).
 - Want to hack on KubeDB? Check our [contribution guidelines](/docs/CONTRIBUTING.md).
diff --git a/docs/guides/elasticsearch/reconfigure_tls/overview.md b/docs/guides/elasticsearch/reconfigure_tls/overview.md
@@ -19,8 +19,8 @@ This guide will give an overview on how KubeDB Ops-manager operator reconfigures
 ## Before You Begin
 
 - You should be familiar with the following `KubeDB` concepts:
-- [Elasticsearch](/docs/guides/Elasticsearch/concepts/elasticsearch.md)
-- [ElasticsearchOpsRequest](/docs/guides/Elasticsearch/concepts/elasticsearch-ops-request.md)
+- [Elasticsearch](/docs/guides/elasticsearch/concepts/elasticsearch/index.md)
+- [ElasticsearchOpsRequest](/docs/guides/elasticsearch/concepts/elasticsearch-ops-request.md)
 
 ## How Reconfiguring Elasticsearch TLS Configuration Process Works
 
diff --git a/docs/guides/elasticsearch/scaling/horizontal/topology.md b/docs/guides/elasticsearch/scaling/horizontal/topology.md
@@ -24,7 +24,7 @@ This guide will show you how to use `KubeDB` Ops-manager operator to scale the E
 
 - You should be familiar with the following `KubeDB` concepts:
     - [Elasticsearch](/docs/guides/elasticsearch/concepts/elasticsearch/index.md)
-    - [Topology](/docs/guides/elasticsearch/clustering/topology-cluster/index.md)
+    - [Topology](/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md)
     - [ElasticsearchOpsRequest](/docs/guides/elasticsearch/concepts/elasticsearch-ops-request/index.md)
     - [Horizontal Scaling Overview](/docs/guides/elasticsearch/scaling/horizontal/overview.md)
 
diff --git a/docs/guides/elasticsearch/scaling/vertical/overview.md b/docs/guides/elasticsearch/scaling/vertical/overview.md
@@ -27,7 +27,7 @@ This guide will give an overview on how KubeDB Ops-manager operator updates the
 The following diagram shows how KubeDB Ops-manager operator updates the resources of the `Elasticsearch`. Open the image in a new tab to see the enlarged version.
 
 <figure align="center">
-      <img alt="Vertical scaling process of Elasticsearch" src="/docs/images/elasticsearch/es-vertical-scaling.jpg">
+      <img alt="Vertical scaling process of Elasticsearch" src="/docs/images/elasticsearch/es-vertical-scaling.png">
     <figcaption align="center">Fig: Vertical scaling process of Elasticsearch</figcaption>
 </figure>
 
diff --git a/docs/guides/elasticsearch/scaling/vertical/topology.md b/docs/guides/elasticsearch/scaling/vertical/topology.md
@@ -23,10 +23,10 @@ This guide will show you how to use `KubeDB` Ops-manager operator to update the
 - Install `KubeDB` Provisioner and Ops-manager operator in your cluster following the steps [here](/docs/setup/README.md).
 
 - You should be familiar with the following `KubeDB` concepts:
-    - [Elasticsearch](/docs/guides/Elasticsearch/concepts/Elasticsearch.md)
-    - [Topology](/docs/guides/Elasticsearch/clustering/topology-cluster/index.md)
-    - [ElasticsearchOpsRequest](/docs/guides/Elasticsearch/concepts/elasticsearch-ops-request.md)
-    - [Vertical Scaling Overview](/docs/guides/Elasticsearch/scaling/vertical-scaling/overview.md)
+    - [Elasticsearch](/docs/guides/elasticsearch/concepts/elasticsearch.md)
+    - [Topology](/docs/guides/elasticsearch/clustering/topology-cluster/index.md)
+    - [ElasticsearchOpsRequest](/docs/guides/elasticsearch/concepts/elasticsearch-ops-request.md)
+    - [Vertical Scaling Overview](/docs/guides/elasticsearch/scaling/vertical/overview.md)
 
 To keep everything isolated, we are going to use a separate namespace called `demo` throughout this tutorial.
 
@@ -686,7 +686,6 @@ kubectl delete ns demo
 
 ## Next Steps
 
-- 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).
+- Detail concepts of [Elasticsearch object](/docs/guides/elasticsearch/concepts/elasticsearch.md).
+- Different Elasticsearch topology clustering modes [here](/docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md).
 - Want to hack on KubeDB? Check our [contribution guidelines](/docs/CONTRIBUTING.md).
diff --git a/docs/guides/elasticsearch/volume-expansion/_index.md b/docs/guides/elasticsearch/volume-expansion/_index.md
diff --git a/docs/guides/elasticsearch/volume-expansion/combined.md b/docs/guides/elasticsearch/volume-expansion/combined.md
@@ -360,6 +360,6 @@ kubectl delete ns demo
 
 ## Next Steps
 
-- Detail concepts of [Elasticsearch object](/docs/guides/elasticsearch/concepts/elasticsearch.md).
-- Different Elasticsearch topology clustering modes [here](/docs/guides/elasticsearch/clustering/topology-cluster/index.md).
+- Detail concepts of [Elasticsearch object](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
+- Different Elasticsearch topology clustering modes [here](/docs/guides/elasticsearch/clustering/topology-cluster/single-dedicated-cluster/index.md).
 - Want to hack on KubeDB? Check our [contribution guidelines](/docs/CONTRIBUTING.md).
diff --git a/docs/guides/elasticsearch/volume-expansion/es-voloume-expansion.png b/docs/guides/elasticsearch/volume-expansion/es-voloume-expansion.png
diff --git a/docs/guides/elasticsearch/volume-expansion/overview.md b/docs/guides/elasticsearch/volume-expansion/overview.md
@@ -27,7 +27,7 @@ This guide will give an overview on how KubeDB Ops-manager operator expand the v
 The following diagram shows how KubeDB Ops-manager operator expand the volumes of `Elasticsearch` database components. Open the image in a new tab to see the enlarged version.
 
 <figure align="center">
-      <img alt="Volume Expansion process of Elasticsearch" src="/docs/images/elasticsearch/es-volume-expansion.jpg">
+      <img alt="Volume Expansion process of Elasticsearch" src="/docs/images/elasticsearch/es-volume-expansion.png">
     <figcaption align="center">Fig: Volume Expansion process of Elasticsearch</figcaption>
 </figure>
 
diff --git a/docs/guides/elasticsearch/volume-expansion/topology.md b/docs/guides/elasticsearch/volume-expansion/topology.md
@@ -745,7 +745,7 @@ spec:
 ```
 
 ```bash
-$ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/elasticsearch/volume-expantion/volume-expansion-topo-data.yaml
+$ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/elasticsearch/volume-expansion/volume-expansion-topo-data.yaml
 Elasticsearchopsrequest.ops.kubedb.com/volume-expansion-data-nodes created
 ```
 ## Cleaning Up
