clustered max idle upgrade notes

documentation/src/main/asciidoc/topics/eviction.adoc

@@ -234,10 +234,10 @@ When nodes detect that an entry reaches the maximum idle time, {brandname}
 removes it from the cache and does not return the entry to the client that
 requested it.
 
-Before using clustered `max-idle`, you should review the following points:
+Before using `max-idle` with clustered cache modes, you should review the following points:
 
 * `Cache.get()` does not return until the touch commands complete. This synchronous behavior increases latency of client requests.
-* Clustered `max-idle` also updates the recent access count for eviction on all owners.
+* Clustered `max-idle` also updates the "recently accessed" metadata for cache entries on all owners, which {brandname} uses for eviction.
 //Scattered cache is community only
 ifndef::productized[]
 * With scattered cache mode, {brandname} sends touch commands to all nodes, not

documentation/src/main/asciidoc/topics/upgrading.adoc

@@ -1,3 +1,23 @@
+= Upgrading from 10.0 to 10.1 and 10.0 to 11.0
+
+== Maximum Idle Timeouts with Clustered Cache Modes
+Maximum idle expiration has been changed to improve data consistency with clustered cache modes when Infinispan nodes fail.
+
+[NOTE]
+====
+* `Cache.get()` calls do not return until the touch commands complete. This
+synchronous behavior increases latency of client requests and reduces
+performance.
+
+* Maximum idle expiration, `max-idle`, does not currently work with entries
+stored in off-heap memory.
+
+* Likewise, `max-idle` does not work if caches use cache stores as a persistence
+layer.
+====
+
+See link:{../configuring/configuring.html#expiration_maxidle}[Maximum Idle Expiration] for complete details.
+
 = Upgrading from 10.0 to 10.1
 
 == REST Store