diff --git a/docs/_docs/synchronous-concurrency.md b/docs/_docs/synchronous-concurrency.md
index 3d838e3e0..68e9aa457 100755
--- a/docs/_docs/synchronous-concurrency.md
+++ b/docs/_docs/synchronous-concurrency.md
@@ -12,6 +12,8 @@ By setting this property to YES, the main thread will be blocked until display h
 
 Using this option does not eliminate all of the performance advantages of Texture. Normally, a given node has been preloading and is almost done when it reaches the screen, so the blocking time is very short.  Even if the rangeTuningParameters are set to 0 this option outperforms UIKit.  While the main thread is waiting, all subnode display executes concurrently, thus synchronous concurrency.
 
+See the <a href="goo.gl/KJijuX">NSSpain 2015 talk video</a> for a visual walkthrough of this behavior.
+
 <div class = "highlight-group">
 <span class="language-toggle"><a data-lang="swift" class="swiftButton">Swift</a><a data-lang="objective-c" class = "active objcButton">Objective-C</a></span>
 <div class = "code">
@@ -26,3 +28,5 @@ node.neverShowPlaceholders = true
 <br>
 
 Usually, if a cell hasn't finished its display pass before it has reached the screen it will show placeholders until it has drawing its content.  Setting this option to YES makes your scrolling node or ASViewController act more like UIKit, and in fact makes Texture scrolling visually indistinguishable from UIKit's, except that it's faster.
+
+<img src="/static/images/synchronous-concurrency.jpg" width="50%">
diff --git a/docs/static/images/synchronous-concurrency.jpg b/docs/static/images/synchronous-concurrency.jpg
new file mode 100644
index 000000000..b49ea5d4c
Binary files /dev/null and b/docs/static/images/synchronous-concurrency.jpg differ