made the 'nometasync' sync mode explanation more clear

diff --git a/docs/backends/lmdb.rst b/docs/backends/lmdb.rst
index 4bc8e151f8fb1cc80addd6e338ca919a6ca82c15..d63d0735756921136e45c3793537864629f8c87c 100644 (file)
--- a/docs/backends/lmdb.rst
+++ b/docs/backends/lmdb.rst
@@ -47,9 +47,9 @@ Default is 2 on 32 bits systems, and 64 on 64 bits systems.
 
 Synchronisation mode: nosync, nometasync, mapasync
 
-* ``nosync``: Don't flush systems buffers to disk when committing a transation.
+* ``nosync``: don't flush systems buffers to disk when committing a transation.
   This means a system crash can corrupt the database or lose the last transactions if buffers are not yet flushed to disk.
-* ``nometasync``: Flush the data on a commit. Slightly faster  than  doing a full sync, but can potentially lose the last committed transaction if the operating system crashes.
+* ``nometasync``: flush system buffers to disk only once per transaction, omit the metadata flush. This maintains database integrity, but can potentially lose the last committed transaction if the operating system crashes.
 * ``mapasync``: use asynchronous flushes to disk. As with nosync, a system crash can then corrupt the database or lose the last transactions.