docs: add more more code-tags

It's easier to read function-names, file-names and other
"machine"-related strings if they are formatted in a monospace font. So
let's mark these up with code-tags.

Signed-off-by: Erik Faye-Lund <[email protected]>
Reviewed-by: Emil Velikov <[email protected]>
Reviewed-by: Eric Engestrom <[email protected]>

1 files changed, 12 insertions, 12 deletions

diff --git a/docs/devinfo.html b/docs/devinfo.html
index 07d154bb5e5..a636e37ad35 100644
--- a/docs/devinfo.html
+++ b/docs/devinfo.html
@@ -29,8 +29,8 @@ To add a new GL extension to Mesa you have to do at least the following.
 
 <ul>
 <li>
-   If glext.h doesn't define the extension, edit include/GL/gl.h and add
-   code like this:
+   If <code>glext.h</code> doesn't define the extension, edit
+   <code>include/GL/gl.h</code> and add code like this:
    <pre>
      #ifndef GL_EXT_the_extension_name
      #define GL_EXT_the_extension_name 1
@@ -41,18 +41,18 @@ To add a new GL extension to Mesa you have to do at least the following.
    </pre>
 </li>
 <li>
-   In the src/mapi/glapi/gen/ directory, add the new extension functions and
-   enums to the gl_API.xml file.
+   In the <code>src/mapi/glapi/gen/</code> directory, add the new extension
+   functions and enums to the <code>gl_API.xml</code> file.
    Then, a bunch of source files must be regenerated by executing the
    corresponding Python scripts.
 </li>
 <li>
-   Add a new entry to the <code>gl_extensions</code> struct in mtypes.h
-   if the extension requires driver capabilities not already exposed by
-   another extension.
+   Add a new entry to the <code>gl_extensions</code> struct in
+   <code>mtypes.h</code> if the extension requires driver capabilities not
+   already exposed by another extension.
 </li>
 <li>
-   Add a new entry to the src/mesa/main/extensions_table.h file.
+   Add a new entry to the <code>src/mesa/main/extensions_table.h</code> file.
 </li>
 <li>
    From this point, the best way to proceed is to find another extension,
@@ -65,13 +65,13 @@ To add a new GL extension to Mesa you have to do at least the following.
 </li>
 <li>
    To determine if the new extension is active in the current context,
-   use the auto-generated _mesa_has_##name_str() function defined in
-   src/mesa/main/extensions.h.
+   use the auto-generated <code>_mesa_has_##name_str()</code> function
+   defined in <code>src/mesa/main/extensions.h</code>.
 </li>
 <li>
-   The dispatch tests check_table.cpp and dispatch_sanity.cpp
+   The dispatch tests check_table.cpp and <code>dispatch_sanity.cpp</code>
    should be updated with details about the new extensions functions. These
-   tests are run using 'meson test'
+   tests are run using <code>meson test</code>.
 </li>
 </ul>