ref-manual: Edits to image_types class.

Noticed that this class file name is "image_types.bbclass" and not
"image-types.bbclass".  Fixed it.

(From yocto-docs rev: 594cc933c919b7b84248c670ed7563bd23b8597d)

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

1 files changed, 5 insertions, 5 deletions

diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index d65ac0b0bd..2cc962eead 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -940,11 +940,11 @@
     </para>
 </section>
 
-<section id='ref-classes-image-types'>
-    <title><filename>image-types.bbclass</filename></title>
+<section id='ref-classes-image_types'>
+    <title><filename>image_types.bbclass</filename></title>
 
     <para>
-        The image types (<filename>image-types</filename>) class defines all of
+        The image types (<filename>image_types</filename>) class defines all of
         the standard image output types that you can enable through the
         <link linkend='var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></link>
         variable.
@@ -959,8 +959,8 @@
         <link linkend='ref-classes-image'><filename>image.bbclass</filename></link>.
         If you define your own image types using a custom BitBake class and
         then use <filename>IMAGE_CLASSES</filename> to enable it, the custom
-        class must either inherit <filename>image-types</filename> or
-        <filename>image-types</filename> must also appear in
+        class must either inherit <filename>image_types</filename> or
+        <filename>image_types</filename> must also appear in
         <filename>IMAGE_CLASSES</filename>.
     </para>
 </section>