[gnome-devel-docs/wip/swilmet/prog-guidelines: 3/3] programming-guidelines: add some missing markup in documentation.page

[Sébastien Wilmet <swilmet src gnome org>]

commit b6b97a061c1102197c47f56821ddde851e8ccdac
Author: Sébastien Wilmet <swilmet gnome org>
Date:   Wed Nov 11 11:00:48 2015 +0100

    programming-guidelines: add some missing markup in documentation.page
    
    While I'm at it.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=757736

 programming-guidelines/C/documentation.page |    9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)
---
diff --git a/programming-guidelines/C/documentation.page b/programming-guidelines/C/documentation.page
index 57c45d9..3a5f6cd 100644
--- a/programming-guidelines/C/documentation.page
+++ b/programming-guidelines/C/documentation.page
@@ -215,14 +215,15 @@ gtk_get_flow (GtkWidget *widget)
     <p>
       Keep in mind that in order to include a function, macro,
       function type, or struct type, it needs to be listed in your
-      documentation’s modulename-sections.txt file.
+      documentation’s <file>modulename-sections.txt</file> file.
     </p>
 
     <p>
       To properly document a new class, it needs to be given its own
-      section in modulename-sections.txt, needs to be included in your
-      toplevel modulename-docs.sgml, and the get_type() function for
-      your class needs to listed in your modulename.types.
+      section in <file>modulename-sections.txt</file>, needs to be
+      included in your toplevel <file>modulename-docs.sgml</file>,
+      and the <code>get_type()</code> function for your class needs
+      to be listed in your <file>modulename.types</file>.
     </p>
   </section>