From 4c4d403ecba80e372e413b219e44df2ff7339a52 Mon Sep 17 00:00:00 2001 From: Dimitris Apostolou Date: Wed, 2 Feb 2022 19:32:31 +0200 Subject: [PATCH] Fix typos --- programs/fileio_asyncio.c | 2 +- programs/fileio_asyncio.h | 2 +- tests/cli-tests/README.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/programs/fileio_asyncio.c b/programs/fileio_asyncio.c index 332292bbc..92c9a5b1d 100644 --- a/programs/fileio_asyncio.c +++ b/programs/fileio_asyncio.c @@ -415,7 +415,7 @@ static IOJob_t* AIO_ReadPool_findNextWaitingOffsetCompletedJob_locked(ReadPoolCt } /* AIO_ReadPool_numReadsInFlight: - * Returns the number of IO read jobs currrently in flight. */ + * Returns the number of IO read jobs currently in flight. */ static size_t AIO_ReadPool_numReadsInFlight(ReadPoolCtx_t* ctx) { const size_t jobsHeld = (ctx->currentJobHeld==NULL ? 0 : 1); return ctx->base.totalIoJobs - (ctx->base.availableJobsCount + ctx->completedJobsCount + jobsHeld); diff --git a/programs/fileio_asyncio.h b/programs/fileio_asyncio.h index bf07f8594..30db44b6e 100644 --- a/programs/fileio_asyncio.h +++ b/programs/fileio_asyncio.h @@ -151,7 +151,7 @@ void AIO_ReadPool_free(ReadPoolCtx_t* ctx); void AIO_ReadPool_consumeBytes(ReadPoolCtx_t *ctx, size_t n); /* AIO_ReadPool_fillBuffer: - * Makes sure buffer has at least n bytes loaded (as long as n is not bigger than the initalized bufferSize). + * Makes sure buffer has at least n bytes loaded (as long as n is not bigger than the initialized bufferSize). * Returns if srcBuffer has at least n bytes loaded or if we've reached the end of the file. * Return value is the number of bytes added to the buffer. * Note that srcBuffer might have up to 2 times bufferSize bytes. */ diff --git a/tests/cli-tests/README.md b/tests/cli-tests/README.md index 3098f466f..cdf9b8e71 100644 --- a/tests/cli-tests/README.md +++ b/tests/cli-tests/README.md @@ -67,9 +67,9 @@ They are generally used by the helper scripts in `bin/` to coordinate everything ### Basic test case -When executing your `$TEST` executable, by default the exit code is expected to be `0`. However, you can provide an alterate expected exit code in a `$TEST.exit` file. +When executing your `$TEST` executable, by default the exit code is expected to be `0`. However, you can provide an alternate expected exit code in a `$TEST.exit` file. -When executing your `$TEST` exectuable, by default the expected stderr and stdout are empty. However, you can override the default by providing one of three files: +When executing your `$TEST` executable, by default the expected stderr and stdout are empty. However, you can override the default by providing one of three files: * `$TEST.{stdout,stderr}.exact` * `$TEST.{stdout,stderr}.glob`