review resolved

Signed-off-by: Rudro-25 <[email protected]>
kubedb · Oct 25, 2024 · 32d19d9 · 32d19d9
1 parent e685158
commit 32d19d9
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 12 deletions.
diff --git a/docs/guides/zookeeper/restart/restart.md b/docs/guides/zookeeper/restart/restart.md
@@ -3,7 +3,7 @@ title: Restart ZooKeeper
 menu:
   docs_{{ .version }}:
     identifier: zk-restart-details
-    name: Restart Cluster
+    name: Restart Ensemble
     parent: zk-restart
     weight: 10
 menu_name: docs_{{ .version }}
@@ -96,7 +96,7 @@ Now the Ops-manager operator will restart the pods sequentially by their cardina
 
 ```shell
 $ kubectl get zookeeperopsrequest -n demo
-NAME      TYPE      STATUS       AGE
+NAME         TYPE      STATUS       AGE
 zk-restart   Restart   Successful   10m
 
 $ kubectl get zookeeperopsrequest -n demo -oyaml zk-restart

diff --git a/docs/guides/zookeeper/update-version/overview.md b/docs/guides/zookeeper/update-version/overview.md
@@ -12,7 +12,7 @@ section_menu_id: guides
 
 > New to KubeDB? Please start [here](/docs/README.md).
 
-# updating ZooKeeper version Overview
+# Overview of ZooKeeper Version Update
 
 This guide will give you an overview on how KubeDB Ops-manager operator update the version of `ZooKeeper` database.
 
@@ -45,10 +45,10 @@ The updating process consists of the following steps:
 
 6. When it finds a `ZooKeeperOpsRequest` CR, it halts the `ZooKeeper` object which is referred from the `ZooKeeperOpsRequest`. So, the `KubeDB` Provisioner  operator doesn't perform any operations on the `ZooKeeper` object during the updating process.
 
-7. By looking at the target version from `ZooKeeperOpsRequest` CR, `KubeDB` Ops-manager operator updates the images of all the `PetSets`. After each image update, the operator performs some checks such as if the oplog is synced and database size is almost same or not.
+7. By looking at the target version from `ZooKeeperOpsRequest` CR, `KubeDB` Ops-manager operator updates the images of all the `PetSets`. 
 
-8. After successfully updating the `PetSets` and their `Pods` images, the `KubeDB` Ops-manager operator updates the image of the `ZooKeeper` object to reflect the updated state of the database.
+8. After successfully updating the `PetSets` and their `Pods` images, the `KubeDB` Ops-manager operator updates the version field of the `ZooKeeper` object to reflect the updated state of the database.
 
 9. After successfully updating of `ZooKeeper` object, the `KubeDB` Ops-manager operator resumes the `ZooKeeper` object so that the `KubeDB` Provisioner  operator can resume its usual operations.
 
-In the next doc, we are going to show a step-by-step guide on updating of a ZooKeeper database using updateVersion operation.
+In the [next](/docs/guides/zookeeper/update-version/update-version.md) doc, we are going to show a step-by-step guide on updating of a ZooKeeper database using updateVersion operation.
diff --git a/docs/guides/zookeeper/update-version/update-version.md b/docs/guides/zookeeper/update-version/update-version.md
@@ -12,7 +12,7 @@ section_menu_id: guides
 
 > New to KubeDB? Please start [here](/docs/README.md).
 
-# update version of ZooKeeper Cluster
+# Update Version of ZooKeeper Ensemble
 
 This guide will show you how to use `KubeDB` Ops-manager operator to update the version of `ZooKeeper` Cluster.
 
@@ -36,7 +36,7 @@ namespace/demo created
 
 > **Note:** YAML files used in this tutorial are stored in [docs/examples/zookeeper](/docs/examples/zookeeper) directory of [kubedb/docs](https://github.com/kube/docs) repository.
 
-## Prepare ZooKeeper cluster
+## Prepare ZooKeeper Ensemble
 
 Now, we are going to deploy a `ZooKeeper` cluster with version `3.8.3`.
 
@@ -76,8 +76,8 @@ Now, wait until `zk-quickstart` created has status `Ready`. i.e,
 
 ```bash
 $ kubectl get zk -n demo                                                                                                                                             
-NAME            VERSION    STATUS    AGE
-zk-quickstart      3.12.12   Ready     109s
+NAME               VERSION    STATUS    AGE
+zk-quickstart      3.9.1      Ready     109s
 ```
 
 We are now ready to apply the `ZooKeeperOpsRequest` CR to update this database.
@@ -129,7 +129,7 @@ Let's wait for `ZooKeeperOpsRequest` to be `Successful`.  Run the following comm
 ```bash
 $ kubectl get zookeeperopsrequest -n demo
 Every 2.0s: kubectl get zookeeperopsrequest -n demo
-NAME                      TYPE            STATUS       AGE
+NAME                TYPE            STATUS       AGE
 upgrade-topology    UpdateVersion   Successful   84s
 ```
 

diff --git a/docs/images/day-2-operation/zookeeper/zk-version-update.svg b/docs/images/day-2-operation/zookeeper/zk-version-update.svg