Review iscsi SOP

Signed-off-by: Michal Konečný <mkonecny@redhat.com>

modules/sysadmin_guide/nav.adoc

@@ -54,7 +54,7 @@
 ** xref:infra-repo.adoc[Infrastructure Yum Repo - SOP]
 ** xref:infra-retiremachine.adoc[Infrastructure retire machine - SOP]
 ** xref:ipsilon.adoc[Ipsilon Infrastructure - SOP]
-** xref:iscsi.adoc[iscsi - SOP in review ]
+** xref:iscsi.adoc[iSCSI - SOP]
 ** xref:jenkins-fedmsg.adoc[jenkins-fedmsg - SOP in review ]
 ** xref:kerneltest-harness.adoc[kerneltest-harness - SOP in review ]
 ** xref:kickstarts.adoc[kickstarts - SOP in review ]

modules/sysadmin_guide/pages/iscsi.adoc

@@ -6,21 +6,13 @@ an iscsi export.
 
 == Contents
 
-[arabic]
+* <<_contact_information>>
-. Contact Information
+* <<_typical_uses>>
-. Typical uses
+* <<_iscsi_basics>>
-. iscsi basics
+** <<_terms>>
-
+** <<_iscsis_basic_login_logout_procedure_is>>
-____
+* <<_logging_in>>
-[arabic]
+* <<_logging_out>>
-. Terms
-. iscsi's basic login / logout procedure is
-____
-
-[arabic, start=4]
-. Loggin in
-. Logging out
-. Important note about creating new logical volumes
 
 == Contact Information
 
@@ -28,27 +20,25 @@ Owner::
   Fedora Infrastructure Team
 Contact::
   #fedora-admin, sysadmin-main
-Location::
-  Phoenix
 Servers::
   xen[1-15]
 Purpose::
   Provides iscsi connectivity to our netapp.
 
-== Typical uses
+== Typical Uses
 
 The best uses for Fedora are for servers that are not part of a farm or
 live replicated. For example, we wouldn't put app1 on the iscsi share
 because we don't gain anything from it. Shutting down app1 to move it
 isn't an issue because app1 is part of our application server farm.
 
-noc1, however, is not replicated. It's a stand alone box that, at best,
+_noc1_, however, is not replicated. It's a stand alone box that, at best,
 would have a non-live failover. By placing this host on an iscsi share,
 we can make it more highly available as it allows us to move that box
 around our virtualization infrastructure without rebooting it or even
 taking it down.
 
-== iscsi basics
+== iscsi Basics
 
 === Terms
 
@@ -60,15 +50,11 @@ taking it down.
 === iscsi's basic login / logout procedure is
 
 [arabic]
-. {blank}
+. Notify your client that a new target is available (similar to editing
-+
-Notify your client that a new target is available (similar to editing::
   /etc/fstab for a new nfs mount)
 . Login to the iscsi target (similar to running "mount /my/nfs"
 . Logout from the iscsi target (similar to running "umount /my/nfs"
-. {blank}
+. Delete the target from the client (similar to removing the nfs mount
-+
-Delete the target from the client (similar to removing the nfs mount::
   from /etc/fstab)
 
 ==== Logging in
@@ -115,7 +101,6 @@ iscsiadm --mode node --targetname iqn.1992-08.com.netapp:sn.118047036 --portal 1
 ....
 
 [NOTE]
-.Note
 ====
 `Cannot deactivate volume group`
 
@@ -123,14 +108,12 @@ If the vgchange command fails with an error about not being able to
 deactivate the volume group, this means that one of the logical volumes
 is still in use. By running "lvs" you can get a list of volume groups.
 Look in the Attr column. There are 6 attrs listed. The 5th column
-usually has a '-' or an 'a'. 'a' means its active, - means it is not. To
+usually has a _-_ or an _a_. _a_ means its active, - means it is not. To
-the right of that (the last column) you will see an '-' or an 'o'. If
+the right of that (the last column) you will see an _-_ or an _o_. If
-you see an 'o' that means that logical volume is still mounted and in
+you see an _o_ that means that logical volume is still mounted and in use.
-use.
 ====
 
 [IMPORTANT]
-.Important
 ====
 
 Note about creating new logical volumes