mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-06-29 10:19:26 +02:00
Replace "can not" with "cannot" in docs, user messages, and tests
This commit is contained in:
@ -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`.
|
||||
|
||||
|
Reference in New Issue
Block a user