Fix issue #24435: clarify volume description in bind mounts

[dvdksn]

Clarifies the volume description in the bind mounts documentation to avoid confusion about Docker's role in managing volume contents.

Changes:

• Revised the introductory paragraph to clarify that Docker creates and maintains the storage location, but containers access it directly using standard filesystem operations
• Removes language that could be misinterpreted as Docker actively copying or syncing data

Fixes #24435

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	4480765
🔍 Latest deploy log	https://app.netlify.com/projects/docsdocker/deploys/69bd3c455202fc0007fb3e59
😎 Deploy Preview	https://deploy-preview-24441--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[docker-agent]

Assessment: 🟢 APPROVE

This PR successfully clarifies the volume description in the bind mounts documentation. The changes are well-crafted and improve clarity without introducing any documentation quality issues.

What was reviewed:

• ✅ No vendored content edited
• ✅ No redirects needed (no pages removed/moved)
• ✅ Markdown formatting is correct
• ✅ No AI-isms or hedge words
• ✅ Scope preserved (minimal, focused change)
• ✅ Content is factually accurate
• ✅ Front matter unchanged and valid

Key improvement:
The revised text clarifies that Docker creates and maintains the storage location for volumes, but containers access it directly using standard filesystem operations. This removes potential confusion about Docker "managing" the directory's contents in an active sense.

The package-lock.json changes are routine dependency updates with no documentation impact.

No issues found. This change improves documentation clarity and accuracy.