From e9b8e3db198d955686a5743a289071a155047b18 Mon Sep 17 00:00:00 2001
From: Christoph Hellwig <hch@lst.de>
Date: Fri, 10 Mar 2023 17:41:26 +0100
Subject: [PATCH] fencing wording updates

From David Noveck
---
 scsi_nvme_middle.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml
index 80af104..915da19 100644
--- a/scsi_nvme_middle.xml
+++ b/scsi_nvme_middle.xml
@@ -136,15 +136,15 @@
   <section anchor='ssc:fencing' title='Client Fencing'>
     <t>
       The SCSI layout uses Persistent Reservations (PRs) to provide client
-      fencing.  For this both the MDS and the Clients have to register
-      a key with the storage device, and the MDS has to create a
+      fencing.  For this to be achieved, both the MDS and the Clients have to
+      register a key with the storage device, and the MDS has to create a
       reservation on the storage device.
     </t>
     <t>
-      The following is a full mapping of the required PERSISTENT RESERVE IN
-      and PERSISTENT RESERVE OUT SCSI commands <xref target="SPC5" /> to
-      NVMe commands which MUST be used when using NVMe namespaces as
-      storage devices for the pNFS SCSI layout.
+      The following sub-sections provide a full mapping of the required
+      PERSISTENT RESERVE IN and PERSISTENT RESERVE OUT SCSI commands
+      <xref target="SPC5" /> to NVMe commands which MUST be used when using
+      NVMe namespaces as storage devices for the pNFS SCSI layout.
     </t>
 
     <section anchor='ssc:fencing:keys' title='PRs - Key Registration'>
-- 
2.50.1