From e942c321f0c1b9337387084192c9c7a3fd356b34 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9rgio=20Seco?= <52105707+SurgeCode@users.noreply.github.com> Date: Mon, 22 Jul 2024 11:17:08 +0100 Subject: [PATCH] Update docs/2.build/1.chain-abstraction/meta-transactions.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Damián Parrino --- docs/2.build/1.chain-abstraction/meta-transactions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/2.build/1.chain-abstraction/meta-transactions.md b/docs/2.build/1.chain-abstraction/meta-transactions.md index 6adb382c4ca..7deb6370ae4 100644 --- a/docs/2.build/1.chain-abstraction/meta-transactions.md +++ b/docs/2.build/1.chain-abstraction/meta-transactions.md @@ -112,7 +112,7 @@ When running a relayer that handles a large number of transactions, issues will Fortunately, this is easy to resolve. Adding multiple full access keys to the NEAR account used for relaying (up to 20 keys can make a significant difference) will help. Then, relaying transactions using instances of the Account object created from the various keypairs associated with the account. -To add a key, generate a new keypair and use the original account object to call the addKey method +To add a key, generate a new key pair and use the original account object to call the `addKey` method: ```typescript const keyPair = nearAPI.KeyPair.fromRandom("ed25519");