1 files changed, 12 insertions, 12 deletions
diff --git a/src/H5VLmodule.h b/src/H5VLmodule.h
index 169134a..44b9af0 100644
--- a/src/H5VLmodule.h
+++ b/src/H5VLmodule.h
@@ -35,7 +35,7 @@
  * that could potentially access objects in an HDF5 container and forwards those calls to a VOL
  * connector, which implements the storage. The user or application gets the benefit of using the
  * familiar and widely-used HDF5 data model and API, but can map the physical storage of the HDF5 file
- * and objects to storage that better meets the application’s data needs.
+ * and objects to storage that better meets the application's data needs.
  *
  * \subsection subsec_vol_abstract_layer The VOL Abstraction Layer
  * The VOL lies just under the public API. When a storage-oriented public APIcall is made, the library
@@ -126,7 +126,7 @@
  * due to inadequate support for pass-through connectors. These deficiencies have been addressed
  * in HDF5 1.14.0, so VOL users and connector authors should target the 1.14.0 VOL API.
  *
- * On Windows, it’s probably best to use the same debug vs release configuration for the application and
+ * On Windows, it's probably best to use the same debug vs release configuration for the application and
  * all libraries in order to avoid C runtime (CRT) issues. Pre-2015 versions of Visual Studio are not
  * supported.
  *
@@ -141,7 +141,7 @@
  *
  * Exactly how you go about setting a VOL connector in a fapl, will depend on
  * the complexity of the VOL connector and how much control you have over the
- * application’s source code. Note that the environment variable method, though
+ * application's source code. Note that the environment variable method, though
  * convenient, has some limitations in its implementation, which are discussed
  * below.
  *
@@ -170,7 +170,7 @@
  *
  * \subsection subsec_vol_use Connector Use
  * Before a VOL connector can be set in a fapl, it must be registered with the
- * library (\ref H5Pset_vol requires the connector’s #hid_t ID) and, if a plugin, it
+ * library (\ref H5Pset_vol requires the connector's #hid_t ID) and, if a plugin, it
  * must be discoverable by the library at run time.
  *
  * \subsubsection subsubsec_vol_connect_register Registration
@@ -190,7 +190,7 @@
  *
  * Note the two ways that a VOL connector can be identified: by a name or by
  * a connector-specific numerical value (#H5VL_class_value_t is typedef’d to an
- * integer). The name and value for a connector can be found in the connector’s
+ * integer). The name and value for a connector can be found in the connector's
  * documentation or public header file.
  *
  * Each call also takes a VOL initialization property list (vipl). The library adds
@@ -203,11 +203,11 @@
  * closed. If you want to close a VOL connector ID, either \ref H5VLunregister_connector()
  * or \ref H5VLclose() can be used (they have the same internal code path). The library maintains a
  * reference count on all open IDs and will not do the actual
- * work of closing an ID until its reference count drops to zero, so it’s safe to close
+ * work of closing an ID until its reference count drops to zero, so it's safe to close
  * IDs anytime after they are used, even while an HDF5 file that was opened with
  * that connector is still open.
  *
- * Note that it’s considered an error to unload the native VOL connector. The
+ * Note that it's considered an error to unload the native VOL connector. The
  * library will prevent this. This means that, for the time being, the native VOL
  * connector will always be available. This may change in the future so that
  * the memory footprint of the native VOL connector goes away when not in
@@ -222,7 +222,7 @@
  * in the fapl. These will often be in the form of \b H5Pset_fapl_<name>(). For
  * example, the <a href="https://github.com/HDFGroup/vol-daos">DAOS VOL</a> connector
  * provides a \b H5Pset_fapl_daos() API call which will take MPI parameters and
- * make this call. See the connector’s documentation or public header file(s) for
+ * make this call. See the connector's documentation or public header file(s) for
  * more information.
  *
  * \subsubsection subsubsec_vol_connect_set_vol H5Pset_vol()
@@ -234,12 +234,12 @@
  *
  * It takes the ID of the file access property list, the ID of the registered VOL
  * connector, and a pointer to whatever connector-specific data the connector is
- * expecting. This will usually be a data struct specified in the connector’s header
+ * expecting. This will usually be a data struct specified in the connector's header
  * or a NULL pointer if the connecter requires no special information (as in the
  * native VOL connector).
  *
  * As mentioned above, many connectors will provide their own replacement for
- * this call. See the connector’s documentation for more information.
+ * this call. See the connector's documentation for more information.
  *
  * \subsubsection subsubsec_vol_connect_search VOL Connector Search Path
  * Dynamically loaded VOL connector plugins are discovered and loaded by the
@@ -297,7 +297,7 @@
  *
  * NOTE: Implementing the environment variable in this way means that setting
  * the native VOL connector becomes somewhat awkward as there is no explicit
- * HDF5 API call to do this. Instead you will need to get the native VOL connector’s ID via
+ * HDF5 API call to do this. Instead you will need to get the native VOL connector's ID via
  * \ref H5VLget_connector_id_by_value(#H5_VOL_NATIVE) and set it manually in the fapl
  * using \ref H5Pset_vol().
  *
@@ -595,7 +595,7 @@
  * \code
  *  --vol-(name|value|info)
  * \endcode
- * See the individual tool’s help for the options specific to that tool.
+ * See the individual tool's help for the options specific to that tool.
  *
  * \subsection subsec_vol_compat Compatibility
  *