From 5320eb6c49ed48f8750c11720e567ec218ea50ea Mon Sep 17 00:00:00 2001
From: Marc Fonvieille <blackend@FreeBSD.org>
Date: Tue, 13 Aug 2002 10:13:46 +0000
Subject: [PATCH] Add missing tags for x11 category, use same tags type in all
 categories section, and few fixes.

---
 .../books/porters-handbook/book.sgml          | 30 +++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml
index ef645b1dd0..28a278b457 100644
--- a/en_US.ISO8859-1/books/porters-handbook/book.sgml
+++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml
@@ -1603,8 +1603,8 @@ PORTEPOCH=	1</programlisting>
               </row>
 
               <row>
-                <entry>x11</entry>
-                <entry>The X window system and friends.  This category is only
+                <entry><filename>x11</filename></entry>
+                <entry>The X Window System and friends.  This category is only
                   for software that directly supports the window system.  Do not
                   put regular X applications here.  If your port is an X
                   application, define <makevar>USE_XLIB</makevar> (implied by
@@ -1658,30 +1658,30 @@ PORTEPOCH=	1</programlisting>
         <para>As many of the categories overlap, you often have to choose
           which of the categories should be the primary category of your port.
           There are several rules that govern this issue.  Here is the list of
-          priorities, in decreasing order of precedence.</para>
+          priorities, in decreasing order of precedence:</para>
 
         <itemizedlist>
           <listitem>
             <para>Language specific categories always come first.  For
               example, if your port installs Japanese X11 fonts, then your
-              <makevar>CATEGORIES</makevar> line would read <literal>japanese
-                x11-fonts</literal>.</para>
+              <makevar>CATEGORIES</makevar> line would read <filename>japanese
+                x11-fonts</filename>.</para>
           </listitem>
 
           <listitem>
             <para>Specific categories win over less-specific ones.  For
-              instance, an HTML editor should be listed as <literal>www
-                editors</literal>, not the other way around.  Also, you do not
-              need to list <literal>net</literal> when the port belongs to
-              any of <literal>irc</literal>, <literal>mail</literal>,
-              <literal>mbone</literal>, <literal>news</literal>,
-              <literal>security</literal>, or <literal>www</literal>.</para>
+              instance, an HTML editor should be listed as <filename>www
+                editors</filename>, not the other way around.  Also, you do not
+              need to list <filename>net</filename> when the port belongs to
+              any of <filename>irc</filename>, <filename>mail</filename>,
+              <filename>mbone</filename>, <filename>news</filename>,
+              <filename>security</filename>, or <filename>www</filename>.</para>
           </listitem>
 
           <listitem>
-            <para><literal>x11</literal> is used as a secondary category only
+            <para><filename>x11</filename> is used as a secondary category only
               when the primary category is a natural language.  In particular,
-              you should not put <literal>x11</literal> in the category line
+              you should not put <filename>x11</filename> in the category line
               for X applications.</para>
           </listitem>
 
@@ -1698,12 +1698,12 @@ PORTEPOCH=	1</programlisting>
 
           <listitem>
             <para>If your port truly does not belong anywhere else, put it in
-              <literal>misc</literal>.</para>
+              <filename>misc</filename>.</para>
           </listitem>
         </itemizedlist>
 
         <para>If you are not sure about the category, please put a comment to
-          that effect in your <command>send-pr</command> submission so we can
+          that effect in your &man.send-pr.1; submission so we can
           discuss it before we import it.  If you are a committer, send a note
           to the &a.ports; so we can discuss it first&mdash;too often new ports are
           imported to the wrong category only to be moved right away.</para>