Update content and fix some typo

Author: howardpen9

pages/index.mdx

@@ -1,7 +1,18 @@
 # Tact Documentation
 
-Tact is a new programming language for TON blockchain that is focused on efficiency and simplicity. It is designed to be easy to learn and use, and to be a good fit for smart contracts. Tact is a statically typed language with a simple syntax and a powerful type system.
+![Banner](public/banner.jpeg)
 
-* [Getting Started](/start)
-* [Language and stdlib documentation](/language/guides/types)
-* [Tools](/tools/typescript)
+**Tact is a new programming language for TON blockchain that is focused on efficiency and simplicity.**
+
+**It is designed to be easy to learn and use, and to be a good fit for smart contracts. Tact is a statically typed language with a simple syntax and a powerful type system.**
+
+### Content
+
+- [Getting Started](/start)
+- [Language and stdlib documentation](/language/guides/types)
+- [Tools](/tools/typescript)
+
+### Community
+
+- [✈️ Telegram Group](https://t.me/tactlang)
+- [🐦 Twitter](https://twitter.com/tact_language)

pages/start/deploy.mdx

@@ -4,37 +4,41 @@ Template project provides a handy way to deploy contracts, but you can do it you
 
 ## Deploying with typescript and deploy link
 
-To deploy a smart contract in TON you need to send a message with `init` data attached to it. The easiest way to get an `init` for your contract is using a generated typescript bindings that would help to call an init function. 
+To deploy a smart contract in TON you need to send a message with `init` data attached to it. The easiest way to get an `init` for your contract is using a generated typescript bindings that would help to call an init function.
 
 ```typescript
-import base64url from 'base64url';
-import qs from 'qs';
-import { Address, beginCell, storeStateInit } from 'ton';
-import { Counter } from './output/sample_Counter';
+import base64url from "base64url";
+import qs from "qs";
+import { Address, beginCell, storeStateInit } from "ton";
+import { Counter } from "./output/sample_Counter";
 
 // Forming an init package
-let owner = Address.parse('some-address');
+let owner = Address.parse("some-address");
 let init = await Counter.init(owner);
 let testnet = true;
 
 // Contract address
 let address = contractAddress(0, init);
 
 // Amount of TONs to attach to a deploy message
-let deployAmount = toNano('0.5');
+let deployAmount = toNano("0.5");
 
 // Create string representation of an init package
-let initStr = base64url(beginCell()
-        .store(storeStateInit(init))
-        .endCell()
-        .toBoc({ idx: false }));
+let initStr = base64url(
+  beginCell().store(storeStateInit(init)).endCell().toBoc({ idx: false })
+);
 
 // Create a deploy link
-console.log(`ton://transfer/` + address.toString({ testOnly: testnet }) + "?" + qs.stringify({
-    text: 'Deploy',
-    amount: deployAmount.toString(10),
-    init: initStr
-}));
+console.log(
+  `ton://transfer/` +
+    address.toString({ testOnly: testnet }) +
+    "?" +
+    qs.stringify({
+      text: "Deploy",
+      amount: deployAmount.toString(10),
+      init: initStr,
+    })
+);
 ```
-    
-After running this code you will get a link that you can open in your favorite TON wallet. It will open a transfer page with a deploy message already filled in. You can change the amount of TONs to attach to a deploy message and click on the `Send` button. After a few seconds your contract will be deployed and you will see a transaction in your wallet.
+
+After running this code you will get a link that you can open in your favorite TON wallet. It will open a transfer page with a deploy message already filled in. You can change the amount of TONs to attach to a deploy message and click on the `Send` button. After a few seconds your contract will be deployed and you will see a transaction in your wallet.

pages/start/first.mdx

@@ -3,9 +3,10 @@
 TON contract is an isolated object that have state and code, can send and receive messages and export get-methods for off-chain reading of a contract state.
 
 The code of the contract dictates how:
-* it manipulates it's own state
-* it reacts to incoming messages
-* exposes it's state to off-chain world
+
+- it manipulates it's own state
+- it reacts to incoming messages
+- exposes it's state to off-chain world
 
 ## Contract example
 
@@ -47,14 +48,14 @@ This contract has two state variables that persisted between contract calls: `ow
 Notation `receive("increment")` means declaration of a `receiver` function that will be called when a text with value `"increment"` is sent to the contract. The function body can modify the state of the contract and send messages to other contracts. It is impossbile to call `receiver` directly. If you need to reuse some logic you can declare a function and call it from `receiver`.
 
 There are several receiver functions. All receiver functions are processed in the order they are listed below:
-* `receive()` - called when an empty message is sent to the contract
-* `receive("message")` - called when a text message with a specific comment is sent to the contract
-* `receive(str: String)` - called when an arbitrary text message is sent to the contract
-* `receive(msg: MyMessage)` - called when binary message of type `MyMessage` is sent to the contract
-* `receive(msg: Slice)` - called when binary message of unknown type is sent to the contract
-* `bounced(msg: Slice)` - called when outgoing message bounced
 
+- `receive()` - called when an empty message is sent to the contract
+- `receive("message")` - called when a text message with a specific comment is sent to the contract
+- `receive(str: String)` - called when an arbitrary text message is sent to the contract
+- `receive(msg: MyMessage)` - called when binary message of type `MyMessage` is sent to the contract
+- `receive(msg: Slice)` - called when binary message of unknown type is sent to the contract
+- `bounced(msg: Slice)` - called when outgoing message bounced
 
 ## Getters
 
-There are two getters in this contract `counter` and `owner` that returns current counter value and `owner` of a contract. Getters are **not accessible from other contracts** and exported only to off-chain world.
+There are two getters in this contract `counter` and `owner` that returns current counter value and `owner` of a contract. Getters are **not accessible from other contracts** and exported only to off-chain world.

pages/start/index.mdx

@@ -1,16 +1,18 @@
 # Welcome to Tact
 
-There are two ways to start with tact: using template and starting from scratch. We recommend using template as it contains a simple contract that can be deployed to the TON blockchain, example of implementing unit tests and helper functions for contract deployment.
+There are two ways to start with Tact: using a template or starting from scratch.
+
+We recommend using a template, as it contains a **simple contract** that can be deployed to the TON blockchain, along with examples of implementing unit tests and helper functions for contract deployment.
 
 ## Getting started from template
 
-To get started, you can use the template project. It contains a simple contract that can be deployed to the TON blockchain, example of implementing unit tests and helper functions for contract deployment.
+To get started, you can use the template project. It contains a simple contract that can be deployed to the TON blockchain, as well as examples of implementing unit tests and helper functions for contract deployment.
 
-To create a project from template, just create a new repository from the template project: https://github.com/tact-lang/tact-template.
+> To create a project from the template, simply create a new repository from the template project: https://github.com/tact-lang/tact-template.
 
 ## Getting started from scratch
 
-Tact is distributed via `npm` package manager and is meant to be installed to typescript/javascript projects:
+Tact is distributed via `npm` package manager and is meant to be installed to TypeScript/JavaScript projects:
 
 ```bash
 yarn add @tact-lang/compiler
@@ -20,11 +22,13 @@ Then you need to create a `tact.config.json` file in the root of your project. I
 
 ```json
 {
-    "projects": [{
-        "name": "sample",
-        "path": "./sources/contract.tact",
-        "output": "./sources/output"
-    }]
+  "projects": [
+    {
+      "name": "sample",
+      "path": "./sources/contract.tact",
+      "output": "./sources/output"
+    }
+  ]
 }
 ```
 
@@ -48,11 +52,11 @@ contract SampleTactContract with Deployable {
     }
 
     fun add(v: Int) {
-        
+
         // Check sender
         let ctx: Context = context();
         require(ctx.sender == self.owner, "Invalid sender");
-        
+
         // Update counter
         self.counter = (self.counter + v);
     }
@@ -75,11 +79,10 @@ Add a build script to `package.json`:
 
 ```json
 {
-    "scripts": {
-        "build": "tact --config ./tact.config.json",
-    }
+  "scripts": {
+    "build": "tact --config ./tact.config.json"
+  }
 }
 ```
 
 Now you can run `yarn build` and get the compiled contract in `./sources/output` folder.
-

public/banner.jpeg

@@ -56,8 +56,17 @@ export default {
         content="Language reference and guides for Tact"
       />
 
-      <meta name="twitter:card" content="summary_large_image" />
-      <meta name="twitter:site" content="@tact_language"></meta>
+      <meta 
+        name="twitter:card" 
+        content="summary_large_image" 
+      />
+      
+      <meta 
+        name="twitter:site" 
+        content="@tact_language
+      ">
+        
+      </meta>
 
       <meta name="apple-mobile-web-app-title" content="Tact" />