fixed typo in signature-provider

eosnetworkfoundation · May 23, 2024 · 767c0a7 · 767c0a7
2 parents 4dbeb53 + 0a07123
commit 767c0a7
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/native/07_node-operation/100_migration-guides/04_upgrade-guide-spring-1-0.md b/native/07_node-operation/100_migration-guides/04_upgrade-guide-spring-1-0.md
@@ -95,7 +95,7 @@ State history log file compression has been disabled. Consumers with state histo
 ### Finalizer Keys
 The Savanna Consensus algorithm utilized by Spring v1 separates the roles of publishing blocks from signing and finalizing blocks. Finalizer Keys are needed to sign and finalize blocks. In Spring v1, all block producers are expected to be finalizers. There are three steps to creating finalizer keys
 - generate your key(s) using `spring-utils`
-- add `signature-provided` to configuration with the generated key(s)
+- add `signature-provider` to configuration with the generated key(s)
 - register a single key on chain with the `regfinkey` action
 
 Additional Documentation may be found in [Guide to Managing Finalizer Keys](../../advanced-topics/managing-finalizer-keys)
diff --git a/native/07_node-operation/100_migration-guides/10_switch-to-savanna.md b/native/07_node-operation/100_migration-guides/10_switch-to-savanna.md
@@ -34,8 +34,8 @@ The protocol feature `INSTANT_FINALITY` depends on the following protocol featur
 ### Generate and Registering Finalizer Keys
 The Savanna Consensus algorithm utilized by Spring v1 separates the roles of publishing blocks from signing and finalizing blocks. Finalizer Keys are needed to sign and finalize blocks. In Spring v1, all block producers are expected to be finalizers. There are three steps to creating finalizer keys
 - generate your key(s) using `spring-utils`
-- add `signature-provided` to configuration with the generated key(s)
-- restart nodeos with the new `signature-provided` config
+- add `signature-provider` to configuration with the generated key(s)
+- restart nodeos with the new `signature-provider` config
 - register a single key on chain with the `regfinkey` action
 
 Additional information on Finalizer Keys may be found in [Guide to Managing Finalizer Keys](../../advanced-topics/managing-finalizer-keys)

diff --git a/native/60_advanced-topics/05_managing-finalizer-keys.md b/native/60_advanced-topics/05_managing-finalizer-keys.md
@@ -39,7 +39,7 @@ Proof of Possession: SIG_BLS_ZPZZbZIZukZksBbZ9Z9Zfysz9zZsy9z9S9V99Z-9rZZe99vZUzZ
 ```
 
 ### Add Finalizer Keys to Config
-You may add several finalizer keys to configuration. **NOTE** Instances of nodeos must be restarted to pick up the new configuration options. Keys are added to configuration with the `signature-provided` option. These keys may be added via the command line or placed into a configuration file. Placing the finalizer keys into a configuration file would look like this.
+You may add several finalizer keys to configuration. **NOTE** Instances of nodeos must be restarted to pick up the new configuration options. Keys are added to configuration with the `signature-provider` option. These keys may be added via the command line or placed into a configuration file. Placing the finalizer keys into a configuration file would look like this.
 `signature-provider = PUBLIC_KEY=KEY:PRIVATE_KEY`
 For example
 `signature-provider = PUB_BLS_SvLa9z9kZoT9bzZZZ-Zezlrst9Zb-Z9zZV9olZazZbZvzZzk9r9ZZZzzarUVzbZZ9Z9ZUzf9iZZ9P_kzZZzGLtezL-Z9zZ9zzZb9ZitZctzvSZ9G9SUszzcZzlZu-GsZnZ9I9Z=KEY:PVT_BLS_9-9ziZZzZcZZoiz-ZZzUtz9ZZ9u9Zo9aS9BZ-o9iznZfzUZU`