From 66fbb4545a20849bdd21ee246cafbef728fbcb20 Mon Sep 17 00:00:00 2001 From: "fuder.eth" <139509124+vtjl10@users.noreply.github.com> Date: Mon, 23 Dec 2024 13:52:30 +0200 Subject: [PATCH] docs: fix typos in documentation files (#23063) (cherry picked from commit d1f9fd8f36a9226d88a7b30aec0a3364895288e4) --- docs/user/run-node/04-rosetta.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user/run-node/04-rosetta.md b/docs/user/run-node/04-rosetta.md index ec983f2b6fe3..3e295d5d4335 100644 --- a/docs/user/run-node/04-rosetta.md +++ b/docs/user/run-node/04-rosetta.md @@ -74,13 +74,13 @@ rosetta ## Plugins - Multi chain connections -Rosetta will try to reflect the node types through reflection over the node gRPC endpoints, there may be cases were this approach is not enough. It is possible to extend or implement the required types easily through plugins. +Rosetta will try to reflect the node types through reflection over the node gRPC endpoints, there may be cases where this approach is not enough. It is possible to extend or implement the required types easily through plugins. To use Rosetta over any chain, it is required to set up prefixes and registering zone specific interfaces through plugins. -Each plugin is a minimalist implementation of `InitZone` and `RegisterInterfaces` which allow Rosetta to parse chain specific data. There is an example for cosmos-hub chain under `plugins/cosmos-hun/` folder +Each plugin is a minimalist implementation of `InitZone` and `RegisterInterfaces` which allow Rosetta to parse chain specific data. There is an example for cosmos-hub chain under `plugins/cosmos-hub/` folder - **InitZone**: An empty method that is executed first and defines prefixes, parameters and other settings. -- **RegisterInterfaces**: This method receives an interface registry which is were the zone specific types and interfaces will be loaded +- **RegisterInterfaces**: This method receives an interface registry which is where the zone specific types and interfaces will be loaded In order to add a new plugin: 1. Create a folder over `plugins` folder with the name of the desired zone