Skip to content

Commit

Permalink
Improve grammar: "create" -> "have created" (#1148)
Browse files Browse the repository at this point in the history
Changed to present perfect tense ("have created") to accurately reflect the recent completion of the action.
  • Loading branch information
roudra323 authored Mar 23, 2024
1 parent 214dba7 commit b46648d
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/tutorials/solidity-scripting.md
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@ The next line just imports the `NFT` contract.
contract MyScript is Script {
```

We create a contract called `MyScript` and it inherits `Script` from Forge Std.
We have created a contract called `MyScript` and it inherits `Script` from Forge Std.

```solidity
function run() external {
Expand All @@ -224,7 +224,7 @@ This is a special cheatcode that records calls and contract creations made by ou
NFT nft = new NFT("NFT_tutorial", "TUT", "baseUri");
```

Here we just create our NFT contract. Because we called `vm.startBroadcast()` before this line, the contract creation will be recorded by Forge, and as mentioned previously, we can broadcast the transaction to deploy the contract on-chain. The broadcast transaction logs will be stored in the `broadcast` directory by default. You can change the logs location by setting [`broadcast`](../reference/config/project.md#broadcast) in your `foundry.toml` file.
Here we have just created our NFT contract. Because we called `vm.startBroadcast()` before this line, the contract creation will be recorded by Forge, and as mentioned previously, we can broadcast the transaction to deploy the contract on-chain. The broadcast transaction logs will be stored in the `broadcast` directory by default. You can change the logs location by setting [`broadcast`](../reference/config/project.md#broadcast) in your `foundry.toml` file.

Now that you’re up to speed about what the script smart contract does, let’s run it.

Expand Down

0 comments on commit b46648d

Please sign in to comment.