Update zookeeper doc to caution about intermediate nodes.

Author: GaneshChandrasekaran-zz

components/lock.rst

@@ -519,7 +519,7 @@ can be two running containers in parallel.
 ZookeeperStore
 ~~~~~~~~~~~~~~
 
-The way ZookeeperStore works is by maintaining locks in ephemeral nodes within ``PHP_LOCK_NODE`` on the server. That means that by using
+The way ZookeeperStore works is by maintaining locks as ephemeral nodes on the server. That means that by using
 the :ref:`ZookeeperStore <lock-store-zookeeper>` the locks will be automatically released at the end of the session
 in case the client cannot unlock for any reason.
 
@@ -532,6 +532,11 @@ be lost without notifying the running processes.
     the server goes down, the majority will still be up and serving the requests. All the available servers in the
     cluster will see the same state.
 
+.. caution::
+    If you have a path such as ``base_node/node_1/lock_node`` when creating a lock, then only ``lock_node`` will be created as an ephemeral node and other
+    nodes will be created as a persistent node and will not be cleaned up as a part of delete operations. This is because, it could lead
+    to unexpected behavior and hence it is recommended that you always create a lock as ``lock_node`` without any subpath.
+
 Overall
 ~~~~~~~