summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/faq.rst2
-rw-r--r--documentation/ref-manual/faq.xml2
-rw-r--r--documentation/ref-manual/ref-images.rst4
-rw-r--r--documentation/ref-manual/ref-images.xml4
-rw-r--r--documentation/ref-manual/ref-terms.rst2
-rw-r--r--documentation/ref-manual/ref-terms.xml2
6 files changed, 8 insertions, 8 deletions
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst
index 04066e9202..2d2aaad0a9 100644
--- a/documentation/ref-manual/faq.rst
+++ b/documentation/ref-manual/faq.rst
@@ -143,7 +143,7 @@ various proxy types and configuring proxy servers, see the
143":yocto_wiki:`Working Behind a Network Proxy </wiki/Working_Behind_a_Network_Proxy>`" 143":yocto_wiki:`Working Behind a Network Proxy </wiki/Working_Behind_a_Network_Proxy>`"
144Wiki page. 144Wiki page.
145 145
146**Q:** Whats the difference between target and target\ ``-native``? 146**Q:** What's the difference between target and target\ ``-native``?
147 147
148**A:** The ``*-native`` targets are designed to run on the system being 148**A:** The ``*-native`` targets are designed to run on the system being
149used for the build. These are usually tools that are needed to assist 149used for the build. These are usually tools that are needed to assist
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index 98ae0a975b..2f8fcf3242 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -323,7 +323,7 @@
323 <qandaentry> 323 <qandaentry>
324 <question> 324 <question>
325 <para> 325 <para>
326 What’s the difference between <replaceable>target</replaceable> and <replaceable>target</replaceable><filename>-native</filename>? 326 What's the difference between <replaceable>target</replaceable> and <replaceable>target</replaceable><filename>-native</filename>?
327 </para> 327 </para>
328 </question> 328 </question>
329 <answer> 329 <answer>
diff --git a/documentation/ref-manual/ref-images.rst b/documentation/ref-manual/ref-images.rst
index 47beda0c23..f0229c3bb7 100644
--- a/documentation/ref-manual/ref-images.rst
+++ b/documentation/ref-manual/ref-images.rst
@@ -6,7 +6,7 @@ Images
6 6
7The OpenEmbedded build system provides several example images to satisfy 7The OpenEmbedded build system provides several example images to satisfy
8different needs. When you issue the ``bitbake`` command you provide a 8different needs. When you issue the ``bitbake`` command you provide a
9top-level recipe that essentially begins the build for the type of 9"top-level" recipe that essentially begins the build for the type of
10image you want. 10image you want.
11 11
12.. note:: 12.. note::
@@ -85,7 +85,7 @@ Following is a list of supported recipes:
85 85
86- ``core-image-minimal-initramfs``: A ``core-image-minimal`` image that 86- ``core-image-minimal-initramfs``: A ``core-image-minimal`` image that
87 has the Minimal RAM-based Initial Root Filesystem (initramfs) as part 87 has the Minimal RAM-based Initial Root Filesystem (initramfs) as part
88 of the kernel, which allows the system to find the first init 88 of the kernel, which allows the system to find the first "init"
89 program more efficiently. See the 89 program more efficiently. See the
90 :term:`PACKAGE_INSTALL` variable for 90 :term:`PACKAGE_INSTALL` variable for
91 additional information helpful when working with initramfs images. 91 additional information helpful when working with initramfs images.
diff --git a/documentation/ref-manual/ref-images.xml b/documentation/ref-manual/ref-images.xml
index aaeda55226..6f10a6fd2a 100644
--- a/documentation/ref-manual/ref-images.xml
+++ b/documentation/ref-manual/ref-images.xml
@@ -9,7 +9,7 @@
9 <para> 9 <para>
10 The OpenEmbedded build system provides several example 10 The OpenEmbedded build system provides several example
11 images to satisfy different needs. 11 images to satisfy different needs.
12 When you issue the <filename>bitbake</filename> command you provide a top-level recipe 12 When you issue the <filename>bitbake</filename> command you provide a "top-level" recipe
13 that essentially begins the build for the type of image you want. 13 that essentially begins the build for the type of image you want.
14 </para> 14 </para>
15 15
@@ -100,7 +100,7 @@
100 <listitem><para id='images-core-image-minimal-initramfs'><filename>core-image-minimal-initramfs</filename>: 100 <listitem><para id='images-core-image-minimal-initramfs'><filename>core-image-minimal-initramfs</filename>:
101 A <filename>core-image-minimal</filename> image that has the Minimal RAM-based 101 A <filename>core-image-minimal</filename> image that has the Minimal RAM-based
102 Initial Root Filesystem (initramfs) as part of the kernel, 102 Initial Root Filesystem (initramfs) as part of the kernel,
103 which allows the system to find the first init program more efficiently. 103 which allows the system to find the first "init" program more efficiently.
104 See the 104 See the
105 <link linkend='var-PACKAGE_INSTALL'><filename>PACKAGE_INSTALL</filename></link> 105 <link linkend='var-PACKAGE_INSTALL'><filename>PACKAGE_INSTALL</filename></link>
106 variable for additional information helpful when working with 106 variable for additional information helpful when working with
diff --git a/documentation/ref-manual/ref-terms.rst b/documentation/ref-manual/ref-terms.rst
index 312fc12ef0..6e7e5169ce 100644
--- a/documentation/ref-manual/ref-terms.rst
+++ b/documentation/ref-manual/ref-terms.rst
@@ -273,7 +273,7 @@ universal, the list includes them just in case:
273 Arbitrary groups of software Recipes. You use 273 Arbitrary groups of software Recipes. You use
274 package groups to hold recipes that, when built, usually accomplish a 274 package groups to hold recipes that, when built, usually accomplish a
275 single task. For example, a package group could contain the recipes 275 single task. For example, a package group could contain the recipes
276 for a companys proprietary or value-add software. Or, the package 276 for a company's proprietary or value-add software. Or, the package
277 group could contain the recipes that enable graphics. A package group 277 group could contain the recipes that enable graphics. A package group
278 is really just another recipe. Because package group files are 278 is really just another recipe. Because package group files are
279 recipes, they end with the ``.bb`` filename extension. 279 recipes, they end with the ``.bb`` filename extension.
diff --git a/documentation/ref-manual/ref-terms.xml b/documentation/ref-manual/ref-terms.xml
index d2605c62a8..2a0452bd78 100644
--- a/documentation/ref-manual/ref-terms.xml
+++ b/documentation/ref-manual/ref-terms.xml
@@ -365,7 +365,7 @@
365 You use package groups to hold recipes that, when built, 365 You use package groups to hold recipes that, when built,
366 usually accomplish a single task. 366 usually accomplish a single task.
367 For example, a package group could contain the recipes for a 367 For example, a package group could contain the recipes for a
368 companys proprietary or value-add software. 368 company's proprietary or value-add software.
369 Or, the package group could contain the recipes that enable 369 Or, the package group could contain the recipes that enable
370 graphics. 370 graphics.
371 A package group is really just another recipe. 371 A package group is really just another recipe.