<itemizedlist>
<listitem><para>Whenever a shared state package is written out, so is a
corresponding <filename>.siginfo</filename> file.
- This practice results in a pickled python database of all
+ This practice results in a pickled Python database of all
the metadata that went into creating the hash for a given shared state
package.</para></listitem>
- <listitem><para>If BitBake is run with the <filename>--dump-signatures</filename>
+ <listitem><para>If you run BitBake with the <filename>--dump-signatures</filename>
(or <filename>-S</filename>) option, BitBake dumps out
<filename>.siginfo</filename> files in
the stamp directory for every task it would have executed instead of
building the specified target package.</para></listitem>
<listitem><para>There is a <filename>bitbake-diffsigs</filename> command that
- can process these <filename>.siginfo</filename> files.
- If one file is specified, it will dump out the dependency
+ can process <filename>.siginfo</filename> files.
+ If you specify one of these files, BitBake dumps out the dependency
information in the file.
- If two files are specified, it will compare the two files and dump out
+ If you specify two files, BitBake compares the two files and dumps out
the differences between the two.
- This allows the question of "What changed between X and Y?" to be
- answered easily.</para></listitem>
+ This more easily helps answer the question of "What
+ changed between X and Y?"</para></listitem>
</itemizedlist>
</para>
</section>