* "sys" filesystem is technically "sysfs" filesystem
* "aggregate" already implies together :-)
Signed-off-by: Robert P. J. Day <rpj...@crashcourse.ca>
---
diff --git a/documentation/kernel-dev/kernel-dev-intro.xml
b/documentation/kernel-dev/kernel-dev-intro.xml
index 263e500..8de1f97 100644
--- a/documentation/kernel-dev/kernel-dev-intro.xml
+++ b/documentation/kernel-dev/kernel-dev-intro.xml
@@ -74,17 +74,17 @@
visible <filename>CONFIG</filename> options as presented by the
Linux
kernel <filename>menuconfig</filename> system.
Contrast this against a complete Linux kernel
- <filename>.config</filename>, which includes all the automatically
+ <filename>.config</filename> file, which includes all the
automatically
selected <filename>CONFIG</filename> options.
This efficiency reduces your maintenance effort and allows you
to further separate your configuration in ways that make sense for
your project.
A common split separates policy and hardware.
For example, all your kernels might support
- the <filename>proc</filename> and <filename>sys</filename>
filesystems,
+ the <filename>proc</filename> and <filename>sysfs</filename>
filesystems,
but only specific boards require sound, USB, or specific drivers.
Specifying these configurations individually allows you to
aggregate
- them together as needed, but maintains them in only one place.
+ them as needed, but maintains them in only one place.
Similar logic applies to separating source changes.
</para>
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
