From e9a77676883d5b072546db5b9ca74412854b6e42 Mon Sep 17 00:00:00 2001 From: hattizai <150505746+hattizai@users.noreply.github.com> Date: Wed, 29 Nov 2023 22:52:31 +0800 Subject: [PATCH] fix typos in doc (#1219) --- docs/src/calling-contracts/other-contracts.md | 2 +- docs/src/calling-contracts/read-only.md | 2 +- docs/src/connecting/external-node.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/calling-contracts/other-contracts.md b/docs/src/calling-contracts/other-contracts.md index a8c6c030be..0df2b1b6b9 100644 --- a/docs/src/calling-contracts/other-contracts.md +++ b/docs/src/calling-contracts/other-contracts.md @@ -1,6 +1,6 @@ # Calling other contracts -If your contract method is calling other contracts you will have to add the appropriate `Inputs` and `Outputs` to your transaction. For your convenience, the `ContractCallHandler` provides methods that prepare those inputs and outpus for you. You have two methods that you can use: `with_contracts(&[&contract_instance, ...])` and `with_contract_ids(&[&contract_id, ...])`. +If your contract method is calling other contracts you will have to add the appropriate `Inputs` and `Outputs` to your transaction. For your convenience, the `ContractCallHandler` provides methods that prepare those inputs and outputs for you. You have two methods that you can use: `with_contracts(&[&contract_instance, ...])` and `with_contract_ids(&[&contract_id, ...])`. `with_contracts(&[&contract_instance, ...])` requires contract instances that were created using the `abigen` macro. When setting the external contracts with this method, logs and require revert errors originating from the external contract can be propagated and decoded by the calling contract. diff --git a/docs/src/calling-contracts/read-only.md b/docs/src/calling-contracts/read-only.md index 43b90743c2..72444bffdc 100644 --- a/docs/src/calling-contracts/read-only.md +++ b/docs/src/calling-contracts/read-only.md @@ -13,7 +13,7 @@ You can do this with the SDK. Instead of `.call()`ing the method, use `.simulate {{#include ../../../examples/contracts/src/lib.rs:simulate}} ``` - + Note that if you use `.simulate()` on a method that _does_ change the state of the blockchain, it won't work properly; it will just `dry-run` it. diff --git a/docs/src/connecting/external-node.md b/docs/src/connecting/external-node.md index 08e3b47fa9..5e752ad80c 100644 --- a/docs/src/connecting/external-node.md +++ b/docs/src/connecting/external-node.md @@ -18,7 +18,7 @@ In the code example, we connected a new provider to the Testnet node and created > > Once the assets have been transferred to the wallet, you can reuse it in other tests by providing the private key! > -> In addition to the faucet, there is a block explorer for the Tesnet at +> In addition to the faucet, there is a block explorer for the Testnet at > > [block-explorer](https://fuellabs.github.io/block-explorer-v2)