fix up a non-requirements and bits in the security considerations

Mostly from David Black

diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml
index f140bcf431f44ed1e28ef29f206b9c77b30d3dc0..4d893569b80f7b6d73b279e4c1de0d9cbb0040f1 100644 (file)
--- a/scsi_nvme_middle.xml
+++ b/scsi_nvme_middle.xml
@@ -278,12 +278,12 @@
     NOT be deployed.
   </t>
   <t>
-    As with other block-oriented pNFS layout types, the metadata
-    server MUST be able to fence off a client's access to the data
-    on an NVMe storage device.  When it revokes the layout, the
-    client's access MUST be terminated at the storage devices.  The
-    client has a subsequent opportunity to perform fresh security
-    checks and then reacquire a new layout.
+    As with other block-oriented pNFS layout types, the metadata server
+    is able to fence off a client's access to the data on an NVMe namespace
+    used as a storage device.  If a metadata server revokes a layout, the
+    client's access MUST be terminated at the storage devices via fencing
+    as specified in <xref target="ssc:fencing" />.  The client has a
+    subsequent opportunity to acquire a new layout.
   </t>
 </section>