Update README.md

README.md

@@ -13,12 +13,12 @@ This means that we have to insert tracking code into a number of places to handl
 2. if a user scrolls, revealing new cells, we need to be able to determine which of the newly visible cells are fully in-frame _and_ are already playing back fully-downloaded gifs. 
 3. another situation which is easy to miss relates to the initial presentation of a GIF display. when a collection of gifs is first shown, we need to determine which fully visible cells are already playing back. 
 
-Over Tracking...
+*Over Tracking*
 We also need to be wary of tracking multiple "seen" events for the same gif in the same context. If a user sees a GIF, scrolls down a bunch, then scrolls back to see the same GIF, we should not track a second impresssion for that GIF. 
 
 Luckily, we have "deduplication" logic inside analytics SDK which takes care making sure we don't double or triple track the same gif. 
 
-Under Tracking...
+*Under Tracking*
 However, if a user sees a GIF, then makes a new search, then sees that same the GIF, we _do_ want to track it again, as this a distinct context in which the GIF is being shown.  
 
 Or, alternatively, if the user closes the GIF display, and the reopens it, this is also seen as a new different context.