ref-manual: Edits to bugzilla and deploy class.

Fixed a link in the deploy class.
Re-wrote the bugzilla class to be clearer.

(From yocto-docs rev: 4bb975a0e12c9d38e941f1cf913c042498f06976)

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

1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index a5a906d..965302f 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -291,11 +291,11 @@
     <title><filename>bugzilla.bbclass</filename></title>
 
     <para>
-        The <filename>bugzilla</filename> class automatically files bug reports
-        to a Bugzilla instance in response to build failures.
-        This class uses Bugzilla's XML-RPC interface.
-        Consequently, you need to enable the class in the instance of Bugzilla
-        within which you wish to file reports.
+        The <filename>bugzilla</filename> class supports setting up an
+        instance of Bugzilla in which you can automatically files bug reports
+        in response to build failures.
+        For this class to work, you need to enable the XML-RPC interface in
+        the instance of Bugzilla.
     </para>
 </section>
 
@@ -529,7 +529,7 @@
         Recipes that inherit this class should define their own
         <filename>do_deploy</filename> function to copy the files to be
         deployed to
-        <link linkend='var-DEPLOY_DIR'><filename>DEPLOYDIR</filename></link>,
+        <link linkend='var-DEPLOYDIR'><filename>DEPLOYDIR</filename></link>,
         and use <filename>addtask</filename> to add the task at the appropriate
         place, which is usually after <filename>do_compile</filename> or
         <filename>do_install</filename>.