diff --git a/source/riak/tutorials/fast-track/What-is-Riak.md b/source/riak/tutorials/fast-track/What-is-Riak.md
index 7ba61d22ef..a21eaca389 100644
--- a/source/riak/tutorials/fast-track/What-is-Riak.md
+++ b/source/riak/tutorials/fast-track/What-is-Riak.md
@@ -50,7 +50,7 @@ Hinted handoff lets Riak handle node failure. If a node fails, a neighboring nod
 ### Version Conflicts
 In any systems that replicates data, conflicts can arise - e.g., if two clients update the same object at the exact same time; or if not all updates have yet reached hardware that is experiencing lag. Further, in Riak, replicas are "eventually consistent"-  while data is always available, not all replicas may have the most recent update at the exact same time, causing brief periods (generally on the order of milliseconds) of inconsistency while all state changes are synchronized. 
 
-How is divergence addressed? When you make a read request, Riak looks up all replicas for that object. By default, Riak will return the most updated version, determined by looking at the object's vector clock. Vector clocks are metadata attached to each replica when it is created and extended each time it is updated to keep track of versions. You can also allow clients to resolve conflicts themselves. Learn more on *[[eventual consistency|Eventual Consistency]]* and *[[vector clocks|Vector Clocks]]*. 
+How is divergence addressed? When you make a read request, Riak looks up all replicas for that object. By default, Riak will return the most updated version, determined by looking at the object's vector clock. Vector clocks are metadata attached to each replica when it is created. They are extended each time a replica is updated to keep track of versions. You can also allow clients to resolve conflicts themselves. Learn more on *[[eventual consistency|Eventual Consistency]]* and *[[vector clocks|Vector Clocks]]*. 
 
 ### Read Repair
 Further, when an outdated replica is returned as part of a read request, Riak will automatically update the out-of-sync replica to make it consistent. Read repair, a self-healing property of the database, will even update a replica that returns a "not_found" in the event that a node loses it due to physical failure. *[[More on read repair|Replication]]*.