doc/rados/operations: refine cache-tiering deprecation note per review

Reduce the note to point existing users to the removal procedure, add a
ref target for the removal section, and rephrase the dm-cache mention to
reflect community adoption without implying official endorsement.

diff --git a/doc/rados/operations/cache-tiering.rst b/doc/rados/operations/cache-tiering.rst
index a1f8e49a933b86a4b08477d348d64f504208ccf5..b3df1c3d418859e5dc6483c4874a107177853540 100644 (file)
--- a/doc/rados/operations/cache-tiering.rst
+++ b/doc/rados/operations/cache-tiering.rst
@@ -7,11 +7,11 @@
    notice. **Do not deploy new cache tiers.** Migrate existing cache
    tier deployments as soon as possible.
 
-.. note:: The following documentation is retained for reference for existing
-   deployments only. For new deployments, use erasure-coded pools or fast
-   storage pools directly. As a community-supported block-level caching
-   alternative, consider ``dm-cache`` (the Linux kernel's device-mapper cache
-   target).
+.. note:: This documentation is retained for existing deployments only.
+   If you need to remove a cache tier, see :ref:`cache-tiering-removal`.
+   Some community members have adopted ``dm-cache`` (the Linux kernel's
+   device-mapper cache target) as a block-level caching alternative, though
+   this is not an officially supported or endorsed configuration.
 
 A cache tier provides Ceph clients with better I/O performance for a subset of
 the data stored in a backing storage tier. Cache tiering involves creating a
@@ -452,10 +452,12 @@ For example, to evict objects after 30 minutes, execute the following:
    ceph osd pool set hot-storage cache_min_evict_age 1800
 
 
+.. _cache-tiering-removal:
+
 Removing a Cache Tier
 =====================
 
-Removing a cache tier differs depending on whether it is a writeback 
+Removing a cache tier differs depending on whether it is a writeback
 cache or a read-only cache.