diff --git a/approach/estimates.md b/approach/estimates.md
index e8df5bf..2ab72e0 100644
--- a/approach/estimates.md
+++ b/approach/estimates.md
@@ -1,12 +1,15 @@
+# Estimates
 
 We write [user stories](approach/user-stories.md) with the client and then estimate complexity on our own, ideally two different developers independently come up with an estimate and then compare and discuss the reason for differences to get to a final number.
 
-We estimate complexity using the Fibonacci sequence because complexity grows exponentially. More info at http://www.yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html
+We estimate complexity using the Fibonacci sequence because complexity grows exponentially. More info at [yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html](http://www.yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html)
 
 We usually translate that complexity point into twice as many hours. For example, an issue with a complexity of 5 translates to 10 hours.  This is based very roughly on our typical velocity.
 
 ## Estimating migrations
 
-Historically, We estimate the complexity for migrating Drupal entities roughly based on the following formula:
+Historically, we get a rough first pass at an estimate of the complexity for migrating Drupal entities based on the following formula:
 
-1 * # Entities + 2 * # Fields = Migration Complexity
+```
+$number_of_entities + (2 * $number_of_fields) = Migration Complexity
+```