Process PR comments: Limit text width, minor textual changes.

Author: jorisdral

README.rst

@@ -130,11 +130,23 @@ The general synopsis is as follows:
 
 * ``--validate-db`` - Flag to revalidate all on-disk database files
 
-* ``--in-memory-ledger-db-backend`` - Optionally use the in-memory backend of the UTxO HD feature: store the complete ledger state in memory. Incompatible with ``--lmdb-ledger-db-backend``.
-
-* ``--lmdb-ledger-db-backend`` - Optionally use the LMDB backend of the UTxO HD feature: store parts of the ledger state on disk. Incompatible with ``--in-memory-ledger-db-backend``. The node uses the LMDB backend by default if no ``--*-db-backend`` flags are set.
-
-  * ``--lmdb-mapsize`` - Optionally set the mapsize (maximum database size) for the LMDB backend. By default, the mapsize (maximum database size) of the backend is set to 16 Gigabytes. Warning: if the database size exceeds the given mapsize, the node will abort. Therefore, the mapsize should be set to a value high enough to guarantee that the maximum database size will not be reached during the expected node uptime.
+* ``--in-memory-ledger-db-backend`` - Use the in-memory backend to store the
+  UTxO portion of the ledger state in memory. As a result, the whole ledger
+  state will be stored in memory. Incompatible with
+  ``--lmdb-ledger-db-backend``.
+* ``--lmdb-ledger-db-backend`` - Use the LMDB backend to store the UTxO portion
+  of the ledger state on disk. The remainder of the ledger state will still be
+  stored in memory. Incompatible with ``--in-memory-ledger-db-backend``. The
+  node uses the LMDB backend by default if no ``--*-db-backend`` flags are set.
+
+  * ``--lmdb-mapsize`` - Set the maximum database size (mapsize) for the LMDB
+    backend. By default, the mapsize of the backend is set to 16 Gigabytes.
+    Warning: if the database size exceeds the given mapsize, the node will
+    abort. Therefore, the mapsize should be set to a value high enough to
+    guarantee that the maximum database size will not be reached during the
+    expected node uptime. The current default value is sufficient to offer this
+    guarantee, and setting the mapsize to anything less is therefore not
+    recommended.
 
 Configuration ``.yaml`` files
 =============================

doc/getting-started/understanding-config-files.md

@@ -356,11 +356,22 @@ It is also possible to have more fine grained control over filtering of trace ou
 	}
 ```
 
-#### UTxO HD
-
-The UTxO HD feature of the consensus layer allows parts of the ledger state to be stored on-disk, whereas consensus previously kept the whole ledger state in memory. The node can be configured to use any of two *backends*:
-
-* The *LMDB backend*, which is built around a Lightning Memory-Mapped Database (LMDB), stores parts of the ledger state on disk. Optionally, a configuration can be included that sets the mapsize (maximum size) of the on-disk database that is used to store parts of the ledger state. By default, the mapsize is set to 16 Gigabytes. **Warning**: if the database size exceeds the given mapsize, the node will abort. Therefore, the mapsize should be set to a value high enough to guarantee that the maximum database size will not be reached during the expected node uptime.
+#### Ledger state on disk
+
+The UTxO HD feature of the consensus layer allows parts of the ledger state
+to be stored on disk, as opposed to keeping the whole ledger state in memory.
+The node can be configured to use any of two *backends*:
+
+* The *LMDB backend*, which is built around a [Lightning Memory-Mapped Database
+(LMDB)](http://www.lmdb.tech/doc/index.html), stores parts of the ledger state
+on disk. Optionally, a configuration can be included that sets the maximum
+database size (mapsize) of the on-disk database that is used to store parts of
+the ledger state. By default, the mapsize is set to 16 Gigabytes. **Warning**:
+if the database size exceeds the given mapsize, the node will abort. Therefore,
+the mapsize should be set to a value high enough to guarantee that the maximum
+database size will not be reached during the expected node uptime. The current
+default value is sufficient to offer this guarantee, and setting the mapsize
+to anything less is therefore not recommended.
   ```json
   "LedgerDBBackend": "LMDB",
   "LMDBMapSize": "16G",
@@ -370,4 +381,7 @@ The UTxO HD feature of the consensus layer allows parts of the ledger state to b
   "LedgerDBBackend": "InMemory",
   ```
 
-If no choice of backend is configured, then the node defaults to using the LMDB backend with the *default* mapsize. It is recommended not to opt for the in-memory backend if the machine that is running the node is constrained by the amount of available memory.
+If no choice of backend is given, then the node defaults to using the LMDB
+backend with the *default* mapsize. It is recommended not to opt for the
+in-memory backend if the machine that is running the node is memory
+constrained.