[2.4][online-doc][push] Modified the image of service architecture and clarified...

Change-Id: Idfdadac8195639f1c2577a6a61dae29c46583c49
Signed-off-by: Younho Park <younho.park@samsung.com>

diff --git a/org.tizen.guides/html/images/push_overview.png b/org.tizen.guides/html/images/push_overview.png
new file mode 100644 (file)
index 0000000..1d14cea
Binary files /dev/null and b/org.tizen.guides/html/images/push_overview.png differ

diff --git a/org.tizen.guides/html/native/messaging/push_n.htm b/org.tizen.guides/html/native/messaging/push_n.htm
index 558b452..c18f468 100644 (file)
--- a/org.tizen.guides/html/native/messaging/push_n.htm
+++ b/org.tizen.guides/html/native/messaging/push_n.htm
@@ -56,20 +56,20 @@
 \r
 <p>Push enables you to push events from an application server to your application on a Tizen device.</p> \r
 \r
-  <p>Once your application is successfully registered in the push server through the push daemon on the device, your application server can send push messages to the application in that particular device.</p> \r
-  <p>When a push message arrives when the application is running, it is automatically delivered to the application. If not, the daemon makes a sound or vibrates and adds a ticker or a badge notification to notify the user. By touching this notification, the user can check the message. The application server may send a message with a <span style="font-family: Courier New,Courier,monospace">LAUNCH</span> option. In this case, the daemon forcibly launches the application and hands over the message to the application as an <a href="../app_management/app_controls_n.htm">application control</a>.</p>\r
+  <p>Once your application is successfully registered in the push server through the push service(daemon) on the device, your application server can send push messages to the application in that particular device.</p>\r
+  <p>When a push message arrives when the application is running, it is automatically delivered to the application. If not, the push service makes a sound or vibrates and adds a ticker or a badge notification to notify the user. By touching this notification, the user can check the message. The application server may send a message with a <span style="font-family: Courier New,Courier,monospace">LAUNCH</span> option. In this case, the push service forcibly launches the application and hands over the message to the application as an <a href="../app_management/app_controls_n.htm">application control</a>.</p>\r
 \r
 <p>To use the push messaging service, the application needs the permission to access the Tizen push server. Request the permission from the Tizen push service team by <a href="mailto:push.tizen@samsung.com">email</a>, including the <a href="#request_form">necessary information</a>. When the team approves the request, you receive a push app ID corresponding to your package ID.</p>\r
 \r
 <p>Remember to <a href="#security">take care of security issues</a> when sending notifications with sensitive information.</p>\r
 \r
   <p class="figure">Figure: Push messaging service</p> \r
-  <p align="center"><img alt="Push messaging service" src="../../images/ui_push_message.png" /></p> \r
+  <p align="center"><img alt="Push messaging service" src="../../images/ui_push_message.png" /></p>\r
 \r
   <h2 id="service" name="service">Service Architecture</h2> \r
   <p>The following figure illustrates the service architecture of the Tizen push messaging service.</p> \r
   <p class="figure">Figure: Service architecture</p> \r
-  <p align="center"><img alt="Service architecture" src="../../images/service_architecture.png" /></p> \r
+  <p align="center"><img alt="Service architecture" src="../../images/push_overview.png" /></p>\r
   <p>The following steps illustrate a typical scenario for using the push messaging service on a Tizen device:</p> \r
   <ol> \r
    <li>The application on the device registers for the push messaging service. Before you start, remember to <a href="#prerequisites">prepare your application to use the push functionality</a>.</li> \r