Update FAQ.md

DOC/FAQ.md

@@ -58,6 +58,8 @@ Under the covers however, only the Leader can make changes to the database. If a
 ## Can I send a read request to any node in the cluster?
 Yes. If a read request must be serviced by the Leader, however, rqlite will transparently forward the request to the Leader, wait for the Leader to handle it, and return the results to the client. If the node receiving the write cannot contact the Leader, the write will fail and return an error to the client.
 
+Some reads, depending on the requested [_read consistency_](https://github.com/rqlite/rqlite/blob/master/DOC/CONSISTENCY.md), do not need to serviced by the Leader, and in that case the node can service the read regardless of whether it contact the Leader or not.
+
 ## rqlite is distributed. Does that mean it can increase SQLite performance?
 Yes, but only for reads. It does not provide any scaling for writes, since all writes must go through the leader. **rqlite is distributed primarily for replication and fault tolerance, not for peformance**. In fact write performance is reduced relative to a standalone SQLite database, because of the round-trips between nodes and the need to write to the Raft log.