more README mods.

Author: d-w-moore

README.md

@@ -836,10 +836,10 @@ Disabling AVU reloads from the iRODS server
 -------------------------------------------
 
 With the default setting of reload = True, an iRODSMetaCollection will
-proactively read all current AVUs back from the iRODS server with
-each metadata write done by the client.  This helps methods such as items()
+proactively read all current AVUs back from the iRODS server after any
+metadata write done by the client.  This helps methods such as items()
 to return an up-to-date result.   Changing that default can, however, greatly
-increase code efficiency if for example there are many AVU's must be added or deleted
+increase code efficiency if for example a lot of AVUs must be added or deleted
 at once without reading any back again.
 
 ```
@@ -854,12 +854,11 @@ from pprint import pp
 print(f"{current_metadata = }")
 ```
 
-
 Subclassing iRODSMeta
 ---------------------
-An experimental keyword option, `iRODSMeta_type`, exists which can be used to
-set up any iRODSMeta subclass as the translator between native iRODS metadata
-APIs and the way in which the AVUs thus conveyed should be represented to the
+The keyword option `iRODSMeta_type` can be used to set up any iRODSMeta
+subclass as the translator between native iRODS metadata APIs
+and the way in which the AVUs thus conveyed should be represented to the
 client.
 
 An example is the `irods.meta.iRODSBinOrStringMeta` class which uses the
@@ -891,8 +890,8 @@ Whereas the content of native iRODS AVUs must obey some valid text encoding as
 determined by the resident ICAT DB, the above is a possible alternative - albeit
 one semantically bound to the local application that defines the needed
 translations.  Still, this can be a valid usage for users who need a guarantee
-that any given octet string can be placed into metadata in a way that doesn't
-violate standard text encodings.
+that any given octet string they might generate can be placed into metadata without
+violating standard text encodings.
 
 Atomic operations on metadata
 -----------------------------