Document fuel tank creation via the Platform API

docs/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-a-currency-token.md

@@ -319,7 +319,7 @@ For Token ID management, head to [Best Practices > TokenID Structure](/02-guides
 :::info Explore More Arguments
 For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
 
-`createToken` also accepts `cap`, `attributes`, and `groups` (token-group membership). To sign with a managed wallet instead of the Wallet Daemon, set `signerAccount` on `CreateTransaction`.
+`createToken` also accepts `cap`, `attributes`, and `groups` (token-group membership). To sign with a managed wallet instead of the Wallet Daemon, set `signerAddress` on `CreateTransaction`.
 :::
 
 :::tip What's next?

docs/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md

@@ -372,7 +372,7 @@ For Token ID management, head to [Best Practices > TokenID Structure](/02-guides
 :::info Explore More Arguments
 For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
 
-In addition to the fields shown above, `createToken` accepts `cap`, `behavior` (currency / royalty configuration), `attributes`, and `groups` (token-group membership). To sign with a managed wallet instead of the Wallet Daemon, set `signerAccount` on `CreateTransaction`.
+In addition to the fields shown above, `createToken` accepts `cap`, `behavior` (currency / royalty configuration), `attributes`, and `groups` (token-group membership). To sign with a managed wallet instead of the Wallet Daemon, set `signerAddress` on `CreateTransaction`.
 :::
 
 :::tip What's next?

docs/02-guides/01-platform/01-managing-tokens/03-adding-metadata.md

@@ -452,7 +452,7 @@ Check the [Best Practices for Collection/Token Metadata](/02-guides/01-platform/
 :::info Explore More Arguments
 For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
 
-To sign with a managed wallet instead of the Wallet Daemon, set `signerAccount` on `CreateTransaction`.
+To sign with a managed wallet instead of the Wallet Daemon, set `signerAddress` on `CreateTransaction`.
 :::
 
 :::tip What's next?

docs/02-guides/01-platform/01-managing-tokens/04-minting-a-token.md

@@ -336,7 +336,7 @@ Once it reaches `FINALIZED`, a `MultiTokens.Minted` event is emitted for each re
 :::info Explore More Arguments
 For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
 
-If you want to create _and_ mint new tokens together, use `createTokens` instead of `mintTokens`. To sign with a managed wallet instead of the Wallet Daemon, set `signerAccount` on `CreateTransaction`.
+If you want to create _and_ mint new tokens together, use `createTokens` instead of `mintTokens`. To sign with a managed wallet instead of the Wallet Daemon, set `signerAddress` on `CreateTransaction`.
 :::
 
 :::tip You've minted a token!

docs/02-guides/01-platform/01-managing-tokens/05-transferring-tokens.md

@@ -685,5 +685,5 @@ Once a transfer transaction reaches `FINALIZED`, a `MultiTokens.Transferred` eve
 :::info Explore More Arguments
 For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
 
-To sign with a managed wallet instead of the Wallet Daemon, set `signerAccount` on `CreateTransaction` / `CreateBatchTransaction`.
+To sign with a managed wallet instead of the Wallet Daemon, set `signerAddress` on `CreateTransaction` / `CreateBatchTransaction`.
 :::

docs/02-guides/01-platform/01-managing-tokens/07-freezing-thawing.md

@@ -928,7 +928,7 @@ For each of these actions, an event is emitted once the transaction reaches `FIN
 :::info Explore More Arguments
 For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
 
-To sign with a managed wallet instead of the Wallet Daemon, set `signerAccount` on `CreateTransaction`.
+To sign with a managed wallet instead of the Wallet Daemon, set `signerAddress` on `CreateTransaction`.
 :::
 
 :::tip Need to send a transaction request to user's wallet?

docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/02-using-wallet-connect.md

@@ -170,25 +170,25 @@ Every on-chain action is created through the `CreateTransaction` mutation — th
       'Authorization': 'Bearer my-auth-key',
     },
     body: JSON.stringify({
-      query: `mutation CreateTransaction($signerAccount: String!) {
+      query: `mutation CreateTransaction($signerAddress: String!) {
         CreateTransaction(
             network: CANARY,
             chain: MATRIX,
-            signerAccount: $signerAccount,
+            signerAddress: $signerAddress,
             transaction: { createCollection: {} }
         ) {
             uuid
             encodedData
         }
     }`,
       variables: {
-        signerAccount: req.query.address
+        signerAddress: req.query.address
       }
     })
   });
 ```
 
-We are also passing the `signerAccount`. This is necessary so your daemon doesn't sign the transaction.
+We are also passing the `signerAddress`. This is necessary so your daemon doesn't sign the transaction.
 In the mutation response, we're asking for the `uuid` and `encodedData`, which we will use in the next step.
 
 ### Step #2: Sending the Transaction Request to user's wallet

docs/02-guides/01-platform/02-managing-users/03-using-managed-wallets.md

@@ -649,7 +649,7 @@ By default, every transaction the Enjin Platform creates is signed by your [Wall
 Both `CreateTransaction` and `CreateBatchTransaction` accept two optional arguments for this:
 
 - **`signerExternalId`** — the managed wallet's `externalId`. This is the most direct option, as you don't need to look the wallet's public key up first.
-- **`signerAccount`** — the managed wallet's public key, as returned by [`GetManagedWallet`](#finding-a-managed-wallet).
+- **`signerAddress`** — the managed wallet's public key, as returned by [`GetManagedWallet`](#finding-a-managed-wallet).
 
 Set either one, and the platform signs that transaction with the corresponding managed wallet instead of the Wallet Daemon. Because these arguments live on `CreateTransaction` itself, **any** on-chain action — a transfer, a listing, an attribute change, anything you set on the `transaction` input — can be performed as a managed wallet.
 
@@ -901,7 +901,7 @@ print(response.json())
   </TabItem>
 </Tabs>
 
-Make sure `signerExternalId` (or `signerAccount`) is set to the managed wallet that holds the token being transferred.
+Make sure `signerExternalId` (or `signerAddress`) is set to the managed wallet that holds the token being transferred.
 
 Whether you're minting into a managed wallet or transferring out of one, the on-chain transaction emits the usual events on `FINALIZED` (e.g. `MultiTokens.Minted`, `MultiTokens.Transferred`) — with the managed wallet's address as the signer. See [Working with Events](/05-enjin-platform/03-working-with-events.md) for how to read them.