From 6c679a648d5776139e2a23d59367e43c3abdbf59 Mon Sep 17 00:00:00 2001
From: Rashi Chaubal <12rashic@gmail.com>
Date: Wed, 5 Feb 2025 14:49:29 +0530
Subject: [PATCH] fix: clarified rprivate by adding spell out recursive private
 in volumes.md (#21711)

## Description

<!-- Tell us what you did and why -->
To avoid confusion of rprivate provided fix: clarified rprivate by
adding spell out recursive private in volumes.md

## Related issues or tickets
#21688

<!-- Related issues, pull requests, or Jira tickets -->
#21688

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review

---------

Signed-off-by: Rashi Chaubal <12rashic@gmail.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 content/manuals/engine/storage/volumes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/manuals/engine/storage/volumes.md b/content/manuals/engine/storage/volumes.md
index c99eed561d..d99a39fc60 100644
--- a/content/manuals/engine/storage/volumes.md
+++ b/content/manuals/engine/storage/volumes.md
@@ -56,7 +56,7 @@ If your container generates non-persistent state data, consider using a
 increase the container's performance by avoiding writing into the container's
 writable layer.
 
-Volumes use `rprivate` bind propagation, and bind propagation isn't
+Volumes use `rprivate` (recursive private) bind propagation, and bind propagation isn't
 configurable for volumes.
 
 ## A volume's lifecycle