summaryrefslogtreecommitdiffstats
path: root/src/H5C.c
diff options
context:
space:
mode:
authorBinh-Minh Ribler <bmribler@hdfgroup.org>2018-04-12 23:34:20 (GMT)
committerBinh-Minh Ribler <bmribler@hdfgroup.org>2018-04-12 23:34:20 (GMT)
commit8b15b10c59b73cdc624cacbfe7652f32c3d44dae (patch)
tree2799d33e8d33bbab83c414ab17000e2aa19ce632 /src/H5C.c
parent3fc4ea3d3935f254ac61fd726f9b9d684fe653a6 (diff)
downloadhdf5-8b15b10c59b73cdc624cacbfe7652f32c3d44dae.zip
hdf5-8b15b10c59b73cdc624cacbfe7652f32c3d44dae.tar.gz
hdf5-8b15b10c59b73cdc624cacbfe7652f32c3d44dae.tar.bz2
Fixed typos
Description: Looked for typos similar to user's report in HDFFV-10404. Not all the same but many were found and fixed. Platforms tested: Linux/64 (jelly) - only typos
Diffstat (limited to 'src/H5C.c')
-rw-r--r--src/H5C.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/H5C.c b/src/H5C.c
index e03a0c8..b3f76dc 100644
--- a/src/H5C.c
+++ b/src/H5C.c
@@ -5258,7 +5258,7 @@ H5C_unprotect(H5F_t * f,
*
* All this is a bit awkward, but until the metadata cache entries
* are contiguous, with only one dirty flag, we have to let the supplied
- * functions deal with the reseting the is_dirty flag.
+ * functions deal with the resetting the is_dirty flag.
*/
if ( entry_ptr->clear_on_unprotect ) {
@@ -6912,7 +6912,7 @@ H5C__flash_increase_cache_size(H5C_t * cache_ptr,
if ( (cache_ptr->resize_ctl).rpt_fcn != NULL ) {
/* get the hit rate for the reporting function. Should still
- * be good as we havent reset the hit rate statistics.
+ * be good as we haven't reset the hit rate statistics.
*/
if ( H5C_get_cache_hit_rate(cache_ptr, &hit_rate) != SUCCEED ) {
@@ -7032,7 +7032,7 @@ H5C_flush_invalidate_cache(H5F_t * f,
}
}
- /* The flush proceedure here is a bit strange.
+ /* The flush procedure here is a bit strange.
*
* In the outer while loop we make at least one pass through the
* cache, and then repeat until either all the pinned entries
@@ -7210,7 +7210,7 @@ H5C_flush_invalidate_cache(H5F_t * f,
*
* While this optimization used to be easy, with the possibility
* of new entries being added to the slist in the midst of the
- * flush, we must keep the slist in cannonical form at all
+ * flush, we must keep the slist in canonical form at all
* times.
*/
@@ -7783,7 +7783,7 @@ H5C_flush_single_entry(H5F_t * f,
if ( cache_ptr->aux_ptr != NULL ) {
HGOTO_ERROR(H5E_CACHE, H5E_SYSTEM, FAIL, \
- "resize/move in serialize occured in parallel case.")
+ "resize/move in serialize occurred in parallel case.")
}
}