issue fix

Signed-off-by: Rudro-25 <[email protected]>

docs/guides/zookeeper/backup/kubestash/auto-backup/index.md

@@ -373,12 +373,12 @@ We can see from the above output that the backup session has succeeded. Now, we
 
 **Verify Backup:**
 
-Once a backup is complete, KubeStash will update the respective `Repository` CR to reflect the backup. Check that the repository `sample-zookeeper-backup` has been updated by the following command,
+Once a backup is complete, KubeStash will update the respective `Repository` CR to reflect the backup. Check that the repository `default-blueprint` has been updated by the following command,
 
 ```bash
 $ kubectl get repository -n demo default-blueprint
 NAME                INTEGRITY   SNAPSHOT-COUNT   SIZE        PHASE   LAST-SUCCESSFUL-BACKUP   AGE
-default-blueprint   true        3                1.559 KiB   Ready   80s                      7m32s
+default-blueprint   true        1                1.559 KiB   Ready   80s                      7m32s
 ```
 
 At this moment we have one `Snapshot`. Run the following command to check the respective `Snapshot` which represents the state of a backup run for an application.

docs/guides/zookeeper/backup/kubestash/logical/index.md

@@ -13,7 +13,7 @@ section_menu_id: guides
 
 # Backup and Restore ZooKeeper using KubeStash
 
-KubeStash allows you to backup and restore `ZooKeeper`. It supports backups for `ZooKeeper` instances running in Standalone,  and HA cluster configurations. KubeStash makes managing your `ZooKeeper` backups and restorations more straightforward and efficient.
+KubeStash allows you to backup and restore `ZooKeeper`. KubeStash makes managing your `ZooKeeper` backups and restorations more straightforward and efficient.
 
 This guide will give you an overview how you can take backup and restore your `ZooKeeper` using `Kubestash`.
 
@@ -48,7 +48,7 @@ namespace/demo created
 
 ## Backup ZooKeeper
 
-KubeStash supports backups for `ZooKeeper` instances across different configurations, including Standalone and HA Cluster setups. In this demonstration, we'll focus on a `ZooKeeper` using HA cluster configuration. The backup and restore process is similar for Standalone configuration.
+KubeStash supports backups for `ZooKeeper` instances across different configurations, including Standalone and ZooKeeper Ensemble setups. In this demonstration, we'll focus on a `ZooKeeper` using ZooKeeper Ensemble configuration. The backup and restore process is similar for Standalone configuration.
 
 This section will demonstrate how to backup a `ZooKeeper`. Here, we are going to deploy a `ZooKeeper` using KubeDB. Then, we are going to backup this into a `s3` bucket. Finally, we are going to restore the backup up data into another `ZooKeeper`.
 

docs/guides/zookeeper/backup/kubestash/overview/index.md

@@ -36,11 +36,11 @@ The backup process consists of the following steps:
 
 1. At first, a user creates a `Secret`. This secret holds the credentials to access the backend where the backed up data will be stored.
 
-2. Then, she creates a `BackupStorage` custom resource that specifies the backend information, along with the `Secret` containing the credentials needed to access the backend.
+2. Then, he creates a `BackupStorage` custom resource that specifies the backend information, along with the `Secret` containing the credentials needed to access the backend.
 
 3. KubeStash operator watches for `BackupStorage` custom resources. When it finds a `BackupStorage` object, it initializes the `BackupStorage` by uploading the `metadata.yaml` file to the specified backend.
 
-4. Next, she creates a `BackupConfiguration` custom resource that specifies the target database, addon information (including backup tasks), backup schedules, storage backends for storing the backup data, and other additional settings.
+4. Next, he creates a `BackupConfiguration` custom resource that specifies the target database, addon information (including backup tasks), backup schedules, storage backends for storing the backup data, and other additional settings.
 
 5. KubeStash operator watches for `BackupConfiguration` objects.
 
@@ -79,7 +79,7 @@ The restore process consists of the following steps:
 
 1. At first, a user creates a `ZooKeeper` database where the data will be restored or the user can use the same `ZooKeeper` database.
 
-2. Then, she creates a `RestoreSession` custom resource that specifies the target database where the backed-up data will be restored, addon information (including restore tasks), the target snapshot to be restored, the Repository containing that snapshot, and other additional settings.
+2. Then, he creates a `RestoreSession` custom resource that specifies the target database where the backed-up data will be restored, addon information (including restore tasks), the target snapshot to be restored, the Repository containing that snapshot, and other additional settings.
 
 3. KubeStash operator watches for `RestoreSession` custom resources.