diff --git a/Chart.yaml b/Chart.yaml
index f551bae..f5ee413 100644
--- a/Chart.yaml
+++ b/Chart.yaml
@@ -15,10 +15,10 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.2.6
+version: 0.2.7
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "0.10.3"
+appVersion: "0.10.5"
diff --git a/README.md b/README.md
index fd50b72..24a20fa 100644
--- a/README.md
+++ b/README.md
@@ -69,4 +69,4 @@ Disclaimer: Snapshot restoration is only supported for single qdrant node setups
 To restore a snapshot create a Persistent Volume and a Persistent Volume Claim using a storage class according to your setup, copy the snapshots to the PV, enable snapshot restoration along with the snapshot file names and pvc name in values.yaml file and run the helm install command.
 
 Example EBS pv, pvc and volume creation command is added in examples directory
-Note: Make sure volume is on the same region and az as where qdrant is going to be installed.
+Note: Make sure volume is on the same region and availability zone as where qdrant is going to be installed.
diff --git a/values.yaml b/values.yaml
index 677874f..232745a 100644
--- a/values.yaml
+++ b/values.yaml
@@ -3,7 +3,7 @@ replicaCount: 1
 image:
   repository: qdrant/qdrant
   pullPolicy: IfNotPresent
-  tag: v0.10.3
+  tag: v0.10.5
 
 imagePullSecrets: []
 nameOverride: ""