From 2e28597412ab79c2df22e36bf11e9b0c30703eb4 Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Mon, 23 Mar 2026 17:24:33 +0100
Subject: [PATCH] Merge pull request #24441 from
 docker/fix/issue-24435-clarify-volume-desc

Fix issue #24435: clarify volume description in bind mounts
---
 content/manuals/engine/storage/bind-mounts.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/manuals/engine/storage/bind-mounts.md b/content/manuals/engine/storage/bind-mounts.md
index 3badc3c612..d6846b0413 100644
--- a/content/manuals/engine/storage/bind-mounts.md
+++ b/content/manuals/engine/storage/bind-mounts.md
@@ -10,8 +10,9 @@ aliases:
 
 When you use a bind mount, a file or directory on the host machine is mounted
 from the host into a container. By contrast, when you use a volume, a new
-directory is created within Docker's storage directory on the host machine, and
-Docker manages that directory's contents.
+directory is created within Docker's storage directory on the host machine.
+Docker creates and maintains this storage location, but containers access it
+directly using standard filesystem operations.
 
 ## When to use bind mounts