finished updating 'next' specifications in the headers

_docs/debug-tool-hit-test-slop.md

@@ -2,7 +2,9 @@
 title: Hit Test Visualization
 layout: docs
 permalink: /docs/debug-tool-hit-test-slop.html
+next: debug-tool-ASRangeController.html
 ---
+
 ## Visualize tappable areas on ASControlNodes
 ### Description
 This debug feature adds a semi-transparent neon green highlight overlay on any ASControlNodes that have a `target:action:` pair added. The tappable range is defined as the ASControlNode’s frame + its hitTestSlop (UIEdgeInsets used by the ASControlNode to extend it’s tappable range). 

_docs/debug-tool-pixel-scaling.md

@@ -2,7 +2,9 @@
 title: Image Scaling
 layout: docs
 permalink: /docs/debug-tool-pixel-scaling.html
+next: debug-tool-hit-test-slop.html
 ---
+
 ## Visualize ASImageNode.image’s pixel scaling
 ### Description
 This debug feature adds a red text label overlay on the bottom right hand corner of an ASImageNode if (and only if) the image’s size in pixels does not match it’s bounds size in pixels, e.g.

_docs/drawing-priority.md

@@ -2,6 +2,7 @@
 title: Drawing Priority
 layout: docs
 permalink: /docs/drawing-priority.html
+next: hit-test-slop.html
 ---
 
 <div class = "warning">😑 This page is coming soon...</div>

_docs/hit-test-slop.md

@@ -2,6 +2,7 @@
 title: Hit Test Slop
 layout: docs
 permalink: /docs/hit-test-slop.html
+next: image-modification-block.html
 ---
 
 <div class = "warning">😑 This page is coming soon...</div>

_docs/image-modification-block.md

@@ -2,6 +2,7 @@
 title: Image Modification Blocks
 layout: docs
 permalink: /docs/image-modification-block.html
+next: placeholder-fade-duration.html
 ---
 
 <div class = "warning">😑 This page is coming soon...</div>

_docs/layer-backing.md

@@ -2,6 +2,7 @@
 title: Layer Backing
 layout: docs
 permalink: /docs/layer-backing.html
+next: synchronous-concurrency.html
 ---
 
 Layer-backing. In some cases, you can substantially improve your app's performance by using layers instead of views. 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!).

_docs/layout-options.md

@@ -2,6 +2,7 @@
 title: Layout Options
 layout: docs
 permalink: /docs/layout-options.html
+next: layer-backing.html
 ---
 
 When using ASDK, you have three options for layout. Note that UIKit Autolayout is **not** supported by ASDK. 

_docs/placeholder-fade-duration.md

@@ -2,6 +2,7 @@
 title: Placeholder Fade Duration
 layout: docs
 permalink: /docs/placeholder-fade-duration.html
+next: debug-tool-pixel-scaling.html
 ---
 
 <div class = "warning">😑 This page is coming soon...</div>

_docs/subtree-rasterization.md

@@ -2,6 +2,7 @@
 title: Subtree Rasterization
 layout: docs
 permalink: /docs/subtree-rasterization.html
+next: drawing-priority.html
 ---
 
 Precompositing. Flattening an entire view hierarchy into a single layer also improves performance, but comes with a hit to maintainability and hierarchy-based reasoning. Nodes can do this for you too!

_docs/synchronous-concurrency.md

@@ -2,6 +2,7 @@
 title: Synchronous Concurrency
 layout: docs
 permalink: /docs/synchronous-concurrency.html
+next: subtree-rasterization.html
 ---
 
 <div class = "warning">😑 This page is coming soon...</div>