update documentation for livebox

[model] Redwood
[binary_type] AP
[customer] N/A
[issue#]
[problem]
[cause]
[solution]
[team] Home TF
[horizontal_expansion] N/A

diff --git a/doc/dynamicbox_doc.h b/doc/dynamicbox_doc.h
index a58049e..e00ba37 100644 (file)
--- a/doc/dynamicbox_doc.h
+++ b/doc/dynamicbox_doc.h
@@ -30,7 +30,7 @@
 <H2>1. Script type Dynamic Box</H2>
 If you choose the Script Type DBox, you have to use this.
 
-Dyanmic Box defines its own syntax to share the content between home application and provider application.
+Dynamic Box defines its own syntax to share the content between home application and provider application.
 It is called "Description Data Syntax"
 
 To generate it you have to use following functions.
@@ -58,8 +58,8 @@ dynamicbox_desc_close(desc_handle);
 desc_handle = NULL;
 @endcode
 
-Only after you close the desc_handle, the provider will sends changes to the dynamic box manager service.
-And if it needs to propagates events to the home application, the home application will gets changes event.
+Only after you close the desc_handle, the provider will send changes to the dynamic box manager service.
+And if it needs to propagate events to the home application, the home application will get changes event.
 
 <H2>2. Window(buffer) type Dynamic Box</H2>
 
@@ -81,28 +81,28 @@ if (!win) {
 
 To create a window for dynamic box,
 You have to get the parent object using dynamicbox_get_evas_object().
-And after creates a window for dynamic box, you have to delete it.
+And after creating a window for dynamic box, you have to delete it.
 Its attributes will be passed to the newly created window. So you don't need keep the parent object anymore.
 
-After create a window, you can do what you want like an application.
+After creating a window, you can do what you want like an application.
 Creatig any core-control such as button, list, etc, ....
 
 <H2>3. Image type Dynamic Box</H2>
 This kind of dynamic box should create an image file using given Id.
 The Id's syntax is "file://ABS_PATH_OF_OUTPUT_FILE", so you should create an image file using this URI.
 The Id will be assigned to every dynamic box instances.
-And those are uniq.
+And those are unique.
 
 If you create an image file, you should notify it to the viewer using dynamicbox_provider_app_dbox_updated()
 it is provided by libdynamicbox_provider_app package.
 
 <H2>4. Text type Dynamic Box (Experimental)</H2>
 In case of text type, you may have no window or script file.
-The text type dynamic box only needs to generates content data using dynamicbox_desc_XXXX series APIs.
+The text type dynamic box only needs to generate content data using dynamicbox_desc_XXXX series APIs.
 Of course, after you prepare the desc file, you have to call dynamicbox_provider_app_dbox_updated() function too.
-Then the viewer will gets your updated contents and try to parse it to locate content of dynamic box to its screen.
+Then the viewer will get your updated contents and try to parse it to locate content of dynamic box to its screen.
 But, unfortunately, this type of dynamic box is not fully supported yet.
-Because it is very highly depends on the viewer implementations.
+Because it very highly depends on the viewer implementations.
 So if the viewer doesn't support this type of dynamic box, you cannot do anything for user.
 
 To generate the text data, you can use below API set.