diff options
| author | Jon Atack <jon@atack.com> | 2022-02-17 12:54:39 +0100 |
|---|---|---|
| committer | Jon Atack <jon@atack.com> | 2022-02-21 19:07:29 +0100 |
| commit | 48742693acc9de837735674057c9aae2fe90bd1d (patch) | |
| tree | 77aafdc1af1ed5016ef365e07dce7c63496d3aab /doc | |
| parent | e670edd43441ecb6e5978d65348501c57d856030 (diff) | |
Replace "can not" with "cannot" in docs, user messages, and tests
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/developer-notes.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/developer-notes.md b/doc/developer-notes.md index 1888897856..bfb64093e1 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -331,7 +331,7 @@ other input. failure, it will throw an exception, which can be caught to recover from the error. - For example, a nullptr dereference or any other logic bug in RPC code - means that the RPC code is faulty and can not be executed. However, the + means that the RPC code is faulty and cannot be executed. However, the logic bug can be shown to the user and the program can continue to run. * `Assume` should be used to document assumptions when program execution can safely continue even if the assumption is violated. In debug builds it @@ -1199,7 +1199,7 @@ A few guidelines for introducing and reviewing new RPC interfaces: - Don't forget to fill in the argument names correctly in the RPC command table. - - *Rationale*: If not, the call can not be used with name-based arguments. + - *Rationale*: If not, the call cannot be used with name-based arguments. - Add every non-string RPC argument `(method, idx, name)` to the table `vRPCConvertParams` in `rpc/client.cpp`. |