- Reduce the misuse of role attribute; role="directory" should actually be

  class="directory"
- Add constraint to enforce this

8 files changed, 30 insertions, 30 deletions

diff --git a/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.xml b/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.xml
index c23d4afc19..f175f2669e 100644
--- a/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.xml
@@ -2877,7 +2877,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
 		<filename>pxeboot</filename>, not the kernel.  There are other
 		interesting possibilities, like loading
 		<filename>pxeboot</filename> from a &os; CD-ROM
-		<filename role="directory">/boot</filename> directory (as
+		<filename class="directory">/boot</filename> directory (as
 		&man.pxeboot.8; can load a <filename>GENERIC</filename> kernel,
 		this makes it possible to use <acronym>PXE</acronym> to boot
 		from a remote CD-ROM).</para>
diff --git a/pl_PL.ISO8859-2/books/handbook/audit/chapter.xml b/pl_PL.ISO8859-2/books/handbook/audit/chapter.xml
index 13aa55147a..d7ccb51e3f 100644
--- a/pl_PL.ISO8859-2/books/handbook/audit/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/audit/chapter.xml
@@ -167,7 +167,7 @@ requirements. -->
     <para>Support for Event Auditing is installed with
       the normal <maketarget>installworld</maketarget> process.  An
       administrator may confirm this by viewing the contents
-      of <filename role="directory">/etc/security</filename>.  Files
+      of <filename class="directory">/etc/security</filename>.  Files
       beginning with the word <emphasis>audit</emphasis> should be present.
       For example, <filename>audit_event</filename>.</para>
 
@@ -194,7 +194,7 @@ requirements. -->
     <title>Audit Configuration</title>
 
     <para>All configuration files for security audit are found in
-      <filename role="directory">/etc/security</filename>.  The following
+      <filename class="directory">/etc/security</filename>.  The following
       files must be present before the audit daemon is started:</para>
 
     <itemizedlist>
@@ -451,10 +451,10 @@ naflags:lo</programlisting>
 	  percentage of free space for audit file systems.  This
 	  relates to the file system where audit logs are stored.
 	  For example, if the <option>dir</option> specifies
-	  <filename role="directory">/var/audit</filename> and
+	  <filename class="directory">/var/audit</filename> and
 	  <option>minfree</option> is set to twenty (20), warning
 	  messages will be generated when the
-	  <filename role="directory">/var</filename> file system grows
+	  <filename class="directory">/var</filename> file system grows
 	  to eighty (80) percent full.</para>
 
 	<para>The <option>naflags</option> option specifies audit
diff --git a/pl_PL.ISO8859-2/books/handbook/disks/chapter.xml b/pl_PL.ISO8859-2/books/handbook/disks/chapter.xml
index 041ae3ebb2..cad085f1cd 100644
--- a/pl_PL.ISO8859-2/books/handbook/disks/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/disks/chapter.xml
@@ -3798,7 +3798,7 @@ device crypto</screen>
 	  <para>The following example will describe how to generate a
 	    key file, which will be used as part of the Master Key for
 	    the encrypted provider mounted under
-	    <filename role="directory">/private</filename>.  The key
+	    <filename class="directory">/private</filename>.  The key
 	    file will provide some random data used to encrypt the
 	    Master Key.  The Master Key will be protected by a
 	    passphrase as well.  Provider's sector size will be 4kB big.
@@ -3870,7 +3870,7 @@ Filesystem     Size   Used  Avail Capacity  Mounted on
 	  <title>Unmounting and Detaching the Provider</title>
 
 	  <para>Once the work on the encrypted partition is done, and
-	    the <filename role="directory">/private</filename> partition
+	    the <filename class="directory">/private</filename> partition
 	    is no longer needed, it is prudent to consider unmounting
 	    and detaching the <command>geli</command> encrypted
 	    partition from the kernel.</para>
diff --git a/pl_PL.ISO8859-2/books/handbook/geom/chapter.xml b/pl_PL.ISO8859-2/books/handbook/geom/chapter.xml
index 2026d043cc..49ab5b61f6 100644
--- a/pl_PL.ISO8859-2/books/handbook/geom/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/geom/chapter.xml
@@ -87,7 +87,7 @@
     <para>GEOM permits access and control to classes &mdash; Master Boot
       Records, <acronym>BSD</acronym> labels, etc &mdash; through the
       use of providers, or the special files in
-      <filename role="directory">/dev</filename>.  Supporting various
+      <filename class="directory">/dev</filename>.  Supporting various
       software <acronym>RAID</acronym> configurations, GEOM will
       transparently provide access to the operating system and
       operating system utilities.</para>
@@ -157,7 +157,7 @@
       <step><para>Ensure that a suitable mount point exists.  If this
         volume will become a root partition, then temporarily use
         another mount point such as <filename
-        role="directory">/mnt</filename>:</para>
+        class="directory">/mnt</filename>:</para>
 
         <screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
       </step>
@@ -186,7 +186,7 @@ XXX: What message?  Put it inside the screen output above.
       </step>
 
       <step><para>This process should have created two other devices
-        in the <filename role="directory">/dev/stripe</filename>
+        in the <filename class="directory">/dev/stripe</filename>
         directory in addition to the <devicename>st0</devicename> device.
         Those include <devicename>st0a</devicename> and
         <devicename>st0c</devicename>.  A file system must now be created
@@ -248,7 +248,7 @@ XXX: What message?  Put it inside the screen output above.
     <para>Begin by installing &os; on the first disk with only two
       partitions.  One should be a swap partition, double the
       <acronym>RAM</acronym> size and all remaining space devoted to
-      the root (<filename role="directory">/</filename>) file system.
+      the root (<filename class="directory">/</filename>) file system.
       It is possible to have separate partitions for other mount points;
       however, this will increase the difficulty level ten fold due to
       manual alteration of the &man.bsdlabel.8; and &man.fdisk.8;
@@ -277,7 +277,7 @@ Done.</screen>
     <note>
       <para>This command should have created the
 	<devicename>gm0</devicename>, device node under the
-	<filename role="directory">/dev/mirror</filename>
+	<filename class="directory">/dev/mirror</filename>
 	directory.</para>
     </note>
 
@@ -305,7 +305,7 @@ Done.</screen>
     <para>This should have caused the system to spit out some
       information and a bunch of numbers.  This is good.  Examine the
       screen for any error messages and mount the device to the
-      <filename role="directory">/mnt</filename> mount point:</para>
+      <filename class="directory">/mnt</filename> mount point:</para>
 
     <screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
 
@@ -443,7 +443,7 @@ OK? <userinput>boot</userinput></screen>
     <screen>&prompt.root; <userinput>mount /dev/ggate0 /mnt</userinput></screen>
 
     <para>From here on, the device may be accessed through the
-      <filename role="directory">/mnt</filename> mount point.</para>
+      <filename class="directory">/mnt</filename> mount point.</para>
 
     <note>
       <para>It should be pointed out that this will fail if the device
diff --git a/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.xml b/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.xml
index 9dd6a53a67..4114d79a0a 100644
--- a/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.xml
@@ -410,7 +410,7 @@ multi on</programlisting>
       <para>The shell scripts that
 	<application>&mathematica;</application> created during
 	installation have to be modified before you can use them.  If
-	you chose <filename role="directory">/usr/local/bin</filename>
+	you chose <filename class="directory">/usr/local/bin</filename>
 	as the directory to place the
 	<application>&mathematica;</application> executables in, you
 	will find symlinks in this directory to files called
diff --git a/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.xml b/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.xml
index 6bdc9ae856..552ef66f88 100644
--- a/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.xml
@@ -2433,7 +2433,7 @@ doc/zh_*</screen>
 
       <note>
 	<para>In the default installation
-	  <filename role="directory">/usr/ports</filename> is not
+	  <filename class="directory">/usr/ports</filename> is not
 	  created.  If you run &os;&nbsp;6.0-RELEASE, it should be created before
 	  <command>portsnap</command> is used.  On more recent
 	  versions of &os; or <application>Portsnap</application>,
diff --git a/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.xml b/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.xml
index c73e199a9b..af7d1a0fa7 100644
--- a/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.xml
@@ -3080,7 +3080,7 @@ dhcpd_ifaces="dc0"</programlisting>
 	<hostid>org.</hostid>, as <hostid>org.</hostid> is more specific
 	than the root zone.  The layout of each part of a hostname is
 	much like a file system: the
-	<filename role="directory">/dev</filename> directory falls
+	<filename class="directory">/dev</filename> directory falls
 	within the root, and so on.</para>
     </sect2>
 
@@ -3164,7 +3164,7 @@ dhcpd_ifaces="dc0"</programlisting>
 	    </row>
 
 	    <row>
-	      <entry><filename role="directory">/etc/namedb</filename></entry>
+	      <entry><filename class="directory">/etc/namedb</filename></entry>
 	      <entry>Directory where BIND zone information resides.</entry>
 	    </row>
 
@@ -3178,10 +3178,10 @@ dhcpd_ifaces="dc0"</programlisting>
 
       <para>Depending on how a given zone is configured on the server,
 	the files related to that zone can be found in the <filename
-	role="directory">master</filename>, <filename
-	role="directory">slave</filename>, or <filename
-	role="directory">dynamic</filename> subdirectories of the
-	<filename role="directory">/etc/namedb</filename> directory.
+	class="directory">master</filename>, <filename
+	class="directory">slave</filename>, or <filename
+	class="directory">dynamic</filename> subdirectories of the
+	<filename class="directory">/etc/namedb</filename> directory.
 	These files contain the <acronym>DNS</acronym> information that
 	will be given out by the name server in response to queries.</para>
     </sect2>
@@ -3229,7 +3229,7 @@ dhcpd_ifaces="dc0"</programlisting>
 
       <para>Configuration files for <application>named</application>
 	currently reside in
-	<filename role="directory">/etc/namedb</filename> directory and
+	<filename class="directory">/etc/namedb</filename> directory and
 	will need modification before use, unless all that is needed is
 	a simple resolver.  This is where most of the configuration will
 	be performed.</para>
@@ -3238,7 +3238,7 @@ dhcpd_ifaces="dc0"</programlisting>
 	<title>Using <command>make-localhost</command></title>
 
 	<para>To configure a master zone for the localhost visit the
-	  <filename role="directory">/etc/namedb</filename> directory
+	  <filename class="directory">/etc/namedb</filename> directory
 	  and run the following command:</para>
 
 	<screen>&prompt.root; <userinput>sh make-localhost</userinput></screen>
diff --git a/pl_PL.ISO8859-2/books/handbook/ports/chapter.xml b/pl_PL.ISO8859-2/books/handbook/ports/chapter.xml
index 89624bf757..86bc19dbe9 100644
--- a/pl_PL.ISO8859-2/books/handbook/ports/chapter.xml
+++ b/pl_PL.ISO8859-2/books/handbook/ports/chapter.xml
@@ -624,7 +624,7 @@ docbook                     =
           CVSup</link>.</para>
 
 	<para>Bardzo ważnym jest, aby upewnić się, że katalog
-          <filename role="directory">/usr/ports</filename> jest pusty
+          <filename class="directory">/usr/ports</filename> jest pusty
           nim po raz pierwszy uruchomimy <application>CVSup</application>!
           Jeśli posiadamy już kolekcję portów pozyskaną z innego źródła
           <application>CVSup</application> nie usunie nieużywanych
@@ -717,7 +717,7 @@ docbook                     =
             bądź najnowszą wersję programu <application>Portsnap</application>.
             Przy pierwszym uruchomieniu programu &man.portsnap.8;  zostanie
             automatycznie utworzony katalog <filename
-	    role="directory">/usr/ports</filename>. W starszych wersjach programu
+	    class="directory">/usr/ports</filename>. W starszych wersjach programu
             wymagane jest własnoręczne utworzenie katalogu:</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
@@ -725,7 +725,7 @@ docbook                     =
 
 	<step>
           <para>Pobierz skompresowaną migawkę kolekcji portów do katalogu
-            <filename role="directory">/var/db/portsnap</filename>. Można następnie
+            <filename class="directory">/var/db/portsnap</filename>. Można następnie
             zakończyć połączenie z Internetem, jeśli jest taka potrzeba.</para>
 
 	  <screen>&prompt.root; <userinput>portsnap fetch</userinput></screen>
@@ -734,13 +734,13 @@ docbook                     =
 	<step>
           <para>Jeśli uruchamiany <application>Portsnap</application> po raz
             pierwszy należy rozpakować migawkę do katalogu
-            <filename role="directory">/usr/ports</filename>:
+            <filename class="directory">/usr/ports</filename>:
 	  </para>
 
 	  <screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
 
           <para>Jeśli posiadamy już kolekcję portów w <filename
-	    role="directory">/usr/ports</filename> i jedynie ją aktualizujemy,
+	    class="directory">/usr/ports</filename> i jedynie ją aktualizujemy,
             wpisujemy polecenie:</para>
 
 	  <screen>&prompt.root; <userinput>portsnap update</userinput></screen>
@@ -1250,7 +1250,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
           portów jest <application>Portmanager</application>, dostępny z portu
 	  <filename role="package">sysutils/portmanager</filename>:</para>
 
-	<screen>&prompt.root; <userinput>cd <filename role="directory">/usr/ports/sysutils/portmanager</filename></userinput>
+	<screen>&prompt.root; <userinput>cd <filename class="directory">/usr/ports/sysutils/portmanager</filename></userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
 	<para>Wszystkie zainstalowane porty mogą zostać zaktualizowane