docs: fix spelling errors (#23038)

This commit is contained in:
osrm 2024-12-20 22:51:07 +09:00 committed by GitHub
parent b2c39e2bd0
commit 6ed94527c1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions

View File

@ -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

View File

@ -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

View File

@ -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 `<appd snapshot restore <height> <format>` 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 `<app> 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 `<app> comet bootstrap-state`
### Snapshots Commands