summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-model.xml3
-rw-r--r--documentation/ref-manual/migration.xml2
-rw-r--r--documentation/ref-manual/ref-classes.xml9
3 files changed, 7 insertions, 7 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 55bad34064..43c31b8405 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -295,8 +295,7 @@
<filename>linux-yocto-3.14</filename></emphasis> - The
stable Yocto Project kernel to use with the Yocto
Project Releases 1.6 and 1.7.
- These kernels are based on the Linux 3.14 and 3.17
- released kernels, respectively.
+ This kernel is based on the Linux 3.14 released kernel.
</para></listitem>
<listitem><para><emphasis>
<filename>linux-yocto-3.17</filename></emphasis> - An
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index dd8c3e00cc..f8bd852ad8 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -1759,7 +1759,7 @@
<para>
Some of the core recipes that package binary configuration scripts
- now disable the scripts instead due to the
+ now disable the scripts due to the
scripts previously requiring error-prone path substitution.
Software that links against these libraries using these scripts
should use the much more robust <filename>pkg-config</filename>
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 1b01ef61c9..496425a5a9 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -103,11 +103,11 @@
<para>
By default, the <filename>autotools</filename> class supports
- out-of-tree builds
+ using out-of-tree builds
(<link linkend='var-B'><filename>B</filename></link> <filename>!=</filename>
<link linkend='var-S'><filename>S</filename></link>).
- If your recipes do not support out-of-tree builds, you should
- have them inherit the
+ If the software being built by a recipe does not support
+ using out-of-tree builds, you should have the recipe inherit the
<link linkend='ref-classes-autotools-brokensep'><filename>autotools-brokensep</filename></link>
class.
</para>
@@ -116,7 +116,8 @@
It's useful to have some idea of how the tasks defined by this class work
and what they do behind the scenes.
<itemizedlist>
- <listitem><para><link linkend='ref-tasks-configure'><filename>do_configure</filename></link> &dash; Regenerates the
+ <listitem><para><link linkend='ref-tasks-configure'><filename>do_configure</filename></link> &dash;
+ Regenerates the
configure script (using <filename>autoreconf</filename>) and then launches it
with a standard set of arguments used during cross-compilation.
You can pass additional parameters to <filename>configure</filename> through the