aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoshua Lock <josh@linux.intel.com>2010-06-08 17:23:22 +0100
committerJoshua Lock <josh@linux.intel.com>2010-06-08 17:29:56 +0100
commit79f330c6c9be1a68e5e201948b9b08e3aef687fb (patch)
treea1ca7c4de209137091810df1927adef17087777d
parent3a6948a2af25c1094b22a70c923dfecc296dad8b (diff)
downloadopenembedded-core-contrib-79f330c6c9be1a68e5e201948b9b08e3aef687fb.tar.gz
openembedded-core-contrib-79f330c6c9be1a68e5e201948b9b08e3aef687fb.tar.bz2
openembedded-core-contrib-79f330c6c9be1a68e5e201948b9b08e3aef687fb.zip
handbook: point out required Python version
Signed-off-by: Joshua Lock <josh@linux.intel.com>
-rw-r--r--handbook/usingpoky.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/handbook/usingpoky.xml b/handbook/usingpoky.xml
index d54765c786..07b8f6c939 100644
--- a/handbook/usingpoky.xml
+++ b/handbook/usingpoky.xml
@@ -27,7 +27,7 @@
and configuration data for machines, policy decisions, etc., which acts as
a glue and binds everything together. Bitbake knows how to combine multiple
data sources together, each data source being referred to as a <link
- linkend='usingpoky-changes-collections'>'collection'</link>.
+ linkend='usingpoky-changes-layers'>'layer'</link>.
</para>
<para>