Cherry pick from Honeycomb-mr2 Change ID Id87a6000de458a1d3e4ac11aaf64355a244f2f07

sdk doc change: updated intro to developing and removed reference to G1
Bug: 4483863

Change-Id: Ic8d342145ed909ee5592e93a3055887e478a5688

diff --git a/docs/html/guide/developing/index.jd b/docs/html/guide/developing/index.jd
index 3d7e353..722c75a 100644 (file)
--- a/docs/html/guide/developing/index.jd
+++ b/docs/html/guide/developing/index.jd
@@ -98,20 +98,22 @@ information.
 
     <dt>Jarsigner (or similar signing tool)</dt>
 
-    <dd>To sign your .apk file with a private key generated by keytool. Jarsigner is part of the
+    <dd>To sign your .apk file with a private key generated by Keytool. Jarsigner is part of the
     JDK.</dd>
   </dl>
   
-  <p>If you are using Eclipse and ADT, tools such as <code>adb</code> and the <code>android</code>
-  are called by Eclipse and ADT under the hood or similar functionality is provided within Eclipse.
-  You need to be familiar with <code>adb</code>, however, because certain functions are not accessible from
-  Eclipse, such as the <code>adb</code> shell commands. You might also need to call Keytool and Jarsigner to
+  <p>If you are using Eclipse and ADT, tools such as <code>adb</code> and <code>android</code>
+  are automatically called by Eclipse and ADT so you don't have to manually invoke these tools.
+  You need to be familiar with <code>adb</code>, however, because certain functions are not
+accessible from
+  Eclipse, such as the <code>adb</code> shell commands. You might also need to call Keytool and
+Jarsigner to
   sign your applications, but you can set up Eclipse to do this automatically as well.</p>
   
 <p>For more information on the tools provided with the Android SDK, see the
   <a href="{@docRoot}guide/developing/tools/index.html">Tools</a> section of the documentation.</p>
   
-<h2 id="ThirdParty">Third-Party Development Tools</h2>
+<h2 id="ThirdParty">Other Third-Party Development Tools</h2>
 <p>
        The tools described in this section are not developed by the Android SDK team. The Android Dev Guide
            does not provide documentation for these tools. Please refer to the linked documents in each

diff --git a/docs/html/guide/publishing/preparing.jd b/docs/html/guide/publishing/preparing.jd
index f471961..69aecd4 100644 (file)
--- a/docs/html/guide/publishing/preparing.jd
+++ b/docs/html/guide/publishing/preparing.jd
@@ -78,9 +78,6 @@ device to the greatest extent possible. You can then test your application's UI
 and performance. However, we strongly recommend that you test your application
 on an actual target device before publishing it. </li>
 
-<li>If you are targeting the <a href="http://www.t-mobileg1.com/">T-Mobile
-G1</a> device for your application, make sure that your UI handles screen
-orientation changes. </li>
 </ul>
 
 <h3 id="eula">2. Consider adding an End User License Agreement in your