Merge pull request #20 from SC-One/dev_patch

Message correction

Author: howardpen9

docs/_app/immutable/entry/(examples)-06-contract-deploy-another-page.svelte.ad13b189.js

@@ -37,7 +37,7 @@
         return [await contract2.send(sender, { value: toNano(1) }, "identify")];
       },
       '"deploy 2nd" to 1': async () => {
-        return [await contract.send(sender, { value: toNano(1) }, "deploy next")];
+        return [await contract.send(sender, { value: toNano(1) }, "deploy 2nd")];
       },
     },
     getters: {},

src/routes/(examples)/06-contract-deploy-another/+page.svelte

@@ -4,12 +4,12 @@ Contracts are not necessarily only deployed by users, they can also be deployed
 
 In this example, when pressing the <span class="mdButton blue">Deploy</span> button, we only deploy one contract instance - the one with constructor argument 1.
 
-The second instance (with constructor argument 2) will be deployed by the first contract instance when it receives the `deploy next` message. Send this message to the first instance by pressing the <span class="mdButton grape">Send "deploy 2nd" to 1</span> button.
+The second instance (with constructor argument 2) will be deployed by the first contract instance when it receives the `deploy 2nd` message. Send this message to the first instance by pressing the <span class="mdButton grape">Send "deploy 2nd" to 1</span> button.
 
 ## Messages containing state init
 
 The combination of the inital code and the initial data of a contract is called the *stateInit* of the contract.
 
 When sending any message to a contract, we can attach its *stateInit* by specifying the `code` and `data` fields of the message. This will deploy the contract if it has not already been deployed. If the contract has already been deployed, these fields will be ignored.
 
-Notice that in this example, we piggyback the deployment on the `indentify` message.
+Notice that in this example, we piggyback the deployment on the `indentify` message.