From 40a23b67eaddae2da87ce2c69d2d267168dcc0a8 Mon Sep 17 00:00:00 2001 From: Larry Knox Date: Tue, 7 Dec 2021 15:07:15 -0600 Subject: [PATCH] Correct spelling correction of preceed incorrectly to proceed. Should (#1268) * Correct spelling correction of 'preceed' incorrectly to 'proceed'. It should be 'precede'. --- src/H5C.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/H5C.c b/src/H5C.c index 09c19cecfc..d34c65013e 100644 --- a/src/H5C.c +++ b/src/H5C.c @@ -1484,7 +1484,7 @@ H5C_insert_entry(H5F_t *f, const H5C_class_t *type, haddr_t addr, void *thing, u * Finally, we usually don't check to see if the cache is * oversized at the end of an unprotect. As a result, it is * possible to have a vastly oversized cache with no protected - * entries as long as all the protects proceed the unprotects. + * entries as long as all the protects precede the unprotects. * * Since items 1 and 2 are not changing any time soon, I see * no point in worrying about the third. @@ -2444,7 +2444,7 @@ H5C_protect(H5F_t *f, const H5C_class_t *type, haddr_t addr, void *udata, unsign * Finally, we usually don't check to see if the cache is * oversized at the end of an unprotect. As a result, it is * possible to have a vastly oversized cache with no protected - * entries as long as all the protects proceed the unprotects. + * entries as long as all the protects precede the unprotects. * * Since items 1, 2, and 3 are not changing any time soon, I * see no point in worrying about the fourth.