+ xref closes with '/>'. This causes a trailing '>'

at the end of the reference.  Removed the '/'.

+ Marked up 'log' and 'spool' as filenames
  in the discussion of the 'var' directory.

+ Changed fdisk to show up as command.

+ Marked up vn as device.

+ Marked up "sysinstall" using a man.systinstall.8; entity.

PR:		docs/28989
Submitted by:	Martin Heinen <mheinen0@wiesbaden-online.de>

en_US.ISO8859-1/books/handbook/disks/chapter.sgml

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.35 2001/07/06 13:03:00 dd Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.36 2001/07/14 23:40:28 murray Exp $
 -->
 
 <chapter id="disks">
@@ -216,7 +216,7 @@
 	<literal>b</literal> is reserved for swap partitions, and
 	<literal>c</literal> is an unused partition the size of the
 	entire slice or drive.  This is explained in <xref
-	linkend="disks-adding" />.</para>
+	linkend="disks-adding">.</para>
     </sect2>
   </sect1>
 
@@ -233,7 +233,8 @@
     <indexterm><primary>root filesystem</primary></indexterm>
     <para>There are various reasons to house some of these
       directories on separate filesystems.  <filename>/var</filename>
-      contains log, spool, and various types of temporary files, and
+      contains <filename>log/</filename>, <filename>spool/</filename>,
+      and various types of temporary files, and
       as such, may get filled up.  Filling up the root filesystem
       isn't a good idea, so splitting <filename>/var</filename> from
       <filename>/</filename> is often a good idea.</para>
@@ -478,7 +479,7 @@
       <filename>/dev/da1e</filename>.</para>
 
     <sect2>
-      <title>Using sysinstall</title>
+      <title>Using &man.sysinstall.8;</title>
       <indexterm><primary>sysinstall</primary><secondary>adding disks</secondary></indexterm>
 
       <para>You may use <command>/stand/sysinstall</command> to
@@ -548,10 +549,11 @@
 
 	<para>This setup will allow your disk to work correctly with
 	  other operating systems that might be installed on your
-	  computer and will not confuse other operating systems' fdisk
-	  utilities.  It is recommended to use this method for new disk
-	  installs.  Only use <literal>dedicated</literal> mode if you
-	  have a good reason to do so!</para>
+	  computer and will not confuse other operating systems' 
+	  <command>fdisk</command> utilities.  It is recommended 
+	  to use this method for new disk installs.  Only use 
+	  <literal>dedicated</literal> mode if you have a good reason 
+	  to do so!</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rda1 bs=1k count=1</userinput>
 &prompt.root; <userinput>fdisk -BI da1</userinput> #Initialize your new disk
@@ -1027,8 +1029,8 @@ Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 
       <screen>&prompt.root; <userinput>mkisofs <option>-U</option> <option>-R</option> <option>-b</option> <filename>boot/cdboot</filename> <option>-o</option> <filename>/tmp/bootable.iso</filename> <filename>/tmp/myboot</filename></userinput></screen>
 
-      <para>Having done that, if you have vn configured in your kernel, you
-	can mount the file system with:</para>
+      <para>Having done that, if you have <devicename>vn</devicename>
+	configured in your kernel, you can mount the file system with:</para>
 
       <screen>&prompt.root; <userinput>vnconfig <option>-e</option> <filename>vn0c</filename> <filename>/tmp/bootable.iso</filename></userinput>
 &prompt.root; <userinput>mount <option>-t</option> cd9660 <filename>/dev/vn0c</filename> <filename>/mnt</filename></userinput></screen>