diff --git a/docs/guides/druid/backup/application-level/index.md b/docs/guides/druid/backup/application-level/index.md
index ac2d6b9f9b..4c6394ca81 100644
--- a/docs/guides/druid/backup/application-level/index.md
+++ b/docs/guides/druid/backup/application-level/index.md
@@ -240,7 +240,7 @@ spec:
   version: 30.0.0
 ```
 
-KubeStash uses the `AppBinding` CR to connect with the target database. It requires the following two fields to set in AppBinding's `.spec` section.
+KubeStash uses the `AppBinding` CR to connect with the target database. It requires the following two fields to be set in AppBinding's `.spec` section.
 
 - `.spec.clientConfig.service.name` specifies the name of the Service that connects to the database.
 - `.spec.secret` specifies the name of the Secret that holds necessary credentials to access the database.
@@ -789,4 +789,4 @@ kubectl delete retentionpolicies.storage.kubestash.com -n demo demo-retention
 kubectl delete restoresessions.core.kubestash.com -n demo restore-sample-druid
 kubectl delete druid -n demo sample-druid
 kubectl delete druid -n dev restored-druid
-```
\ No newline at end of file
+```
diff --git a/docs/guides/druid/backup/auto-backup/index.md b/docs/guides/druid/backup/auto-backup/index.md
index 13da05ab20..3c16e8bf33 100644
--- a/docs/guides/druid/backup/auto-backup/index.md
+++ b/docs/guides/druid/backup/auto-backup/index.md
@@ -186,7 +186,7 @@ spec:
 
 Here,
 
-- `.spec.backupConfigurationTemplate.backends[*].storageRef` refers our earlier created `gcs-storage` backupStorage.
+- `.spec.backupConfigurationTemplate.backends[*].storageRef` refers to our earlier created `gcs-storage` backupStorage.
 - `.spec.backupConfigurationTemplate.sessions[*].schedule` specifies that we want to backup the database at `5 minutes` interval.
 
 Let's create the `BackupBlueprint` we have shown above,
@@ -196,7 +196,7 @@ $ kubectl apply -f https://github.com/kubedb/docs/raw/{{< param "info.version" >
 backupblueprint.core.kubestash.com/druid-default-backup-blueprint created
 ```
 
-Now, we are ready to backup our `Druid` databases using few annotations.
+Now, we are ready to backup our `Druid` databases using a few annotations.
 
 ## Deploy Sample Druid Database
 
@@ -814,4 +814,4 @@ kubectl delete secret -n demo encrypt-secret
 kubectl delete retentionpolicies.storage.kubestash.com -n demo demo-retention
 kubectl delete druid -n demo sample-druid
 kubectl delete druid -n demo sample-druid-2
-```
\ No newline at end of file
+```
diff --git a/docs/setup/upgrade/index.md b/docs/setup/upgrade/index.md
index 4fff090b8e..8c7abcb24e 100644
--- a/docs/setup/upgrade/index.md
+++ b/docs/setup/upgrade/index.md
@@ -24,7 +24,7 @@ In order to upgrade from KubeDB `v2021.xx.xx` to `{{< param "info.version" >}}`,
 
 #### 1. Update KubeDB Catalog CRDs
 
-Helm [does not upgrade the CRDs](https://github.com/helm/helm/issues/6581) bundled in a Helm chart if the CRDs already exist. So, to upgrde the KubeDB catalog CRD, please run the command below:
+Helm [does not upgrade the CRDs](https://github.com/helm/helm/issues/6581) bundled in a Helm chart if the CRDs already exist. So, to upgrade the KubeDB catalog CRD, please run the command below:
 
 ```bash
 kubectl apply -f https://github.com/kubedb/installer/raw/{{< param "info.version" >}}/crds/kubedb-catalog-crds.yaml