From 76bd4e338139e1a96faf64238adc80faf9c5a8cf Mon Sep 17 00:00:00 2001 From: ipopescu Date: Wed, 24 Jan 2024 16:04:40 +0100 Subject: [PATCH] Changing the wording based on feedback --- .../casper/resources/advanced/transfer-token-to-contract.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/docs/casper/resources/advanced/transfer-token-to-contract.md b/source/docs/casper/resources/advanced/transfer-token-to-contract.md index 29ba284b71..95b15831b3 100644 --- a/source/docs/casper/resources/advanced/transfer-token-to-contract.md +++ b/source/docs/casper/resources/advanced/transfer-token-to-contract.md @@ -7,7 +7,7 @@ slug: /resources/tutorials/advanced/transfer-token-to-contract This tutorial covers two methods to handle tokens via a contract. This is not a native process to a Casper network and will require the use of custom code. The following two scenarios provide a framework for developers and the pros and cons of each example. Developers should choose the option that best suits their individual needs. -For increased security, token transfers from a main purse must be handled via contract code, not session code as in [other cases](../../developers/writing-onchain-code/writing-session-code.md#example-3-transfers-using-session-code-transfers-using-session-code). In this case, `transfer-*` methods are unavailable in stored session code, even when the stored session runs in the account context. +For increased security, token transfers from a main purse must be handled via session code (WASM), as shown [here](../../developers/writing-onchain-code/writing-session-code.md#example-3-transfers-using-session-code-transfers-using-session-code). Therefore, `transfer-*` methods are unavailable in stored WASM for tokens originating from an account's main purse, even when the stored WASM runs in the account context. ## Scenario 1 - Creating a Throw-Away Purse {#scenario1}