Skip to content

Commit 1d538d5

Browse files
committed
New translations arbitrum-faq.mdx (Chinese Simplified)
1 parent 915f0bf commit 1d538d5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

website/src/pages/zh/archived/arbitrum/arbitrum-faq.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Scaling the protocol smart contracts onto L2 allows network participants to inte
1818

1919
去年,Graph社区在[GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) 讨论的结果之后,决定推进Arbitrum。
2020

21-
## 我需要做什么才能在L2上使用Graph
21+
## 我需要做什么才能在L2上使用The Graph
2222

2323
The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
2424

@@ -37,7 +37,7 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
3737

3838
要使用L2上的Graph,请使用此下拉开关在链之间切换。
3939

40-
![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png)
40+
![下拉式切换器,用于切换Arbitrum](/img/arbitrum-screenshot-toggle.png)
4141

4242
## As a Subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
4343

@@ -49,7 +49,7 @@ All indexing rewards are now entirely on Arbitrum.
4949

5050
All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
5151

52-
所有事项已经经过了彻底测试,并制定了应急计划,以确保安全和无缝过渡。详细信息可以在 [这里] (https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20)找到。
52+
所有事项已经经过了彻底测试,并制定了应急计划,以确保安全和无缝过渡。详细信息可以在[这里](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20)找到。
5353

5454
## Are existing Subgraphs on Ethereum working?
5555

0 commit comments

Comments
 (0)