diff --git a/DOC/DATA_API.md b/DOC/DATA_API.md
index e2d338fe..8facda4d 100644
--- a/DOC/DATA_API.md
+++ b/DOC/DATA_API.md
@@ -152,7 +152,7 @@ curl -XPOST 'localhost:4001/db/execute?pretty&timings' -H "Content-Type: applica
 ## How rqlite handles requests
 _This section assumes a basic familiarity with the Raft protocol. A simple introduction to Raft can be found [here](http://thesecretlivesofdata.com/raft/)._
 
-To make best use of the rqlite API, there are some important details to know.
+To make the very best use of the rqlite API, there are some important details to know. But understanding the following details is **not required** to make full use of rqlite.
 
 With any rqlite cluster, all write-requests must be serviced by the cluster Leader -- this is due to the way the Raft consensus protocol works. If a client sends a write request to a Follower (or read-only, non-voting, node), the Follower transparently forwards the request to the Leader. The Follower waits for the response from the Leader, and returns it to the client. Any credential information included in the original HTTP request to the Follower is included with the forwarded request (assuming that permission checking also passes first on the Follower), and permission checking is performed on the Leader.