From 8d5fcb139eebb7448dd5d9f82bbb565f3273df7f Mon Sep 17 00:00:00 2001
From: Hannah Troisi <htroisi@pinterest.com>
Date: Sat, 16 Jul 2016 21:41:41 -0700
Subject: [PATCH] Update layer-backing.md

---
 _docs/layer-backing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_docs/layer-backing.md b/_docs/layer-backing.md
index b93cd28f..029c408e 100755
--- a/_docs/layer-backing.md
+++ b/_docs/layer-backing.md
@@ -10,7 +10,7 @@ In some cases, you can substantially improve your app's performance by using lay
 
 With UIKit, manually converting view-based code to layers is laborious due to the difference in APIs. Worse, if at some point you need to enable touch handling or other view-specific functionality, you have to manually convert everything back (and risk regressions!).
 
-With all AsyncDisplayKit nodes, converting an entire subtree from views to layers is as simple as...
+With all AsyncDisplayKit nodes, converting an entire subtree from views to layers is as simple as:
 
 <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>