mirror of
https://github.com/bitcoin/bitcoin.git
synced 2026-06-10 14:48:46 +02:00
doc: fix typos
Co-authored-by: Ragnar <rodiondenmark@gmail.com> Co-authored-by: VolodymyrBg <aqdrgg19@gmail.com>
This commit is contained in:
@@ -194,7 +194,7 @@ You can do:
|
||||
git range-diff master previously-reviewed-head new-head
|
||||
```
|
||||
|
||||
Note that `git range-diff` also work for rebases:
|
||||
Note that `git range-diff` also works for rebases:
|
||||
|
||||
```
|
||||
P1--P2--P3--P4--P5 <-- previously-reviewed-head
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
- Logs now include which peer sent us a header. Additionaly there are fewer
|
||||
- Logs now include which peer sent us a header. Additionally there are fewer
|
||||
redundant header log messages. A side-effect of this change is that for
|
||||
some untypical cases new headers aren't logged anymore, e.g. a direct
|
||||
`BLOCK` message with a previously unknown header and `submitheader` RPC. (#27826)
|
||||
|
||||
@@ -127,7 +127,7 @@ serialized transaction.
|
||||
|
||||
Notifies about all transactions, both when they are added to mempool or when a new block
|
||||
arrives. This means a transaction could be published multiple times: first when it enters
|
||||
mempool and then again in each block that includes it. The body part of the mesage is the
|
||||
mempool and then again in each block that includes it. The body part of the message is the
|
||||
32-byte transaction hash in reversed byte order.
|
||||
|
||||
#### rawblock
|
||||
|
||||
Reference in New Issue
Block a user