diff --git a/docs/guides/redis/backup/kubestash/_index.md b/docs/guides/redis/backup/kubestash/_index.md
index 51888b1792..17513ac187 100644
--- a/docs/guides/redis/backup/kubestash/_index.md
+++ b/docs/guides/redis/backup/kubestash/_index.md
@@ -7,4 +7,4 @@
     parent: guides-rd-backup
     weight: 50
 menu_name: docs_{{ .version }}
----
\ No newline at end of file
+---
\ No newline at end of file
diff --git a/docs/guides/redis/backup/kubestash/application-level/index.md b/docs/guides/redis/backup/kubestash/application-level/index.md
index e19d443d72..0b396d00ce 100644
--- a/docs/guides/redis/backup/kubestash/application-level/index.md
+++ b/docs/guides/redis/backup/kubestash/application-level/index.md
@@ -597,7 +597,7 @@ In this section, we will verify whether the desired `Redis` database manifest ha
 ```bash
 $ kubectl get redis -n dev 
 NAME              VERSION   STATUS   AGE
-sample-redis   16.1      Ready    9m46s
+sample-redis      7.4.0     Ready    9m46s
 ```
 
 The output confirms that the `Redis` database has been successfully created with the same configuration as it had at the time of backup.