docs: correct read-only volume wording (fixes #11159)

The read-only volume section incorrectly described the mount as a bind mount.

Refer to the mounted data as a volume and remove the host propagation claim.

Co-Authored-By: Codex <noreply@openai.com>

Author: dvdksn

content/manuals/engine/storage/volumes.md

@@ -403,9 +403,8 @@ $ docker volume rm nginx-vol
 
 ## Use a read-only volume
 
-For some development applications, the container needs to write into the bind
-mount so that changes are propagated back to the Docker host. At other times,
-the container only needs read access to the data. Multiple
+For some applications, the container needs to write to the volume. At other
+times, the container only needs read access to the data. Multiple
 containers can mount the same volume. You can simultaneously mount a
 single volume as `read-write` for some containers and as `read-only` for others.