ref-manual, adt-manual: Minor edits from review.

Fixed some wordings in the ADT manual to remove "Intel-based"
so as not to be biased.

Added "x86" to qualify the types of systems in the toolchain
examples.

Added minor wording to the IMAGE_TYPES variable.

Changed some wording for the IPK_FEED_URIS varilable.

(From yocto-docs rev: 1fa7e0000591bec7e3d0b682df02b95dbee3d4f1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 343b741e1b..54f48a8507 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -253,9 +253,9 @@
                             <para>Go into that folder and download the toolchain
                             installer whose name includes the appropriate target
                             architecture.
-                            For example, if your host development system is an
-                            Intel-based 64-bit system and you are going to use
-                            your cross-toolchain for an Intel-based 32-bit
+                            For example, if your host development system is a
+                            64-bit x86 system and you are going to use
+                            your cross-toolchain for a 32-bit x86
                             target, go into the <filename>x86_64</filename>
                             folder and download the following installer:
                             <literallayout class='monospaced'>
@@ -263,7 +263,7 @@
                             </literallayout></para></listitem>
                         <listitem><para>Build your own toolchain installer.
                             For cases where you cannot use an installer
-                            from the download area, you can build your as
+                            from the download area, you can build your own as
                             described in the
                             "<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>"
                             section.</para></listitem>
@@ -273,8 +273,8 @@
                     You must change the permissions on the toolchain installer
                     script so that it is executable.</para>
                     <para>The following command shows how to run the installer
-                    given a toolchain tarball for a 64-bit development host
-                    system and a 32-bit target architecture.
+                    given a toolchain tarball for a 64-bit x86 development host
+                    system and a 32-bit x86 target architecture.
                     The example assumes the toolchain installer is located
                     in <filename>~/Downloads/</filename>.
                     <literallayout class='monospaced'>