documentation: Config fragment sections updated

I have updated both the section for configuration fragments found
in the BSP and dev manuals.

Reported-by: James Abernathy <jabernathy@gmail.com>
(From yocto-docs rev: 62f4df751c80e7b749356bb80ade3a7847411f7c)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 11 insertions, 11 deletions

diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 0159f48848..05094ca77d 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -596,22 +596,22 @@
             </para>
 
             <para>
-                For example, suppose you had a set of configuration options in a file called 
-                <filename>myconfig.cfg</filename>.  
-                If you put that file inside a directory named <filename>/linux-yocto</filename> and then added 
-                a <filename>SRC_URI</filename> statement such as the following to the append file, 
-                those configuration options will be picked up and applied when the kernel is built.
+                For example, suppose you had a some configuration options in a file called 
+                <filename>network_configs.cfg</filename>.  
+                You can place that file inside a directory named <filename>/linux-yocto</filename> and then add 
+                a <filename>SRC_URI</filename> statement such as the following to the append file.
+                When the OpenEmbedded build system builds the kernel, the configuration options are 
+                picked up and applied.
                 <literallayout class='monospaced'>
-     SRC_URI += "file://myconfig.cfg"
+     SRC_URI += "file://network_configs.cfg"
                 </literallayout>
             </para>
 
             <para>
-                As mentioned earlier, you can group related configurations into multiple files and 
-                name them all in the <filename>SRC_URI</filename> statement as well.
-                For example, you could group separate configurations specifically for Ethernet and graphics
-                into their own files and add those by using a <filename>SRC_URI</filename> statement like the 
-                following in your append file:
+                To group related configurations into multiple files, you perform a similar procedure. 
+                Here is an example that groups separate configurations specifically for Ethernet and graphics
+                into their own files and adds the configurations
+                by using a <filename>SRC_URI</filename> statement like the following in your append file:
                 <literallayout class='monospaced'>
      SRC_URI += "file://myconfig.cfg \
             file://eth.cfg \