docs/124136: [patch] Fix Markup in FAQ, Question 5.7

[Gabor PALI]

>Number:         124136
>Category:       docs
>Synopsis:       [patch] Fix Markup in FAQ, Question 5.7
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 30 16:10:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gabor PALI
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD disznohal 6.3-STABLE FreeBSD 6.3-STABLE #4: Fri Apr 4 23:29:43 CEST 2008 dezzy at disznohal:/usr/obj/usr/src/sys/GENERIC_ i386

>Description:
	I think markups enclosing make(1) commands should be <command> tags
	rather than <quote> tags in the FreeBSD FAQ, Question 5.7. ``Why do
	my programs occasionally die with "Signal 11" errors?''. I attached
	a patch to fix this problem.


>How-To-Repeat:

>Fix:

--- books.faq.patch.19.diff begins here ---
Index: book.sgml
===================================================================
RCS file: /doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.827
diff -u -r1.827 book.sgml
--- book.sgml	27 May 2008 23:51:07 -0000	1.827
+++ book.sgml	29 May 2008 03:12:51 -0000
@@ -3029,11 +3029,11 @@
             that the compiler is carrying out changes each
             time.</para>
 
-          <para>For example, suppose you are running <quote>make
-            buildworld</quote>, and the compile fails while trying to
+          <para>For example, suppose you are running <command>make
+            buildworld</command>, and the compile fails while trying to
             compile <filename>ls.c</filename> into
-            <filename>ls.o</filename>. If you then run <quote>make
-            buildworld</quote> again, and the compile fails in the same
+            <filename>ls.o</filename>. If you then run <command>make
+            buildworld</command> again, and the compile fails in the same
             place then this is a broken build -- try updating your sources
             and try again. If the compile fails elsewhere then this is
             almost certainly hardware.</para>
--- books.faq.patch.19.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: