nits

From David Black

diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml
index 839b8f065440ed274fac310fd308194b796f0495..76f964d7d3e72c1214fbc697da8fb5b326d463ef 100644 (file)
--- a/scsi_nvme_middle.xml
+++ b/scsi_nvme_middle.xml
@@ -84,7 +84,7 @@
 
     <t>
       To be used as storage devices for the pNFS SCSI layout, NVMe namespaces 
-      MUST support either the EUI64 or NGUID value reported in an Namespace
+      MUST support either the EUI64 or NGUID value reported in a Namespace
       Identification Descriptor, the I/O Command Set Independent Identify
       Namespace Data Structure, and the Identify Namespace Data Structure,
       NVM Command Set. If available, the NGUID value SHOULD be used as it is
@@ -97,16 +97,16 @@
     </t>
 
     <t>
-      The pnfs_scsi_base_volume_info4 structure shall be constructed as
-      following:
+      The pnfs_scsi_base_volume_info4 structure for an NVMe namespace
+      SHALL be constructed as follows:
       <list style='numbers'>
       <t>The "sbv_code_set" field SHALL be set to PS_CODE_SET_BINARY.</t>
       <t>The "pnfs_scsi_designator_type" field SHALL be set to
          PS_DESIGNATOR_EUI64.</t>
       <t>The "sbv_designator" field SHALL contain either the NGUID or
-         the EUI64 identifier from NVMe Identify Namespace data.  If
-        both NGUID and EUI64 identifiers are available, then the NGUID
-        identifier SHOULD be used as it is the larger identifier.</t>
+        the EUI64 identifier from the namespace.  If both NGUID and EUI64
+        identifiers are available, then the NGUID identifier SHOULD be
+        used as it is the larger identifier.</t>
       <!-- XXX: add a reference to the persistent reservation section for
            sbv_pr_key -->
       </list>
@@ -116,7 +116,7 @@
       its XDR representation) indicates which NVMe identifier is present.
       That length MUST be 16 octets for an NVMe NGUID identifier and
       MUST be 8 octets for an NVMe EUI64 identifier.  All other lengths
-      MUST NOT be used with NVMe.
+      MUST NOT be used with an NVMe namespace.
     </t>
   </section>