summaryrefslogtreecommitdiffstats
path: root/src/H5Smodule.h
diff options
context:
space:
mode:
authorDana Robinson <43805+derobins@users.noreply.github.com>2023-07-27 19:24:05 (GMT)
committerGitHub <noreply@github.com>2023-07-27 19:24:05 (GMT)
commitdf5dcb2a735dd5bb3ee2cc700119109605976e41 (patch)
tree4013a33b5e586013dce09c4831510cb59fdf400c /src/H5Smodule.h
parentcb69bc279ce12d078d43f7aa70b2929d8df1c147 (diff)
downloadhdf5-df5dcb2a735dd5bb3ee2cc700119109605976e41.zip
hdf5-df5dcb2a735dd5bb3ee2cc700119109605976e41.tar.gz
hdf5-df5dcb2a735dd5bb3ee2cc700119109605976e41.tar.bz2
Normalizes the public headers (#3292)
* Also brings over the apostrophe fix
Diffstat (limited to 'src/H5Smodule.h')
-rw-r--r--src/H5Smodule.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/H5Smodule.h b/src/H5Smodule.h
index c5081c7..d212d5d 100644
--- a/src/H5Smodule.h
+++ b/src/H5Smodule.h
@@ -63,7 +63,7 @@
* \subsubsection subsubsec_dataspace_program_object Dataspace Objects
*
* An HDF5 dataspace is a required component of an HDF5 dataset or attribute. A dataspace defines the size
- * and the shape of a dataset’s or an attribute’s raw data. Currently, HDF5 supports the following types of
+ * and the shape of a dataset's or an attribute's raw data. Currently, HDF5 supports the following types of
* the dataspaces:
* \li Scalar dataspaces
* \li Simple dataspaces
@@ -165,7 +165,7 @@
*
* <h4>Creating a Simple Dataspace</h4>
*
- * Let’s assume that an application wants to store a two‐dimensional array of data, A(20,100). During the
+ * Let's assume that an application wants to store a two‐dimensional array of data, A(20,100). During the
* life of the application, the first dimension of the array can grow up to 30; there is no restriction on
* the size of the second dimension. The following steps are used to declare a dataspace for the dataset
* in which the array data will be stored.
@@ -1221,7 +1221,7 @@
* \subsection subsec_dataspace_sample Sample Programs
*
* This section contains the full programs from which several of the code examples in this chapter were
- * derived. The h5dump output from the program’s output file immediately follows each program.
+ * derived. The h5dump output from the program's output file immediately follows each program.
*
* <em>h5_write.c</em>
* \code