[SAMPLE APP][LIBOAUTH] Changes in sample app guide with respect to the libOAith appli...

Change-Id: I173039ee88249abf749a78a98b7bfa8ee4df216c
Signed-off-by: harsh.v <harsh.v@samsung.com>

diff --git a/org.tizen.sampledescriptions/html/mobile_n/oauth_sd_mn.htm b/org.tizen.sampledescriptions/html/mobile_n/oauth_sd_mn.htm
index 0d2055a..4ce8fc8 100644 (file)
--- a/org.tizen.sampledescriptions/html/mobile_n/oauth_sd_mn.htm
+++ b/org.tizen.sampledescriptions/html/mobile_n/oauth_sd_mn.htm
@@ -43,17 +43,18 @@ figure figcaption {
 <p align="center"> <img alt="OAuth main view" src="../images/oauth_main.png"/> </p>
 
 <h2>Prerequisites</h2>
+<p><b>The dummy consumer key and dummy consumer secret in the oauth_provider_configs.h should be replaced with respective App Id and App secret in the LibOAuthSampleApp. Refer to the respective service owner to get the keys.</b></p>
+<p>The App Id and App secret should be obtained from the respective resource owner provider and is out of scope of OAuth library service.</p>
+
+<p>The system time in the deice should be adjusted to the respective time zone and the time should be accurate.</p>
+<p>Internet connection should be enabled in the device.</p>
+
 <p>To ensure proper application execution, the following privileges must be set:</p>
  <ul>
   <li><span style="font-family: Courier New,Courier,monospace">http://tizen.org/privilege/network.get</span></li>
   <li><span style="font-family: Courier New,Courier,monospace">http://tizen.org/privilege/internet</span></li>
  </ul>
 
-<p>Internet connection should be enabled in the device.</p>
-<p>The system time in the deice should be adjusted to the respective time zone and the time should be accurate.</p>
-<p>The App Id and App secret should be obtained from the respective resource owner provider and is out of scope of OAuth1.0 library service.</p>
-
-
 <h2 id="implementation" name="implementation">Implementation</h2>
 
 <p>The OAuth 1.0 specification is defined in <a href="http://tools.ietf.org/html/rfc5849" target="_blank">[RFC 5849]</a> and it builds on the OAuth 1.0 <a href="http://tools.ietf.org/html/rfc5849" target="_blank">[RFC 5849]</a> deployment experience, as well as additional use cases and extensibility requirements gathered from the wider IETF community.</p>