summaryrefslogtreecommitdiffstats
path: root/src/H5FDmirror_priv.h
diff options
context:
space:
mode:
authorAllen Byrne <50328838+byrnHDF@users.noreply.github.com>2022-03-30 17:34:48 (GMT)
committerGitHub <noreply@github.com>2022-03-30 17:34:48 (GMT)
commitfac4cd9e667e3ec6e62e7975fbdb53ff0d70cdc6 (patch)
tree73d047b9cf257c85a708eb813c12f3071ed6d67a /src/H5FDmirror_priv.h
parentd4f151fac40724b0425e697b1c3613b5d86cfa7b (diff)
downloadhdf5-fac4cd9e667e3ec6e62e7975fbdb53ff0d70cdc6.zip
hdf5-fac4cd9e667e3ec6e62e7975fbdb53ff0d70cdc6.tar.gz
hdf5-fac4cd9e667e3ec6e62e7975fbdb53ff0d70cdc6.tar.bz2
1.10 Merge doxygen changes from develop (#1543)
* Merge doxygen changes from develop * Remove 1.12 section * Minor comment cleanup
Diffstat (limited to 'src/H5FDmirror_priv.h')
-rw-r--r--src/H5FDmirror_priv.h8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/H5FDmirror_priv.h b/src/H5FDmirror_priv.h
index 21de97b..b387f72 100644
--- a/src/H5FDmirror_priv.h
+++ b/src/H5FDmirror_priv.h
@@ -28,7 +28,7 @@ extern "C" {
* = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
*/
-/* The maximum allowed size for a receiving buffer when accepting bytes to
+/* Define the maximum allowed size for a receiving buffer when accepting bytes to
* write. Writes larger than this size are performed by multiple accept-write
* steps by the Writer. */
#define H5FD_MIRROR_DATA_BUFFER_MAX H5_GB /* 1 Gigabyte */
@@ -80,7 +80,7 @@ extern "C" {
*
* `magic` (uint32_t)
* A "unique" number identifying the structure and endianness of
- * transmitting maching.
+ * transmitting machine.
* Must be set to H5FD_MIRROR_XMIT_MAGIC native to the VFD "sender".
*
* `version` (uint8_t)
@@ -214,13 +214,13 @@ typedef struct H5FD_mirror_xmit_open_t {
*
* `status` (uint32_t)
* Number indicating whether the command was successful or if an
- * occured.
+ * occurred.
* Allowed values are H5FD_MIRROR_STATUS_OK and
* H5FD_MIRROR_STATUS_ERROR.
*
* `message` (char[])
* Error message. Populated if and only if there was a problem.
- * It is possible that a message may reach the end of the alloted
+ * It is possible that a message may reach the end of the allotted
* space without a NULL terminator -- the onus is on the programmer to
* handle this situation.
*