diff --git a/doc/persist.rst b/doc/persist.rst
index 1828b4f8..d6c215bb 100644
--- a/doc/persist.rst
+++ b/doc/persist.rst
@@ -446,6 +446,16 @@ desired new container type ``new_table_t`` in a ``immer::persist::incompatible_h
 
 We can see that the transformation has been applied, the keys have the ``_key`` suffix.
 
+.. note::
+   While different transformed containers will not have structural sharing, transforming the same container multiple times will reuse previously transformed data.
+   In other words, transformation will be cached on the container level but not on the nodes level.
+
+.. literalinclude:: ../test/extra/persist/test_for_docs.cpp
+   :language: c++
+   :start-after: start-returned-transformed-container-is-the-same
+   :end-before:  end-returned-transformed-container-is-the-same
+
+
 .. _transforming-nested-containers:
 
 Transforming nested containers
diff --git a/test/extra/persist/test_for_docs.cpp b/test/extra/persist/test_for_docs.cpp
index fc23ef1c..0f6e3bc2 100644
--- a/test/extra/persist/test_for_docs.cpp
+++ b/test/extra/persist/test_for_docs.cpp
@@ -588,6 +588,12 @@ TEST_CASE("Transform table's ID type", "[docs]")
                                               new_item{{"two_key"}, "_2_"}};
         REQUIRE(new_value == expected_new);
         // include:end-new_table_t-new-hash-transformation
+
+        // include:start-returned-transformed-container-is-the-same
+        const auto new_value_2 =
+            immer::persist::convert_container(pools, transformed_pools, value);
+        REQUIRE(new_value_2.impl().root == new_value.impl().root);
+        // include:end-returned-transformed-container-is-the-same
     }
 }