From 699e551880f86c2decb7864afa1ded7dec8c6759 Mon Sep 17 00:00:00 2001
From: Semun Lee <sm79.lee@samsung.com>
Date: Mon, 29 Jun 2015 14:38:57 +0900
Subject: [PATCH] Fix errata

Change-Id: Ibb41e15e311907f346fcc57e6697f17d473e6553
Signed-off-by: Semun Lee <sm79.lee@samsung.com>
---
 org.tizen.gettingstarted/html/native/app_model/application_model_n.htm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/org.tizen.gettingstarted/html/native/app_model/application_model_n.htm b/org.tizen.gettingstarted/html/native/app_model/application_model_n.htm
index 8420cf9..b66cacd 100644
--- a/org.tizen.gettingstarted/html/native/app_model/application_model_n.htm
+++ b/org.tizen.gettingstarted/html/native/app_model/application_model_n.htm
@@ -79,7 +79,7 @@ These devices have constraints, such as relatively small screen sizes and lack o
     <li><p>Your application itself requests to exit by calling the <span style="font-family: Courier New,Courier,monospace;">ui_app_exit()</span> or <span style="font-family: Courier New,Courier,monospace;">service_app_exit()</span> function to terminate the event loop.</p></li>
     <li><p>The low memory killer is terminating your application in a low memory situation.</p></li>
   </ul>
-<p>Since the service application has no UI, sit also has no pause state.</p>
+<p>Since the service application has no UI, it also has no pause state.</p>
   
 <p>Application state changes are managed by the underlying framework. 
 	For more information about application state transitions, see <a href="../../../../org.tizen.guides/html/native/app/application_n.htm#state_trans">Managing Application States and Transitions</a>.</p>
-- 
2.7.4