summaryrefslogtreecommitdiffstats
path: root/docs/html/guide/publishing
diff options
context:
space:
mode:
authorThe Android Open Source Project <initial-contribution@android.com>2009-02-19 10:57:31 -0800
committerThe Android Open Source Project <initial-contribution@android.com>2009-02-19 10:57:31 -0800
commit3001a035439d8134a7d70d796376d1dfbff3cdcd (patch)
tree343ccdba15a594ff6e50c874a145232753315a30 /docs/html/guide/publishing
parentda996f390e17e16f2dfa60e972e7ebc4f868f37e (diff)
downloadframeworks_base-3001a035439d8134a7d70d796376d1dfbff3cdcd.zip
frameworks_base-3001a035439d8134a7d70d796376d1dfbff3cdcd.tar.gz
frameworks_base-3001a035439d8134a7d70d796376d1dfbff3cdcd.tar.bz2
auto import from //branches/cupcake/...@132276
Diffstat (limited to 'docs/html/guide/publishing')
-rw-r--r--docs/html/guide/publishing/preparing.jd20
-rw-r--r--docs/html/guide/publishing/versioning.jd4
2 files changed, 12 insertions, 12 deletions
diff --git a/docs/html/guide/publishing/preparing.jd b/docs/html/guide/publishing/preparing.jd
index 267cba2..4db546d 100644
--- a/docs/html/guide/publishing/preparing.jd
+++ b/docs/html/guide/publishing/preparing.jd
@@ -94,12 +94,12 @@ orientation changes. </li>
</ul>
<h3 id="eula">2. Consider adding an End User License Agreement in your
-application</h4>
+application</h3>
<p>To protect your person, organization, and intellectual property, you may want
to provide an End User License Agreement (EULA) with your application.
-<h3 id="iconlabel">3. Specify an icon and label in the application's manifest</h4>
+<h3 id="iconlabel">3. Specify an icon and label in the application's manifest</h3>
<p>The icon and label that you specify in an application's manifest are
important because they are displayed to users as your application's icon and
@@ -114,7 +114,7 @@ display the icon and label to users. </p>
<p>As regards the design of your icon, you should try to make it match as much
as possible the style used by the built-in Android applications.</p>
-<h3 id="logging">4. Turn off logging and debugging and clean up data/files</h4>
+<h3 id="logging">4. Turn off logging and debugging and clean up data/files</h3>
<p>For release, you should make sure that debug facilities are turned off and
that debug and other unnecessary data/files are removed from your application
@@ -129,9 +129,9 @@ application project.</li>
code.</li>
</ul>
-<h2 id="finalcompile">Before you do the final compile of your application</h3>
+<h2 id="finalcompile">Before you do the final compile of your application</h2>
-<h3 id="versionapp">5. Version Your Application</h4>
+<h3 id="versionapp">5. Version Your Application</h3>
<p>Before you compile your application, you must make sure that you have defined
a version number for your application, specifying an appropriate value for both
@@ -149,7 +149,7 @@ element in the application's manifest file, using appropriate values. </p>
<p>For detailed information about how to define version information for your
application, see <a href="{@docRoot}guide/publishing/versioning.html">Versioning Your Applications</a>.</p>
-<h3 id="cryptokey">6. Obtain a suitable cryptographic key</h4>
+<h3 id="cryptokey">6. Obtain a suitable cryptographic key</h3>
<p>If you have read and followed all of the preparation steps up to this point,
your application is compiled and ready for signing. Inside the .apk, the
@@ -222,20 +222,20 @@ to download Maps data. </li>
href="#signing">Signing Your Applications</a>.</p>
-<h2 id="compile">Compile Your Application</h3>
+<h2 id="compile">Compile Your Application</h2>
<p>When you've prepared your application as described in the previous sections,
you can compile your application for release. </p>
-<h2 id="post-compile">After Compiling Your Application</h3>
+<h2 id="post-compile">After Compiling Your Application</h2>
-<h3 id="signapp">8. Sign Your Application</h4>
+<h3 id="signapp">8. Sign Your Application</h3>
<p>Sign your application using your private key. Signing your application
correctly is critically important. Please see <a href="#signing">Signing Your
Applications</a> for complete information. </p>
-<h3 id="testapp">9. Test Your Compiled and Signed Application</h4>
+<h3 id="testapp">9. Test Your Compiled and Signed Application</h3>
<p>Before you release your compiled application, you should thoroughly test it
on the target mobile device (and target network, if possible). In particular,
diff --git a/docs/html/guide/publishing/versioning.jd b/docs/html/guide/publishing/versioning.jd
index d106266..d0eafcd 100644
--- a/docs/html/guide/publishing/versioning.jd
+++ b/docs/html/guide/publishing/versioning.jd
@@ -125,7 +125,7 @@ applications use the
{@link android.content.pm.PackageManager#getPackageInfo(java.lang.String, int)}
method of {@link android.content.pm.PackageManager PackageManager}. </p>
-<h2 id="#minsdkversion">Specifying Minimum System API Version</h2>.
+<h2 id="minsdkversion">Specifying Minimum System API Version</h2>
<p>If your application requires a specific minimum version of the Android
platform, you can specify that version as an API Level identifier
@@ -152,4 +152,4 @@ that your application is compatible with all platform versions.</p></li>
<code>&lt;manifest&gt;</code>, then define the
<code>android:minSdkVersion</code> as an attribute. </p>
-<p>For more information, also see the <a href="{@docRoot}sdk/android-1.1.html">Android System Image 1.1 Version Notes</a>.</p> \ No newline at end of file
+<p>For more information, also see the <a href="{@docRoot}sdk/android-1.1.html">Android System Image 1.1 Version Notes</a>.</p>