fix doc indendation

README.md

@@ -32,8 +32,7 @@ The on-disk format is **not stable** yet.
 
 ## Future work
 
-- Optimize tiny write transactions: append to the last file if possible, instead of starting a new one. Currently each write transaction opens a new file, which will have to erase at least one full page, even if the transaction writes just one small key. It is recommended to batch multiple writes in a single transaction
-for performance.
+- Optimize tiny write transactions: append to the last file if possible, instead of starting a new one. Currently each write transaction opens a new file, which will have to erase at least one full page, even if the transaction writes just one small key. It is recommended to batch multiple writes in a single transaction for performance.
 - Support access align higher than 4. Currently reads/writes are (optionally) aligned up to 4 bytes. Some flash out there can only be written in 8-byte words or higher.
 - Allow writes within a transaction to be unsorted.
 - Allow reads within a write transaction. They should see the the not yet committed writes in the current transaction.

src/config.rs

@@ -5,11 +5,11 @@
 //! They can be set in two ways:
 //!
 //! - Via Cargo features: enable a feature like `<name>-<value>`. `name` must be in lowercase and
-//! use dashes instead of underscores. For example. `max-page-count-1024`. Only a selection of values
-//! is available, check `Cargo.toml` for the list.
+//!   use dashes instead of underscores. For example. `max-page-count-1024`. Only a selection of values
+//!   is available, check `Cargo.toml` for the list.
 //! - Via environment variables at build time: set the variable named `EKV_<value>`. For example
-//! `EKV_MAX_PAGE_COUNT=1024 cargo build`. You can also set them in the `[env]` section of `.cargo/config.toml`.
-//! Any value can be set, unlike with Cargo features.
+//!   `EKV_MAX_PAGE_COUNT=1024 cargo build`. You can also set them in the `[env]` section of `.cargo/config.toml`.
+//!   Any value can be set, unlike with Cargo features.
 //!
 //! Environment variables take precedence over Cargo features. If two Cargo features are enabled for the same setting
 //! with different values, compilation fails.