more nits

From Sorin Faibish

diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml
index 76f964d7d3e72c1214fbc697da8fb5b326d463ef..a7a5454b5cd5a727df00b3188a863a19a6835215 100644 (file)
--- a/scsi_nvme_middle.xml
+++ b/scsi_nvme_middle.xml
@@ -24,7 +24,7 @@
   </t>
   <t>
     This document does not amend the pNFS SCSI layout document, but
-    instead of explains how to map the SCSI constructs used in
+    instead explains how to map the SCSI constructs used in
     the pNFS SCSI layout document to NVMe concepts.
   </t>
 
@@ -170,7 +170,7 @@
        Before returning a PNFS_SCSI_VOLUME_BASE volume to the client, the MDS
        needs to prepare the volume for fencing using PRs. This is done by
        registering the reservation generated for the MDS with the device (see
-       <xref target="ssc:fencing:keys" /> followed by a Reservation Acquire
+       <xref target="ssc:fencing:keys" />) followed by a Reservation Acquire
        command (refer to Section 7.2 of <xref target="NVME-BASE" />) with
        the Reservation Acquire Action (RACQA) field set to 000b (i.e., Acquire)
        and the Reservation Type (RTYPE) field set to 4h (i.e., Exclusive Access
@@ -197,8 +197,8 @@
 
     <section anchor='ssc:recovery' title='Client Recovery after a Fence Action'>
       <t>
-        If a NVMe command issued by the client to the storage device returns a
-       non-retryable error (refer to the DNR bit defined in Figure 92 in
+        If an NVMe command issued by the client to the storage device returns
+       a non-retryable error (refer to the DNR bit defined in Figure 92 in
        <xref target="NVME-BASE" />), the client MUST commit all layouts that
        use the storage device through the MDS, return all outstanding layouts
        for the device, forget the device ID, and unregister the reservation