Replace `UNIX™' combination with the `&unix;' entity.

Approved by:	des (mentor)

1 files changed, 9 insertions, 9 deletions

diff --git a/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml b/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
index c955721cf1..6778ab3d39 100644
--- a/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
@@ -275,7 +275,7 @@
 	<listitem>
 	  <para>The most visible object is the virtual disk, called a
 	    <emphasis>volume</emphasis>.  Volumes have essentially the same
-	    properties as a UNIX&trade; disk drive, though there are some minor
+	    properties as a &unix; disk drive, though there are some minor
 	    differences.  They have no size limitations.</para>
 	</listitem>
 
@@ -288,13 +288,13 @@
 	</listitem>
 
 	<listitem>
-	  <para>Since Vinum exists within the UNIX&trade; disk storage
-	    framework, it would be possible to use UNIX&trade;
+	  <para>Since Vinum exists within the &unix; disk storage
+	    framework, it would be possible to use &unix;
 	    partitions as the building block for multi-disk plexes,
 	    but in fact this turns out to be too inflexible:
-	    UNIX&trade; disks can have only a limited number of
+	    &unix; disks can have only a limited number of
 	    partitions.  Instead, Vinum subdivides a single
-	    UNIX&trade; partition (the <emphasis>drive</emphasis>)
+	    &unix; partition (the <emphasis>drive</emphasis>)
 	    into contiguous areas called
 	    <emphasis>subdisks</emphasis>, which it uses as building
 	    blocks for plexes.</para>
@@ -302,7 +302,7 @@
       
 	<listitem>
 	  <para>Subdisks reside on Vinum <emphasis>drives</emphasis>,
-	    currently UNIX&trade; partitions.  Vinum drives can
+	    currently &unix; partitions.  Vinum drives can
 	    contain any number of subdisks.  With the exception of a
 	    small area at the beginning of the drive, which is used
 	    for storing configuration and state information, the
@@ -677,7 +677,7 @@
       <para><anchor id="vinum-resilience">With sufficient hardware, it
 	is possible to build volumes which show both increased
 	resilience and increased performance compared to standard
-	UNIX&trade; partitions.  A typical configuration file might
+	&unix; partitions.  A typical configuration file might
 	be:</para>
 
       <programlisting>
@@ -875,7 +875,7 @@
       <title>Creating File Systems</title>
 
 	<para>Volumes appear to the system to be identical to disks,
-	  with one exception.  Unlike UNIX&trade; drives, Vinum does
+	  with one exception.  Unlike &unix; drives, Vinum does
 	  not partition volumes, which thus do not contain a partition
 	  table.  This has required modification to some disk
 	  utilities, notably &man.newfs.8;, which previously tried to
@@ -958,7 +958,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
 	  configuration information: it finds the drives by scanning
 	  the configured disk drives for partitions with a Vinum
 	  label.  This enables Vinum to identify drives correctly even
-	  if they have been assigned different UNIX&trade; drive
+	  if they have been assigned different &unix; drive
 	  IDs.</para>
   
       <sect3 id="vinum-rc-startup">