strong-consistency.md: wrap the paragraph.

Author: knz

strong-consistency.md

@@ -4,7 +4,15 @@ summary: CockroachDB implements consistent replication via majority consensus be
 toc: false
 ---
 
-CockroachDB replicates your data multiple times and guarantees consistency between replicas using the [Raft consensus algorithm](https://raft.github.io/), a popular alternative to [Paxos](http://research.microsoft.com/en-us/um/people/lamport/pubs/paxos-simple.pdf). A consensus algorithm guarantees that any majority of replicas together can always provide the most recently written data on reads. Writes must reach a majority of replicas (2 out of 3 by default) before they are considered committed. If a write does not reach a majority of replicas, it will fail, not be permanent, and will never be visible to readers. This means that clients always see serializable consistency when viewing data (i.e., stale reads are not possible).  
+CockroachDB replicates your data multiple times and guarantees consistency between replicas 
+using the [Raft consensus algorithm](https://raft.github.io/), a popular alternative to 
+[Paxos](http://research.microsoft.com/en-us/um/people/lamport/pubs/paxos-simple.pdf). 
+A consensus algorithm guarantees that any majority of replicas together can always provide 
+the most recently written data on reads. Writes must reach a majority of replicas (2 out of 
+3 by default) before they are considered committed. If a write does not reach a majority of 
+replicas, it will fail, not be permanent, and will never be visible to readers. This means 
+that clients always see serializable consistency when viewing data (i.e., stale reads are 
+not possible).  
 
 -   No downtime for server restarts, machine failures, or datacenter outages
 -   Local or wide-area replication with no stale reads on failover