diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 1f1667114c..3732498873 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -400,8 +400,8 @@
For example, the Crown Bay BSP crownbay.conf has the
following statements:
- include conf/machine/include/tune-atom.inc
- include conf/machine/include/ia32-base.inc
+ require conf/machine/include/tune-atom.inc
+ require conf/machine/include/ia32-base.inc
@@ -739,7 +739,7 @@
A brief description about the hardware the BSP
targets.
- A list of all the dependencies a
+ A list of all the dependencies
on which a BSP layer depends.
These dependencies are typically a list of required layers needed
to build the BSP.
@@ -787,14 +787,13 @@
using the BSP layer.
Multiple machine configuration files define variations of machine
configurations that are supported by the BSP.
- If a BSP supports more multiple machine variations, you need to
+ If a BSP supports multiple machine variations, you need to
adequately describe each variation in the BSP
README file.
Do not use multiple machine configuration files to describe disparate
hardware.
- Multiple machine configuration files should describe very similar targets.
- If you do have very different targets, you should create a separate
- BSP.
+ If you do have very different targets, you should create separate
+ BSP layers for each target.
It is completely possible for a developer to structure the
working repository as a conglomeration of unrelated BSP
files, and to possibly generate specifically targeted 'release' BSPs