From 5b7c246685f269d4f1b94a5e3fbf5cf5c5008710 Mon Sep 17 00:00:00 2001 From: Ikko Ashimine Date: Tue, 25 Jan 2022 00:46:03 +0900 Subject: [PATCH] docs(RFC): fix typo in rfc-001.md (#2283) inadvertantly -> inadvertently --- rfcs/rfc-001.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/rfc-001.md b/rfcs/rfc-001.md index dcb67347d..2163400f6 100644 --- a/rfcs/rfc-001.md +++ b/rfcs/rfc-001.md @@ -5,7 +5,7 @@ In Nock v10/v11, the lifecycle methods are confusingly named, difficult to understand, and at times inconvenient. Unless they are studied carefully, it -is easy to inadvertantly leave unwanted state in Nock. +is easy to inadvertently leave unwanted state in Nock. Nock doesn't automatically provide a way to assert that mocks have been satisfied; it's the caller's responsibility to do this for each mock.