From f0dac1450556dad8dafa9a3091f5aeb4da1d652f Mon Sep 17 00:00:00 2001
From: Muukii <muukii.app@gmail.com>
Date: Tue, 26 Jun 2018 00:29:02 +0900
Subject: [PATCH] Fix typo in containers-asviewcontroller.md (#989)

---
 docs/_docs/containers-asviewcontroller.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/_docs/containers-asviewcontroller.md b/docs/_docs/containers-asviewcontroller.md
index f3a5d8e5d3..8b4fd3648d 100755
--- a/docs/_docs/containers-asviewcontroller.md
+++ b/docs/_docs/containers-asviewcontroller.md
@@ -62,6 +62,6 @@ init(models: [Model]) {
 
 <br>
 <div class = "note">
-<b>Conversion Tip</b>: If your app already has a complex view controller hierarchy, it is perfectly fine to have all of them subclass <code>ASViewController</code>. That is to say, even if you don't use <code>ASViewController</code>'s designated initializer <code>-initiWithNode:</code>, and only use the <code>ASViewController</code> in the manner of a traditional <code>UIViewController</code>, this will give you the additional node support if you choose to adopt it in different areas your application. 
+<b>Conversion Tip</b>: If your app already has a complex view controller hierarchy, it is perfectly fine to have all of them subclass <code>ASViewController</code>. That is to say, even if you don't use <code>ASViewController</code>'s designated initializer <code>-initWithNode:</code>, and only use the <code>ASViewController</code> in the manner of a traditional <code>UIViewController</code>, this will give you the additional node support if you choose to adopt it in different areas your application. 
 </div>