nvme-*: spelling fixes in meta data text

heartbeat/nvmet-namespace

@@ -56,7 +56,7 @@ the LUN of an iSCSI target.
 <longdesc lang="en">
 The NVMe Qualified Name (NQN) is used to identify the remote NVMe
 storage target. It is similar to an iSCSI Qualified Name
-(IQN). While it is a free from string follow the conversion:
+(IQN). While it is a free-form string, you should follow the convention:
 nqn.2014-08.com.vendor:nvme:nvm-subsystem-sn-12345
 You need to refer here to the NQN of an NVMe Subsystem your created
 with the NVMeSubsystem resource agent.
@@ -76,7 +76,7 @@ The NVMe namespace id (number).
 <parameter name="backing_path" required="1" unique="0">
 <longdesc lang="en">
 The full path to the block device or file that should be exposed through this
-namesapce.
+namespace.
 </longdesc>
 <shortdesc lang="en">block device full path</shortdesc>
 <content type="string"/>
@@ -85,7 +85,7 @@ namesapce.
 <parameter name="uuid" required="1" unique="1">
 <longdesc lang="en">
 The UUID that should be exposed by NVMe. Create it using uuidgen. This is
-necessary that the initiators accept the Namespace from the new server
+necessary for the initiators to accept the namespace from the new server
 after failover.
 </longdesc>
 <shortdesc lang="en">UUID</shortdesc>

heartbeat/nvmet-port

@@ -68,33 +68,33 @@ The NVMe port number is a 16 bit number.
 
 <parameter name="type" required="0" unique="0">
 <longdesc lang="en">
-The NVMe transport type. Might be one of 'tcp', 'rdma', 'fc' or 'loop'.
+The NVMe transport type. Should be one of 'tcp', 'rdma', 'fc' or 'loop'.
 </longdesc>
 <shortdesc lang="en">tcp or rdma</shortdesc>
 <content type="string" default="${OCF_RESKEY_type_default}"/>
 </parameter>
 
 <parameter name="addr_fam" required="0" unique="0">
 <longdesc lang="en">
-The address family of the address. Mibht be 'ipv4', 'ipv6' or 'fc'.
+The address family of the address. Should be 'ipv4', 'ipv6' or 'fc'.
 </longdesc>
 <shortdesc lang="en">ipv4 or ipv6</shortdesc>
 <content type="string" default="${OCF_RESKEY_addr_fam_default}"/>
 </parameter>
 
 <parameter name="svcid" required="0" unique="0">
 <longdesc lang="en">
-The transport service identifier, is the TCP/IP port number of the
-equivalent in the RDMA world.
+The transport service identifier. The TCP/IP port number this target binds to,
+or its RDMA protocol equivalent.
 </longdesc>
 <shortdesc lang="en">IP/RDMA port number</shortdesc>
 <content type="integer" default="${OCF_RESKEY_svcid_default}"/>
 </parameter>
 
 <parameter name="addr" required="1" unique="0">
 <longdesc lang="en">
-The transport address, is the TCP/IP address this targets binds to
-or the equivalent in the RDMA world.
+The transport address. The TCP/IP address this targets binds to,
+or its RDMA protocol equivalent.
 </longdesc>
 <shortdesc lang="en">IP/RDMA/FC address</shortdesc>
 <content type="string"/>

heartbeat/nvmet-subsystem

@@ -56,7 +56,7 @@ A subsystem must be created first, before namespace(s) and port(s).
 <longdesc lang="en">
 The NVMe Qualified Name (NQN) is used to identify the remote NVMe
 storage target. It is similar to an iSCSI Qualified Name
-(IQN). While it is a free from string follow the conversion:
+(IQN). While it is a free-form string, you should follow the convention:
 nqn.2014-08.com.vendor:nvme:nvm-subsystem-sn-12345
 </longdesc>
 <shortdesc lang="en">NVMe Qualified Name</shortdesc>