X-Git-Url: http://review.tizen.org/git/?p=platform%2Fcore%2Fuifw%2Fdali-toolkit.git;a=blobdiff_plain;f=plugins%2Fdali-script-v8%2Fdocs%2Fcontent%2Fdali.js;h=e03a9d22dc2c657538e3586118ae732a487191ec;hp=611d0042655873b2aa95062e0943d8b3cf400a61;hb=f3da11c2818c6d17706fbb2417f21b602b3190f5;hpb=2d5d28f89d92f5a7db5bd84f39ce0c5dbc74508d

diff --git a/plugins/dali-script-v8/docs/content/dali.js b/plugins/dali-script-v8/docs/content/dali.js
index 611d004..e03a9d2 100644
--- a/plugins/dali-script-v8/docs/content/dali.js
+++ b/plugins/dali-script-v8/docs/content/dali.js
@@ -38,7 +38,7 @@ mScript.ExecuteFile( mScriptFileName);
 
 A DALi application uses a hierachy of Dali::Actor objects to position visible content.  An actor inherits a position relative to its parent, and can be moved relative to this point.  UI controls can be built by combining multiple actors.
 
-To display the contents of an actor, it must be connected to the Dali::Stage.  This provides an invisible root (top-level) actor, to which all other actors are added.  A direct or indirect child of the root actor is considered "on-stage".  Multi-touch events are received through signals emitted by on-stage actors.
+To display the contents of an actor, it must be connected to the Dali::Stage.  This provides an invisible root (top-level) actor, to which all other actors are added.  A direct or indirect child of the root actor is considered "onStage".  Multi-touch events are received through signals emitted by on-stage actors.
 
 The following example shows how to connect a new actor to the stage:
 ```