diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 1f04930b9f..aee30ae455 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -692,7 +692,7 @@
wiki page.
The requirements for the BSP as it is made available to a developer
are completely independent of the released form of the BSP.
- For example, the BSP metadata can be contained within a Git repository
+ For example, the BSP Metadata can be contained within a Git repository
and could have a directory structure completely different from what appears
in the officially released BSP layer.
It is not required that specific packages or package
@@ -741,12 +741,12 @@
recipes.
The recipes themselves should follow the general guidelines
for recipes used in the Yocto Project found in the
- Yocto
- Recipe and Patch Style Guide.
+ "Yocto Recipe and Patch Style Guide".
+
License File:
You must include a license file in the
meta-<bsp_name> directory.
- This license covers the BSP metadata as a whole.
+ This license covers the BSP Metadata as a whole.
You must specify which license to use since there is no
default license if one is not specified.
See the
@@ -775,11 +775,15 @@
For example, this information includes information on
special variables needed to satisfy a EULA,
or instructions on information needed to build or distribute
- binaries built from the BSP metadata.
+ binaries built from the BSP Metadata.
The name and contact information for the
BSP layer maintainer.
This is the person to whom patches and questions should
- be sent.
+ be sent.
+ For information on how to find the right person, see the
+ "How to Submit a Change"
+ section in the Yocto Project Development Manual.
+
Instructions on how to build the BSP using the BSP
layer.
Instructions on how to boot the BSP build from
@@ -822,7 +826,7 @@
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
+ files, and to possibly generate BSPs targeted for release
from that directory using scripts or some other mechanism.
Such considerations are outside the scope of this document.