some correction

docs/00-scd/14-async-communication/async-communications.md

@@ -5,9 +5,9 @@ slug: /async-communication/async-communications
 hide_table_of_contents: true
 ---
 
-This lesson focuses on the Actor model for message-passing communications, a key and distinguishing feature of the Gear Protocol.
+This lesson focuses on the Actor model for message-passing communications, a key and distinguishing feature of the Vara network.
 
-One of the key and distinguished features of the Gear Protocol is the Actor model for message-passing communications. Gear Protocol leverages the Actor model for message-passing communication, allowing parallel computation and asynchronous messaging to ensure faster processing times. The development structure provides developers with immense flexibility when building complex dApps.
+One of the key and distinguished features of the Vara network is the Actor model for message-passing communications. Vara network leverages the Actor model for message-passing communication, allowing parallel computation and asynchronous messaging to ensure faster processing times. The development structure provides developers with immense flexibility when building complex dApps.
 
 If a program sends an asynchronous message to another program, it needs to wait for the reply from that program before it can proceed to the next operation.
 

docs/00-scd/14-async-communication/distributed-transactions.md

@@ -5,9 +5,9 @@ slug: /async-communication/distributed-transactions
 hide_table_of_contents: true
 ---
 
-This lesson discusses the interactions between programs in the Gear Protocol, which involve distributed transactions across actors with their respective states.
+This lesson discusses the interactions between programs in the Vara network, which involve distributed transactions across actors with their respective states.
 
-Programs in the Gear Protocol interact and create distributed transactions involving processes across actors and their respective states. In our case, operations occur across actors and their states. The distributed transactions must have the following features:
+Programs in the Vara network interact and create distributed transactions involving processes across actors and their respective states. In our case, operations occur across actors and their states. The distributed transactions must have the following features:
 
 - **Atomicity**: All data changes are treated as a single operation, i.e., all the modifications are made or none.
 - **Consistency**: This property implies the data state is consistent when a transaction begins and ends.

docs/00-scd/16-auction-automation/automation.md

@@ -29,7 +29,7 @@ Once all the necessary logic is complete, the auction contract will send itself
 
 Therefore, by utilizing delayed messages, we can automate the execution of a contract. As long as there is sufficient gas for execution, the contract can self-execute for an unlimited block number. However, if the gas runs out, the execution may be interrupted.
 
-The Gear protocol offers another powerful feature: gas reservation. Developers can reserve gas, which they can later use to send regular or delayed messages.
+The Vara network offers another powerful feature: gas reservation. Developers can reserve gas, which they can later use to send regular or delayed messages.
 
 To reserve a specific amount of gas for future usage, you can use the following function:
 

docs/00-scd/19-auction-signals/system-signals.md

@@ -11,7 +11,7 @@ In Gear programs, there are three common entry points:
 - `handle`
 - `handle_reply`
 
-The Gear Protocol also introduces the `handle_signal` entry point, enabling the system to communicate with programs and notify them (signal) of events related to the program's messages. Only the system (Gear node runtime) can send signal messages to a program.
+The Vara network also introduces the `handle_signal` entry point, enabling the system to communicate with programs and notify them (signal) of events related to the program's messages. Only the system (Gear node runtime) can send signal messages to a program.
 
 The system sends messages to a program in the event of errors during program execution. For example, a program can panic or run out of gas.
 

docs/02-basic/01-introduction/program-state.md

@@ -13,6 +13,6 @@ Program memory is organized in pages of 64KB according to the Wasm memory model.
 
 Programs running in Vara networks don’t use a shared storage but rather their full state is persisted which ensures much less API surface for blockchain context. It avoids domain-specific language features as well as allows using much more complex language constructs — persisted boxed closures, futures compositors, etc.
 
-The Gear Protocol uses clever memory virtualization techniques (despite vanilla Wasm does not), memory allocation and deallocation are first-class syscalls of the protocol. Memory access is also tracked and only required pages are loaded/stored. That allows heap-allocated frames of smart contracts stored in the blockchain’s state (typically found in futures and their compositors) to be seamlessly persisted and invoked when needed, preserving their state upon request.
+The Vara network uses clever memory virtualization techniques (despite vanilla Wasm does not), memory allocation and deallocation are first-class syscalls of the protocol. Memory access is also tracked and only required pages are loaded/stored. That allows heap-allocated frames of smart contracts stored in the blockchain’s state (typically found in futures and their compositors) to be seamlessly persisted and invoked when needed, preserving their state upon request.
 
 Gear instance holds individual memory space per program and guarantees its persistence. A program can read and write only within its own memory space and has no access to the memory space of other programs. Individual memory space is reserved for a program during its initialization and does not require an additional fee (it is included in the program's initialization fee).

docs/02-basic/02-program-basics/message-handling.md

@@ -5,7 +5,7 @@ hide_table_of_contents: true
 
 # Message Handling
 
-The Gear Protocol allows users and programs to interact with other users and programs via messages. Messages can contain a payload that will be able to be processed during message execution. Interaction with messages is possible thanks to the module [`gstd::msg`](https://docs.gear.rs/gstd/msg/index.html):
+The Vara network allows users and programs to interact with other users and programs via messages. Messages can contain a payload that will be able to be processed during message execution. Interaction with messages is possible thanks to the module [`gstd::msg`](https://docs.gear.rs/gstd/msg/index.html):
 
 ```rust
 use gstd::msg;

i18n/zh-cn/docusaurus-plugin-content-docs/current/00-scd/02-substrate-id/key-information.md

@@ -5,7 +5,7 @@ slug: /substrate-id/key-information
 hide_table_of_contents: true
 ---
 
-一个账户代表了一个身份，可以是个人或一个能够进行交易或持有资金的组织。用户可以上传智能合约，并通过区块链网络上的交易与其进行互动，而这些区块链网络是基于 Gear Protocol 构建的。用户需要连接一个 Substrate 账户来实现这一点。Gear Idea 可以与连接的基于 Gear 网络中的 Substrate 账户一起作用。这个账户还可以在任何 DotSama 生态系统的网络中持有资金并进行交易，点击了解[更多](https://docs.substrate.io/fundamentals/accounts-addresses-keys/)。
+一个账户代表了一个身份，可以是个人或一个能够进行交易或持有资金的组织。用户可以上传智能合约，并通过区块链网络上的交易与其进行互动，而这些区块链网络是基于 Vara network 构建的。用户需要连接一个 Substrate 账户来实现这一点。Gear Idea 可以与连接的基于 Gear 网络中的 Substrate 账户一起作用。这个账户还可以在任何 DotSama 生态系统的网络中持有资金并进行交易，点击了解[更多](https://docs.substrate.io/fundamentals/accounts-addresses-keys/)。
 
 - 地址是账户的公共部分。它就像一个你可以与他人分享以发送和接收交易的位置。
 - 密钥是账户的私有部分。它允许你作为账户所有者访问你的地址。只有使用你的私钥（助记词、种子或带有密码的账户 JSON 文件）才能访问你的账户。

i18n/zh-cn/docusaurus-plugin-content-docs/current/00-scd/14-async-communication/async-communications.md

@@ -5,9 +5,9 @@ slug: /async-communication/async-communications
 hide_table_of_contents: true
 ---
 
-本课关注消息传递通信的 Actor 模型，这是 Gear Protocol 的一个关键和独特特性。
+本课关注消息传递通信的 Actor 模型，这是 Vara network 的一个关键和独特特性。
 
-Gear Protocol 的一个关键和独特特性是使用 Actor 模型进行消息传递通信。 Gear Protocol 利用 Actor 模型进行消息传递通信，允许并行计算和异步消息传递，以确保更快的处理时间。这种开发结构为开发人员构建复杂的 dApps 提供了极大的灵活性。
+Vara network 的一个关键和独特特性是使用 Actor 模型进行消息传递通信。 Vara network 利用 Actor 模型进行消息传递通信，允许并行计算和异步消息传递，以确保更快的处理时间。这种开发结构为开发人员构建复杂的 dApps 提供了极大的灵活性。
 
 如果一个程序向另一个程序发送异步消息，它需要等待来自该程序的回复，然后才能继续进行下一项操作。
 

i18n/zh-cn/docusaurus-plugin-content-docs/current/00-scd/14-async-communication/distributed-transactions.md

@@ -5,9 +5,9 @@ slug: /async-communication/distributed-transactions
 hide_table_of_contents: true
 ---
 
-本课讨论了 Gear Protocol 中程序之间的交互，涉及到跨 Actor 及其各自状态的分布式交易。
+本课讨论了 Vara network 中程序之间的交互，涉及到跨 Actor 及其各自状态的分布式交易。
 
-Gear Protocol 中的程序进行交互并创建涉及 Actor 及其各自状态的过程的分布式交易。在我们的案例中，操作发生在 Actor 及其状态之间。这些分布式交易必须具备以下特性：
+Vara network 中的程序进行交互并创建涉及 Actor 及其各自状态的过程的分布式交易。在我们的案例中，操作发生在 Actor 及其状态之间。这些分布式交易必须具备以下特性：
 
 - **原子性**：所有数据更改被视为单个操作，即所有修改要么全部完成，要么都不完成。
 - **一致性**：这一属性意味着交易开始和结束时数据状态是一致的。

i18n/zh-cn/docusaurus-plugin-content-docs/current/00-scd/16-auction-automation/automation.md

@@ -29,7 +29,7 @@ msg::send_bytes_delayed(program, payload, value, delay)
 
 因此，通过利用延迟消息，我们可以自动执行合约。只要有足够的 gas 进行执行，合约就可以自我执行到无限的区块号。但是，如果 gas 用尽，执行可能会中断。
 
-Gear Protocol 提供了另一个强大的功能：gas 预留。开发者可以预留 gas，以供将来发送常规或延迟消息使用。
+Vara network 提供了另一个强大的功能：gas 预留。开发者可以预留 gas，以供将来发送常规或延迟消息使用。
 
 要为将来的使用预留特定数量的 gas，可以使用以下函数：
 

i18n/zh-cn/docusaurus-plugin-content-docs/current/00-scd/19-auction-signals/system-signals.md

@@ -11,7 +11,7 @@ hide_table_of_contents: true
 - `handle`
 - `handle_reply`
 
-Gear Protocol 还引入了 `handle_signal` 入口点，使系统能够与程序进行通信并通知它们与程序消息相关的事件。只有系统（Gear 节点运行时）可以向程序发送信号消息。
+Vara network 还引入了 `handle_signal` 入口点，使系统能够与程序进行通信并通知它们与程序消息相关的事件。只有系统（Gear 节点运行时）可以向程序发送信号消息。
 
 系统在程序执行期间出现错误时向程序发送消息。例如，程序可能会出现紧急情况或 gas 用尽。