diff --git a/docs/02-addresses.html b/docs/02-addresses.html index d454236..fb3cd47 100644 --- a/docs/02-addresses.html +++ b/docs/02-addresses.html @@ -65,7 +65,7 @@

All contracts are deployed by sending them a message. While any message can be used for this purpose, best practice is to use the special Deploy message.

This message has a single field, queryId, provided by the deployer (usually set to zero). If the deployment succeeds, the contract will reply with a DeployOk message and echo the same queryId in the response.


-

If you're using Tact's auto-generated TypeScript classes to deploy, sending the deploy message should look like:

+

If you're using Tact's auto-generated TypeScript classes to deploy, sending the deploy message should look like:

const msg = { $$type: "Deploy", queryId: 0n };
 await contract.send(sender, { value: toNano(1) }, msg);
 
diff --git a/docs/03-sender.html b/docs/03-sender.html index 56a4086..d995974 100644 --- a/docs/03-sender.html +++ b/docs/03-sender.html @@ -70,7 +70,7 @@

The intricate math

Info: More details for different sending modes can check - here + here