#27345 Updated warnings in order of importance

Author: Joe Bennett

components/lock.rst

@@ -466,18 +466,21 @@ method uses the Memcached's ``flush()`` method which purges and removes everythi
 MongoDbStore
 ~~~~~~~~~~~~
 
-The locked resouce name is indexed in the ``_id`` field of the lock collection.
-An indexed field's value in MongoDB can be a maximum of 1024 bytes in length
-inclusive of structural overhead.
+.. caution::
+
+    The locked resouce name is indexed in the ``_id`` field of the
+    lock collection.
+    An indexed field's value in MongoDB can be a maximum of 1024 bytes in
+    length inclusive of structural overhead.
 
 For more details see: https://docs.mongodb.com/manual/reference/limits/#Index-Key-Limit
 
 .. caution::
 
     This store relies on all client and server nodes to have
     synchronized clocks for lock expiry to occur at the correct time.
-    To ensure locks don't expire prematurely; the ttl's should be set with enough
-    extra time to account for any clock drift between nodes.
+    To ensure locks don't expire prematurely; the lock TTL should be set
+    with enough extra time to account for any clock drift between nodes.
 
 A TTL index MUST BE used on MongoDB 2.2+ to automatically clean up expired locks.
 
@@ -495,8 +498,9 @@ to create the TTL index during setup.
 
 For more details see: http://docs.mongodb.org/manual/tutorial/expire-data/
 
-writeConcern, readConcern and readPreference are not specified by MongoDbStore
-meaning the collection's settings will take effect.
+``writeConcern``, ``readConcern`` and ``readPreference`` are not specified by
+MongoDbStore meaning the collection's settings will take effect.
+
 For more details see: https://docs.mongodb.com/manual/applications/replication/
 
 RedisStore