From 601cd321c874e2aa4b57d4e8b1a5c49fae281290 Mon Sep 17 00:00:00 2001 From: David Salami Date: Sat, 12 Oct 2024 16:20:18 +0000 Subject: [PATCH] nit --- docs/pages/developers/polkadot/tokengateway.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pages/developers/polkadot/tokengateway.mdx b/docs/pages/developers/polkadot/tokengateway.mdx index f29402ce..731d3434 100644 --- a/docs/pages/developers/polkadot/tokengateway.mdx +++ b/docs/pages/developers/polkadot/tokengateway.mdx @@ -159,7 +159,7 @@ There are three scenarios that you need to understand when creating token gatewa This would instruct token gateway to not recreate the asset locally.
* **Registering entirely new assets on token gateway:**
To register assets that do not exist locally on token gateway, leave the `local_id` field empty when dispatching the extrinsic. Token gateway will create the assets locally before dispatching a request to hyperbridge.
- + This requires the `AssetAdmin` account configured for the pallet to have sufficient funds to pay for the asset metadata storage. Assets can also be updated in the same way by dispatching `update_erc6160_asset`.
## Asset Ids @@ -167,7 +167,7 @@ Assets can also be updated in the same way by dispatching `update_erc6160_asset` ## Teleporting assets -To make a crosschain transfer the `teleport` called must be dispatched with the required parameters. +To make a crosschain transfer the `teleport` extrinsic should must be dispatched with the correct parameters. ```rust pub struct TeleportParams {