From 3caec2433541b85a8fcb628c2bec3dbd25493024 Mon Sep 17 00:00:00 2001 From: T Date: Mon, 8 Jan 2024 01:28:54 -0500 Subject: [PATCH] docs: Fix typos, broken link, spacing in diagram (#18973) --- docs/learn/beginner/01-tx-lifecycle.md | 50 +++++++++++------------ docs/learn/beginner/02-query-lifecycle.md | 4 +- 2 files changed, 27 insertions(+), 27 deletions(-) diff --git a/docs/learn/beginner/01-tx-lifecycle.md b/docs/learn/beginner/01-tx-lifecycle.md index 8c8118fa38..52fb720cb1 100644 --- a/docs/learn/beginner/01-tx-lifecycle.md +++ b/docs/learn/beginner/01-tx-lifecycle.md @@ -164,44 +164,44 @@ As mentioned throughout the documentation `BeginBlock`, `ExecuteTx` and `EndBloc Although every full-node operates individually and locally, the outcome is always consistent and unequivocal. This is because the state changes brought about by the messages are predictable, and the transactions are specifically sequenced in the proposed block. ```text - ----------------------- - |Receive Block Proposal| - ----------------------- - | - v + -------------------------- + | Receive Block Proposal | + -------------------------- + | + v ------------------------- - | FinalizeBlock | - | - v - ------------------- - | BeginBlock | - ------------------- - | - v + | FinalizeBlock | + ------------------------- + | + v + ------------------- + | BeginBlock | + ------------------- + | + v -------------------- | ExecuteTx(tx0) | | ExecuteTx(tx1) | | ExecuteTx(tx2) | | ExecuteTx(tx3) | - | . | - | . | - | . | + | . | + | . | + | . | ------------------- - | - v + | + v -------------------- - | EndBlock | + | EndBlock | -------------------- - ------------------------- - | - v + | + v ----------------------- - | Consensus | + | Consensus | ----------------------- | - v + v ----------------------- - | Commit | + | Commit | ----------------------- ``` diff --git a/docs/learn/beginner/02-query-lifecycle.md b/docs/learn/beginner/02-query-lifecycle.md index 04e4fc9ed6..d4f2fed521 100644 --- a/docs/learn/beginner/02-query-lifecycle.md +++ b/docs/learn/beginner/02-query-lifecycle.md @@ -76,7 +76,7 @@ The first thing that is created in the execution of a CLI command is a `client.C * **Codec**: The [encoder/decoder](../advanced/05-encoding.md) used by the application, used to marshal the parameters and query before making the CometBFT RPC request and unmarshal the returned response into a JSON object. The default codec used by the CLI is Protobuf. * **Account Decoder**: The account decoder from the [`auth`](../../build/modules/auth/README.md) module, which translates `[]byte`s into accounts. * **RPC Client**: The CometBFT RPC Client, or node, to which requests are relayed. -* **Keyring**: A [Key Manager]../beginner/03-accounts.md#keyring) used to sign transactions and handle other operations with keys. +* **Keyring**: A [Key Manager](../beginner/03-accounts.md#keyring) used to sign transactions and handle other operations with keys. * **Output Writer**: A [Writer](https://pkg.go.dev/io/#Writer) used to output the response. * **Configurations**: The flags configured by the user for this command, including `--height`, specifying the height of the blockchain to query, and `--indent`, which indicates to add an indent to the JSON response. @@ -134,7 +134,7 @@ Once a result is received from the querier, `baseapp` begins the process of retu ## Response -Since `Query()` is an ABCI function, `baseapp` returns the response as an [`abci.ResponseQuery`](https://docs.cometbft.com/master/spec/abci/abci.html#query-2) type. The `client.Context` `Query()` routine receives the response and. +Since `Query()` is an ABCI function, `baseapp` returns the response as an [`abci.ResponseQuery`](https://docs.cometbft.com/master/spec/abci/abci.html#query-2) type. The `client.Context` `Query()` routine receives the response. ### CLI Response