clean up "actually guaranteed" wording

From David Black

diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml
index 6a9041633bd0c389bc2946b820adc37d0ec44787..82b9fc78d72072522f624c2ca7ab1dcb58576a7a 100644 (file)
--- a/scsi_nvme_middle.xml
+++ b/scsi_nvme_middle.xml
@@ -153,9 +153,11 @@
        One important difference between SCSI Persistent Reservations
        and NVMe Reservations is that NVMe reservation keys always apply
        to all controllers used by a host (as indicated by the NVMe Host
-       Identifier) This behavior is similar to setting the ALL_TG_PT bit
-       when registering a SCSI Reservation key, but actually guaranteed
-       to work reliably.
+       Identifier). This behavior is analogous to setting the ALL_TG_PT
+       bit when registering a SCSI Reservation key, and is always supported
+       by NVMe Reservations, unlike the ALL_TG_PT for which SCSI support is
+       inconsistent and cannot be relied upon.
+
        Registering a reservation key with a namespace creates an
        association between a host and a namespace. A host that is a
        registrant of a namespace may use any controller with which that