From 96d40acd169541d70a548e3b5cdf54682e4f4140 Mon Sep 17 00:00:00 2001 From: osrm <90407222+osrm@users.noreply.github.com> Date: Fri, 20 Dec 2024 18:41:59 +0900 Subject: [PATCH 1/3] fix typo 01-run-node.md "Bootsrapping" -> "Bootstrapping" --- docs/user/run-node/01-run-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/run-node/01-run-node.md b/docs/user/run-node/01-run-node.md index 7f4bc247c801..7a4bdae535e6 100644 --- a/docs/user/run-node/01-run-node.md +++ b/docs/user/run-node/01-run-node.md @@ -198,7 +198,7 @@ Local state sync work similar to normal state sync except that it works off a lo 1. As mentioned in https://docs.cometbft.com/v0.37/core/state-sync, one must set a height and hash in the config.toml along with a few rpc servers (the afromentioned link has instructions on how to do this). 2. Run ` ` to restore a local snapshot (note: first load it from a file with the *load* command). -3. Bootsrapping Comet state in order to start the node after the snapshot has been ingested. This can be done with the bootstrap command ` comet bootstrap-state` +3. Bootstrapping Comet state in order to start the node after the snapshot has been ingested. This can be done with the bootstrap command ` comet bootstrap-state` ### Snapshots Commands From 13b5149de4bf653a4d3f92562d00922410544789 Mon Sep 17 00:00:00 2001 From: osrm <90407222+osrm@users.noreply.github.com> Date: Fri, 20 Dec 2024 19:04:40 +0900 Subject: [PATCH 2/3] fix typo adr-063-core-module-api.md "ServiceRegitrar" -> "ServiceRegistrar" --- docs/architecture/adr-063-core-module-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/adr-063-core-module-api.md b/docs/architecture/adr-063-core-module-api.md index 74212b2982dd..f26e04d13c2b 100644 --- a/docs/architecture/adr-063-core-module-api.md +++ b/docs/architecture/adr-063-core-module-api.md @@ -226,7 +226,7 @@ type HasServices interface { ``` -Because of the `cosmos.msg.v1.service` protobuf option, required for `Msg` services, the same `ServiceRegitrar` can be +Because of the `cosmos.msg.v1.service` protobuf option, required for `Msg` services, the same `ServiceRegistrar` can be used to register both `Msg` and query services. #### Genesis From 3f15431ec2fb2d877947dbd95a086786f12b0851 Mon Sep 17 00:00:00 2001 From: osrm <90407222+osrm@users.noreply.github.com> Date: Fri, 20 Dec 2024 19:53:54 +0900 Subject: [PATCH 3/3] fix typo adr-023-protobuf-naming.md "fully-qualifed" -> "fully-qualified" --- docs/architecture/adr-023-protobuf-naming.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/adr-023-protobuf-naming.md b/docs/architecture/adr-023-protobuf-naming.md index 01bfd8bd94ca..7475ae96c62b 100644 --- a/docs/architecture/adr-023-protobuf-naming.md +++ b/docs/architecture/adr-023-protobuf-naming.md @@ -70,7 +70,7 @@ Further guidelines to be described below. Names should be descriptive enough to convey their meaning and distinguish them from other names. -Given that we are using fully-qualifed names within +Given that we are using fully-qualified names within `google.protobuf.Any` as well as within gRPC query routes, we should aim to keep names concise, without going overboard. The general rule of thumb should be if a shorter name would convey more or else the same thing, pick the shorter