From 732e7fe9c4db5dc7da7c430ce8c8a3cb04de7f2c Mon Sep 17 00:00:00 2001 From: Kenton Varda Date: Fri, 26 Apr 2024 12:27:40 -0500 Subject: [PATCH] Drive-by: Typos in worker-rpc.c++. --- src/workerd/api/worker-rpc.c++ | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/workerd/api/worker-rpc.c++ b/src/workerd/api/worker-rpc.c++ index 4b591cbd0df..a26fe8cb74e 100644 --- a/src/workerd/api/worker-rpc.c++ +++ b/src/workerd/api/worker-rpc.c++ @@ -939,9 +939,9 @@ public: // object's lifetime is that of the RPC call, but in reality they are refcounted under the // hood. Since well be executing the call in the JS microtask queue, we have no ability to // actually cancel execution if a cancellation arrives over RPC, and at the end of that - // execution we're going to accell the call context to write the results. We could invent some + // execution we're going to access the call context to write the results. We could invent some // complicated way to skip initializing results in the case the call has been canceled, but - // it's easier and safer to just grap a refcount on the call context object itself, which + // it's easier and safer to just grab a refcount on the call context object itself, which // fully protects us. So... do that. auto ownCallContext = capnp::CallContextHook::from(callContext).addRef();