From 694fc4a03767db7c84a1eb63b4c23b85d7a76a7e Mon Sep 17 00:00:00 2001
From: TastyHeadphones <76083688+TastyHeadphones@users.noreply.github.com>
Date: Sat, 26 Sep 2026 10:10:59 +0900
Subject: [PATCH] man: fix volume create mount path and name reuse notes

The example mounts at /world but the prose said /src. Also document
same-driver reuse vs cross-driver name clash, matching the reference docs.
---
 man/src/volume/create.md | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/man/src/volume/create.md b/man/src/volume/create.md
index 1935b07e020b..8d76045e9de8 100644
--- a/man/src/volume/create.md
+++ b/man/src/volume/create.md
@@ -6,12 +6,17 @@ configure the container to use it, for example:
     hello
     $ docker run -d -v hello:/world busybox ls /world
 
-The mount is created inside the container's `/src` directory. Docker does
+The mount is created inside the container's `/world` directory. Docker does
 not support relative paths for mount points inside the container.
 
-Multiple containers can use the same volume in the same time period. This is
-useful if two containers need access to shared data. For example, if one
-container writes and the other reads the data.
+Multiple containers can use the same volume. This is useful if two containers
+need access to shared data. For example, if one container writes and the other
+reads the data.
+
+Volume names must be unique among drivers. Attempting to create two volumes
+with the same name on different drivers results in an error. If you specify a
+volume name already in use on the current driver, Docker reuses the existing
+volume and does not return an error.
 
 ## Driver specific options