final corrections from Guido

LDP/inprogress/Linux-Android-HOWTO.sgml

@@ -88,6 +88,33 @@ on my devices; hopefully, they should work on your device too. If you
 want me to cover more Android versions, I'll be glad to receive new
 equipment; or just tips. Equipment is preferred :-)
 
+<p>
+Currently, the majority of Android devices are ARM based; others are
+based on x86 or MIPS CPUs, in both 32 and 64 bit flavours. This is not
+a significant difference: most applications are written in Java with
+no native code, so they are CPU-agnostic. Instructions in this HOWTO
+should work for these Android versions, too. I guess that relevant
+differences concern security policies.
+
+<p>
+Should you have trouble with your Android device, I suggest that you
+refer to Android forums. Among the many available, I find the
+following especially helpful:
+
+<itemize>
+  
+  <item> <htmlurl url="http://forum.xda-developers.com/"
+  name="http://forum.xda-developers.com/">
+
+  <item> <htmlurl url="http://forums.androidcentral.com/"
+  name="http://forums.androidcentral.com/">
+
+</itemize>
+
+<p>
+Besides: if you find any error in this guide, please report them to
+me.
+
 <p>
 Thoughout this HOWTO, all instances of ``Linux'' actually mean
 ``GNU/Linux''. The GNU part is very important, and I'm very grateful
@@ -646,7 +673,7 @@ Linux:~$ _
 <p>
 An Andbox can easily share its installed programs with another
 device, provided that the Android versions are compatible. All you
-need is Ghost Commander.  In the next paragraph, you can see how to
+need is Ghost Commander. In the next paragraph, you can see how to
 send a file to Alice using Bob's Andbox.
 
 <p>
@@ -994,8 +1021,8 @@ come in handy.
 <sect1>Backing up applications
 
 <p>
-Installed pplications are stored in <tt>/data/apps/</tt>, which is
-inaccessible on unrooted devices.  You can, however, backup your
+Installed applications are stored in <tt>/data/apps/</tt>, which is
+inaccessible on unrooted devices. You can, however, backup your
 <tt>.apk</tt> files using Ghost Commander or the <tt>adb backup</tt>
 command. I prefer the former, which is way faster and more convenient
 (IMHO).
@@ -1405,7 +1432,8 @@ kbox$ _
 <p>
 Once you have a terminal emulator, you can add a lot of command-line
 based software to your Android box. If you're a geek, this is an
-invaluable extension; but even if you're a casual user, please read on.
+invaluable extension that makes your Andbox closer to a ``real''
+computer ; but even if you're a casual user, please read on.
 
 <p>
 You can compile C programs both on your Andbox and, obviously,
@@ -1425,7 +1453,12 @@ toolchain from the NDK home page:
 name="http://developer.android.com/ndk/downloads/index.html">
 
 <p>
-Download the binary package for Linux 32-bit or 64-bit. The directory
+Another toolchain that targets Android on x86 CPUs is called
+<tt>gcc-arm-linux-androideabi</tt>.
+
+<p>
+Choose the relevant architecture and download the binary package for
+Linux 32-bit or 64-bit. The directory
 
 <tscreen><verb>
 toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86/bin/
@@ -1433,12 +1466,13 @@ toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86/bin/
 
 <p>
 contains prebuilt binaries: include that directory in the
-<tt>$PATH</tt>.
+<tt>$PATH</tt>. MIPS and x86 binaries are also available.
 
 <p>
-The compiler is called <tt>arm-linux-androideabi-gcc</tt>. You use it
-instead of <tt>gcc</tt> to compile Android binaries. In general, all
-binutils have a <tt>arm-linux-androideabi-</tt> prefix.
+Supposing you're compiling for ARM, the compiler is called
+<tt>arm-linux-androideabi-gcc</tt>. You use it instead of <tt>gcc</tt>
+to compile Android binaries. In general, all binutils have a
+<tt>arm-linux-androideabi-</tt> prefix.
 
 <tscreen>
 <verb>
@@ -2023,3 +2057,4 @@ Enjoy,
 <tt>&nbsp;&nbsp;&nbsp;&nbsp;</tt>Guido <tt>=8-)</tt>
 
 </article>
+