diff --git a/docs/concepts/databases/elasticsearch.md b/docs/concepts/databases/elasticsearch.md
index c20d8c11c..e96dd53a9 100644
--- a/docs/concepts/databases/elasticsearch.md
+++ b/docs/concepts/databases/elasticsearch.md
@@ -249,7 +249,7 @@ If not set, KubeDB operator creates a new Secret `{Elasticsearch name}-auth` wit
 
 ### spec.storage
 
-If you don't set `spec.storageType:`  to `Ephemeral` and if you don't specify `spec.topology` filed then `spec.storage` field is required. This field specifies the StorageClass of PVCs dynamically allocated to store data for the database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. You can specify any StorageClass available in your cluster with appropriate resource requests.
+If you don't set `spec.storageType:`  to `Ephemeral` and if you don't specify `spec.topology` field then `spec.storage` field is required. This field specifies the StorageClass of PVCs dynamically allocated to store data for the database. This storage spec will be passed to the StatefulSet created by KubeDB operator to run database pods. You can specify any StorageClass available in your cluster with appropriate resource requests.
 
  - `spec.storage.storageClassName` is the name of the StorageClass used to provision PVCs. PVCs don’t necessarily have to request a class. A PVC with its storageClassName set equal to "" is always interpreted to be requesting a PV with no class, so it can only be bound to PVs with no class (no annotation or one set equal to ""). A PVC with no storageClassName is not quite the same and is treated differently by the cluster depending on whether the DefaultStorageClass admission plugin is turned on.
  - `spec.storage.accessModes` uses the same conventions as Kubernetes PVCs when requesting storage with specific access modes.