[wwwdocs] faq.html -- replace <tt>

[Gerald Pfeifer <gerald at pfeifer dot com>]

...by <code>, rendering this page HTML 5 compliant.

Committed.

Gerald

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.229
diff -u -r1.229 faq.html
--- faq.html	1 Sep 2018 23:42:00 -0000	1.229
+++ faq.html	2 Sep 2018 21:34:39 -0000
@@ -217,23 +217,24 @@
 building GCC.</p>
 
 <p>Another alternative is to create links to GNU as and ld in any of
-the directories printed by the command `<tt>gcc -print-search-dirs |
-grep '^programs:'</tt>'.  The link to `<tt>ld</tt>' should be named
-`<tt>real-ld</tt>' if `<tt>ld</tt>' already exists.  If such links do
-not exist while you're compiling GCC, you may have to create them in
-the build directories too, within the <tt>gcc</tt> directory
-<em>and</em> in all the <tt>gcc/stage*</tt> subdirectories.</p>
+the directories printed by the command `<code>gcc -print-search-dirs |
+grep '^programs:'</code>'.  The link to `<code>ld</code>' should be named
+`<code>real-ld</code>' if `<code>ld</code>' already exists.  If such links
+do not exist while you're compiling GCC, you may have to create them in
+the build directories too, within the <code>gcc</code> directory
+<em>and</em> in all the <code>gcc/stage*</code> subdirectories.</p>
 
 <p>GCC 2.95 allows you to specify the full pathname of the assembler
 and the linker to use.  The configure flags are
-`<tt>--with-as=/path/to/as</tt>' and `<tt>--with-ld=/path/to/ld</tt>'.
-GCC will try to use these pathnames before looking for `<tt>as</tt>'
-or `<tt>(real-)ld</tt>' in the standard search dirs.  If, at
+`<code>--with-as=/path/to/as</code>' and
+`<code>--with-ld=/path/to/ld</code>'.
+GCC will try to use these pathnames before looking for `<code>as</code>'
+or `<code>(real-)ld</code>' in the standard search dirs.  If, at
 configure-time, the specified programs are found to be GNU utilities,
-`<tt>--with-gnu-as</tt>' and `<tt>--with-gnu-ld</tt>' need not be
+`<code>--with-gnu-as</code>' and `<code>--with-gnu-ld</code>' need not be
 used; these flags will be auto-detected.  One drawback of this option
 is that it won't allow you to override the search path for assembler
-and linker with command-line options <tt>-B/path/</tt> if the
+and linker with command-line options <code>-B/path/</code> if the
 specified filenames exist.</p>
 
 <hr />
@@ -444,7 +445,8 @@
 compile additional code to be included in the library.  That additional code
 must also be compiled with the proper PIC option.</p>
 
-<p>Adding the proper PIC option (<tt>-fpic</tt> or <tt>-fPIC</tt>) to the link
+<p>Adding the proper PIC option (<code>-fpic</code> or <code>-fPIC</code>)
+to the link
 line which creates the shared library will fix this problem on targets that
 support PIC in this manner.  For example:</p>
 <pre>