diff --git a/Reference-Manual-(v3.x).mediawiki b/Reference-Manual-(v3.x).mediawiki
index 56eb825..b6df3d2 100644
--- a/Reference-Manual-(v3.x).mediawiki
+++ b/Reference-Manual-(v3.x).mediawiki
@@ -3184,7 +3184,7 @@ To create a collection to hold session variables (SESSION) use action setsid. To
 
 ; Note : ModSecurity implements atomic updates of persistent variables only for integer variables (counters) at this time. Variables are read from storage whenever initcol is encountered in the rules and persisted at the end of request processing. Counters are adjusted by applying a delta generated by re-reading the persisted data just before being persisted. This keeps counter data consistent even if the counter was modified and persisted by another thread/process during the transaction.
 
-; Note : ModSecurity uses a Berkley Database (SDBM) for persistent storage. This type of database is generally limited to storing a maximum of 1008 bytes per key. This may be a limitation if you are attempting to store a considerable amount of data in variables for a single key. Some of this limitation is planned to be reduced in a future version of ModSecurity.
+; Note : When using on-disk storage rather than in-memory storage, libModSecurity uses LMDB. This type of database has, by default, a maximum key length of 511 bytes. This may be a limitation if you are attempting to store a considerable amount of data in variables for a single key.
 
 = Miscellaneous Topics =