diff options
| author | MacroFake <falke.marco@gmail.com> | 2022-10-31 11:46:13 +0100 |
|---|---|---|
| committer | MacroFake <falke.marco@gmail.com> | 2022-10-31 11:46:43 +0100 |
| commit | 2856dee808620a6518e86cd333eebdbf1a7e1344 (patch) | |
| tree | cfbe5435e408e736bae2d31b2860e43396a34243 /doc | |
| parent | c75c0d8e1147079ab1aef088e0a2486d295ab625 (diff) | |
| parent | 180eac0f73b7d96861f9626ebb701d9a46585a5b (diff) | |
Merge bitcoin/bitcoin#26402: doc: Fix typos
180eac0f73b7d96861f9626ebb701d9a46585a5b Fix: typos (omahs)
Pull request description:
Fix: typos
ACKs for top commit:
aureleoules:
ACK 180eac0f73b7d96861f9626ebb701d9a46585a5b
Tree-SHA512: 23150f3408a2eb9cb298c6add16d1bcb149da277238786f053c2896c803f896b07555b3dc71e15cd8d390023800c8e006f931f415f887bab69ee5bd4b0420581
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tracing.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/tracing.md b/doc/tracing.md index b6e3b9263a..6e60901496 100644 --- a/doc/tracing.md +++ b/doc/tracing.md @@ -76,7 +76,7 @@ the passed message. #### Tracepoint `net:outbound_message` -Is called when a message is send to a peer over the P2P network. Passes +Is called when a message is sent to a peer over the P2P network. Passes information about our peer, the connection and the message as arguments. Arguments passed: @@ -116,7 +116,7 @@ added to and removed (spent) from the cache when we connect a new block. (`chainstate.CoinsTip()`). For example, the RPCs `generateblock` and `getblocktemplate` call `TestBlockValidity()`, which applies the UTXO set changes to a temporary cache. Similarly, mempool consistency checks, which are -frequent on regtest, also apply the the UTXO set changes to a temporary cache. +frequent on regtest, also apply the UTXO set changes to a temporary cache. Changes to the _main_ UTXO cache and to temporary caches trigger the tracepoints. We can't tell if a temporary cache or the _main_ cache was changed. @@ -253,8 +253,8 @@ TRACE6(net, inbound_message, ### Guidelines and best practices -#### Clear motivation and use-case -Tracepoints need a clear motivation and use-case. The motivation should +#### Clear motivation and use case +Tracepoints need a clear motivation and use case. The motivation should outweigh the impact on, for example, code readability. There is no point in adding tracepoints that don't end up being used. |