Description of TTL incorrect in session use case documentation

This page: http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-developing-usecases-sessionstore.html

This text is incorrect:
"When Couchbase Server performs lazy deletion, it flags an item as deleted when the server receives a delete request; later when a client tries to retrieve the item, Couchbase Server will return a message that the key does not exist and actually delete the item. Items that are flagged as expired will be removed every 60 minutes by default by an automatic maintenance process."

-There is no "flagging" of items as expired or deleted.
-Not sure what you mean by "when the server receives a delete request", but any operation to the key causes the TTL to be checked and it is deleted from RAM and asynchronously deleted from disk at that time.
-The automatic process scans the memory space to find items that have already expired, again, there is no flagging.

See this writeup in our KB for a bit more explanation. http://support.couchbase.com/entries/21898948-expiration-in-couchbase. I thought we had some other documentation written about this already, but couldn't find it. This is a pretty key part of our software and should be documented on its own as part of our architecture as well.