summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index aeb89024aa..3eb8febefa 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2710,10 +2710,10 @@
<title>Trim the Kernel</title>
<para>
- Kernel is built by including policies for hardware-independent
+ The kernel is built by including policies for hardware-independent
aspects.
What subsystems do you enable?
- What architecture are you building for?
+ For what architecture are you building?
Which drivers do you build by default.
<note>You can modify the kernel source if you want to help
with boot time.
@@ -2737,7 +2737,7 @@
will be smaller by a relatively constant factor in a compressed
kernel image.
Look to reduce the areas that are large and taking up around
- the "90% rule".
+ the "90% rule."
</para>
<para>
@@ -2760,7 +2760,7 @@
<para>
After figuring out what to eliminate, you need to reconfigure
- kernel to reflect those changes during the next build.
+ the kernel to reflect those changes during the next build.
You could run <filename>menuconfig</filename> and make all your
changes at once.
However, that makes it difficult to see the effects of your
@@ -2772,7 +2772,7 @@
fragments into a single configuration file using
<filename>merge_config.sh</filename>.
The tool makes it easy for you to iterate using the
- configuration change/build cycle.
+ configuration change and build cycle.
</para>
<para>