FIx Error

Signed-off-by: Muhammad Raisul Islam Evan <[email protected]>
kubedb · Sep 11, 2024 · 76fd45f · 76fd45f
1 parent c754d55
commit 76fd45f
Show file tree

Hide file tree

Showing 6 changed files with 10 additions and 10 deletions.
diff --git a/docs/guides/memcached/concepts/memcached-autoscaler.md b/docs/guides/memcached/concepts/memcached-autoscaler.md
@@ -18,7 +18,7 @@ section_menu_id: guides
 
 `MemcachedAutoscaler` is a Kubernetes `Custom Resource Definitions` (CRD). It provides a declarative configuration for autoscaling Memcached compute resources in a Kubernetes native way.
 
-## RedisAutoscaler CRD Specifications
+## MemcachedAutoscaler CRD Specifications
 
 Like any official Kubernetes resource, a `MemcachedAutoscaler` has `TypeMeta`, `ObjectMeta`, `Spec` and `Status` sections.
 

diff --git a/docs/guides/memcached/monitoring/overview.md b/docs/guides/memcached/monitoring/overview.md
@@ -44,7 +44,7 @@ In order to enable monitoring for a database, you have to configure `spec.monito
 
 ## Sample Configuration
 
-A sample YAML for Redis crd with `spec.monitor` section configured to enable monitoring with [Prometheus operator](https://github.com/prometheus-operator/prometheus-operator) is shown below.
+A sample YAML for Memcached crd with `spec.monitor` section configured to enable monitoring with [Prometheus operator](https://github.com/prometheus-operator/prometheus-operator) is shown below.
 
 ```yaml
 apiVersion: kubedb.com/v1
@@ -83,7 +83,7 @@ spec:
             cpu: 250m
 ```
 
-Assume that above Redis is configured to use basic authentication. So, exporter image also need to provide password to collect metrics. We have provided it through `spec.monitor.args` field.
+Assume that above Memcached is configured to use basic authentication. So, exporter image also need to provide password to collect metrics. We have provided it through `spec.monitor.args` field.
 
 Here, we have specified that we are going to monitor this server using Prometheus operator through `spec.monitor.agent: prometheus.io/operator`. KubeDB will create a `ServiceMonitor` crd in `monitoring` namespace and this `ServiceMonitor` will have `release: prometheus` label.
 

diff --git a/docs/guides/memcached/reconfigure/_index.md b/docs/guides/memcached/reconfigure/_index.md
@@ -4,7 +4,7 @@ menu:
   docs_{{ .version }}:
     identifier: mc-reconfigure
     name: Reconfigure
-    parent: mc-redis-guides
+    parent: mc-memcached-guides
     weight: 46
 menu_name: docs_{{ .version }}
 ---
diff --git a/docs/guides/memcached/reconfigure/memcached.md b/docs/guides/memcached/reconfigure/memcached.md
@@ -84,7 +84,7 @@ spec:
 Let's create the `Memcached` CR we have shown above,
 
 ```bash
-$ kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/memcached/reconfigure/sample-redis-config.yaml
+$ kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/memcached/reconfigure/sample-memcached-config.yaml
 memcached.kubedb.com/memcd-quickstart created
 ```
 
@@ -192,7 +192,7 @@ NAME                          TYPE          STATUS       AGE
 memcd-reconfig                Reconfigure   Successful   1m
 ```
 
-We can see from the above output that the `MemcachedOpsRequest` has succeeded. If we describe the `RedisOpsRequest` we will get an overview of the steps that were followed to reconfigure the database.
+We can see from the above output that the `MemcachedOpsRequest` has succeeded. If we describe the `MemcachedOpsRequest` we will get an overview of the steps that were followed to reconfigure the database.
 
 ```bash
 $ kubectl describe memcachedopsrequest -n demo memcd-reconfig
@@ -312,7 +312,7 @@ As we can see from the configuration of running memcached, the value of `maxclie
 
 Now we will reconfigure this database again to set `maxclients` to `3000`. This time we won't use a new secret. We will use the `applyConfig` field of the `MemcachedOpsRequest`. This will merge the new config in the existing secret.
 
-#### Create RedisOpsRequest
+#### Create MemcachedOpsRequest
 
 Now, we will use the new configuration in the `data` field in the `MemcahcedOpsRequest` CR. The `MemcachedOpsRequest` yaml is given below,
 

diff --git a/docs/guides/memcached/scaling/vertical-scaling/memcached.md b/docs/guides/memcached/scaling/vertical-scaling/memcached.md
@@ -1,5 +1,5 @@
 ---
-title: Vertical Scaling Standalone Redis
+title: Vertical Scaling Memcached
 menu:
   docs_{{ .version }}:
     identifier: rd-vertical-scaling-standalone

diff --git a/docs/guides/memcached/scaling/vertical-scaling/overview.md b/docs/guides/memcached/scaling/vertical-scaling/overview.md
@@ -28,7 +28,7 @@ The following diagram shows how KubeDB Ops Manager updates the resources of the
 
 <figure align="center">
   <img alt="Vertical scaling process of Memcached" src="/docs/images/memcached/memcached-vertical-scaling.png">
-<figcaption align="center">Fig: Vertical scaling process of Redis</figcaption>
+<figcaption align="center">Fig: Vertical scaling process of Memcached</figcaption>
 </figure>
 
 The updating process consists of the following steps:
@@ -49,7 +49,7 @@ The updating process consists of the following steps:
 
 10. After successfully updating of `Memcached`object, the `KubeDB` Enterprise operator resumes the `Memcached` object so that the `KubeDB` Community operator can resume its usual operations.
 
-In the next doc, we are going to show a step-by-step guide on updating of a Redis database using update operation.
+In the next doc, we are going to show a step-by-step guide on updating of a Memcached database using update operation.
 
 ## Next Steps