Add a bit to the iSCSI intro.

Slight tightening of section headings.

Sponsored by: iXsystems

en_US.ISO8859-1/books/handbook/network-servers/chapter.xml

@@ -5657,30 +5657,44 @@ Logging to FILE /var/log/messages</screen>
     <title><acronym>iSCSI</acronym> Initiator and Target
       Configuration</title>
 
-    <para><acronym>iSCSI</acronym> is a way to share storage, to make
+    <para><acronym>iSCSI</acronym> is a way to share storage over a
-      disk space at one machine (the server, in iSCSI nomenclature
+      network.  Unlike
-      known as the <emphasis>target</emphasis>) available to others
+      <acronym>NFS</acronym>, which works at the
-      (clients, called <emphasis>initiators</emphasis> in
+      file system level, <acronym>iSCSI</acronym> works at the
-      <acronym>iSCSI</acronym>).  The main difference when compared to
+      block device level.</para>
-      <acronym>NFS</acronym> is that <acronym>NFS</acronym> works at a
+ 
-      filesystem level, while <acronym>iSCSI</acronym> works at the
+    <para>In <acronym>iSCSI</acronym> terminology, the system that
-      block device level.  To initiators, remote disks served via
+      shares the storage is
-      <acronym>iSCSI</acronym> are just like physical disks.  Their
+      known as the <emphasis>target</emphasis>.  The storage can be a
-      device nodes appear in <filename>/dev/</filename>, and must be
+      physical disk, or an area representing multiple disks or a
-      separately mounted.</para>
+      portion of a physical disk.  For example, if the disk(s) are
+      formatted with <acronym>ZFS</acronym>, a zvol can be created to
+      use as the <acronym>iSCSI</acronym> storage.</para>
+	
+    <para>The clients which access the <acronym>iSCSI</acronym>
+      storage are called <emphasis>initiators</emphasis>.
+      To initiators, the storage available through
+      <acronym>iSCSI</acronym> appears as a raw, unformatted disk
+      known as a <acronym>LUN</acronym>.
+      Device nodes for the disk appear in <filename>/dev/</filename> and the device must be
+      separately formatted and mounted.</para>
+      
+    <para>Beginning with 10.0-RELEASE, &os; provides a native,
+      kernel-based <acronym>iSCSI</acronym> target and initiator.
+      This section describes how to configure a &os; system as a
+      target or an initiator.</para>
 
     <sect2 xml:id="network-iscsi-target">
-      <title><acronym>iSCSI</acronym> Target</title>
+      <title>Configuring an <acronym>iSCSI</acronym> Target</title>
 
+      <note>
       <para>Note: the native <acronym>iSCSI</acronym> target is
 	supported starting with &os; 10.0-RELEASE.  To use
 	<acronym>iSCSI</acronym> in older versions of &os;, install a
 	userspace target from the Ports Collection, such as
 	<package>net/istgt</package>.  This chapter only describes the
 	native target.</para>
-
+      </note>
-      <sect3>
-	<title>Basic Operation</title>
 
 	<para>Configuring an <acronym>iSCSI</acronym> target is
 	  straightforward: create the
@@ -5793,7 +5807,6 @@ target iqn.2012-06.com.example:target0 {
 	  to reread it:</para>
 
 	<screen>&prompt.root; <userinput>service ctld reload</userinput></screen>
-      </sect3>
 
       <sect3>
 	<title>Authentication</title>
@@ -5849,7 +5862,7 @@ target iqn.2012-06.com.example:target0 {
     </sect2>
 
     <sect2 xml:id="network-iscsi-initiator">
-      <title><acronym>iSCSI</acronym> Initiator</title>
+      <title>Configuring an <acronym>iSCSI</acronym> Initiator</title>
 
       <note>
 	<para>The current <acronym>iSCSI</acronym> initiator is