dev-manual: Applied review edits to the 'wic' section.

I made some small edits to the section based on Tom Zanussi's
review.

(From yocto-docs rev: 560ea7b0eb131e59b190a34cadbe77729e76d61c)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-07-31 09:23:00 +03:00 committed by Richard Purdie
parent 73abcb0b16
commit 3be4af9cf3
1 changed files with 9 additions and 8 deletions

View File

@ -3560,12 +3560,12 @@
have already created an image using the
Openembedded build system (e.g.
<filename>core-image-minimal</filename>).
It might seem redundant to generate an image in
While it might seem redundant to generate an image in
order to create an image using
<filename>wic</filename>, but in the current
version <filename>wic</filename>, the artifacts
are needed in the form generated by the build
system.</para></listitem>
<filename>wic</filename>, the current version of
<filename>wic</filename> requires the artifacts
in the form generated by the build system.
</para></listitem>
<listitem><para>
You must have sourced one of the build environment
setup scripts (i.e.
@ -4182,7 +4182,8 @@
The code that then needs to call the plugin methods uses
<filename>plugin.get_source_plugin_methods()</filename>
to find the method or methods needed by the call.
Location is accomplished by filling up a dict with keys
Retrieval of those methods is accomplished is accomplished
by filling up a dict with keys
containing the method names of interest.
On success, these will be filled in with the actual
methods.
@ -4205,7 +4206,7 @@
The following is a list of the commands, their syntax,
and meanings.
The commands are based on the Fedora
kickstart documentation but with modifications to
kickstart versions but with modifications to
reflect <filename>wic</filename> capabilities.
You can see the original documentation for those commands
at the following links:
@ -4356,7 +4357,7 @@
means of modifying bootloader configuration.
</para>
<para>
Future updates will implement more options.
Future updates will implement more commands and options.
If you use anything that is not specifically
supported, results can be unpredictable.</para>
</note>