New Crowdin updates (#837)

* New translations l2-transfer-tools-guide.mdx (Swahili)

* New translations substreams-powered-subgraphs.mdx (Japanese)

* New translations substreams-powered-subgraphs.mdx (Swahili)

* New translations substreams-powered-subgraphs-faq.mdx (French)

* New translations substreams-powered-subgraphs-faq.mdx (Portuguese)

* New translations substreams-powered-subgraphs-faq.mdx (Urdu (Pakistan))

* New translations substreams-powered-subgraphs-faq.mdx (Hindi)

* New translations substreams-powered-subgraphs-faq.mdx (Swahili)

* New translations new-chain-integration.mdx (Romanian)

* New translations new-chain-integration.mdx (French)

* New translations new-chain-integration.mdx (Spanish)

* New translations new-chain-integration.mdx (Arabic)

* New translations new-chain-integration.mdx (Czech)

* New translations new-chain-integration.mdx (German)

* New translations new-chain-integration.mdx (Italian)

* New translations new-chain-integration.mdx (Japanese)

* New translations new-chain-integration.mdx (Korean)

* New translations new-chain-integration.mdx (Dutch)

* New translations new-chain-integration.mdx (Polish)

* New translations new-chain-integration.mdx (Portuguese)

* New translations new-chain-integration.mdx (Russian)

* New translations new-chain-integration.mdx (Swedish)

* New translations new-chain-integration.mdx (Turkish)

* New translations new-chain-integration.mdx (Ukrainian)

* New translations new-chain-integration.mdx (Chinese Simplified)

* New translations new-chain-integration.mdx (Urdu (Pakistan))

* New translations new-chain-integration.mdx (Vietnamese)

* New translations new-chain-integration.mdx (Marathi)

* New translations new-chain-integration.mdx (Hindi)

* New translations new-chain-integration.mdx (Swahili)

* New translations chain-integration-overview.mdx (Romanian)

* New translations chain-integration-overview.mdx (French)

* New translations chain-integration-overview.mdx (Spanish)

* New translations chain-integration-overview.mdx (Arabic)

* New translations chain-integration-overview.mdx (Czech)

* New translations chain-integration-overview.mdx (German)

* New translations chain-integration-overview.mdx (Italian)

* New translations chain-integration-overview.mdx (Japanese)

* New translations chain-integration-overview.mdx (Korean)

* New translations chain-integration-overview.mdx (Dutch)

* New translations chain-integration-overview.mdx (Polish)

* New translations chain-integration-overview.mdx (Portuguese)

* New translations chain-integration-overview.mdx (Russian)

* New translations chain-integration-overview.mdx (Swedish)

* New translations chain-integration-overview.mdx (Turkish)

* New translations chain-integration-overview.mdx (Ukrainian)

* New translations chain-integration-overview.mdx (Chinese Simplified)

* New translations chain-integration-overview.mdx (Urdu (Pakistan))

* New translations chain-integration-overview.mdx (Vietnamese)

* New translations chain-integration-overview.mdx (Marathi)

* New translations chain-integration-overview.mdx (Hindi)

* New translations chain-integration-overview.mdx (Swahili)

* New translations sunrise.mdx (Romanian)

* New translations sunrise.mdx (French)

* New translations sunrise.mdx (Spanish)

* New translations sunrise.mdx (Arabic)

* New translations sunrise.mdx (Czech)

* New translations sunrise.mdx (German)

* New translations sunrise.mdx (Italian)

* New translations sunrise.mdx (Japanese)

* New translations sunrise.mdx (Korean)

* New translations sunrise.mdx (Dutch)

* New translations sunrise.mdx (Polish)

* New translations sunrise.mdx (Portuguese)

* New translations sunrise.mdx (Russian)

* New translations sunrise.mdx (Swedish)

* New translations sunrise.mdx (Turkish)

* New translations sunrise.mdx (Ukrainian)

* New translations sunrise.mdx (Chinese Simplified)

* New translations sunrise.mdx (Urdu (Pakistan))

* New translations sunrise.mdx (Vietnamese)

* New translations sunrise.mdx (Marathi)

* New translations sunrise.mdx (Hindi)

* New translations sunrise.mdx (Swahili)

* New translations querying-with-python.mdx (Swahili)

* New translations common-issues.mdx (French)

* New translations common-issues.mdx (Swahili)

* New translations supported-networks.json (French)

* New translations supported-networks.json (Russian)

* New translations supported-networks.json (Urdu (Pakistan))

* New translations supported-networks.json (Swahili)

* New translations querying-by-subgraph-id-vs-deployment-id.mdx (Swahili)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Czech)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Portuguese)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Turkish)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Ukrainian)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Marathi)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Hindi)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Swahili)

* New translations contracts.mdx (Russian)

* New translations contracts.mdx (Swahili)

* New translations supported-network-requirements.mdx (Romanian)

* New translations supported-network-requirements.mdx (French)

* New translations supported-network-requirements.mdx (Spanish)

* New translations supported-network-requirements.mdx (Arabic)

* New translations supported-network-requirements.mdx (Czech)

* New translations supported-network-requirements.mdx (German)

* New translations supported-network-requirements.mdx (Italian)

* New translations supported-network-requirements.mdx (Japanese)

* New translations supported-network-requirements.mdx (Korean)

* New translations supported-network-requirements.mdx (Dutch)

* New translations supported-network-requirements.mdx (Polish)

* New translations supported-network-requirements.mdx (Portuguese)

* New translations supported-network-requirements.mdx (Russian)

* New translations supported-network-requirements.mdx (Swedish)

* New translations supported-network-requirements.mdx (Turkish)

* New translations supported-network-requirements.mdx (Ukrainian)

* New translations supported-network-requirements.mdx (Chinese Simplified)

* New translations supported-network-requirements.mdx (Urdu (Pakistan))

* New translations supported-network-requirements.mdx (Vietnamese)

* New translations supported-network-requirements.mdx (Marathi)

* New translations supported-network-requirements.mdx (Hindi)

* New translations supported-network-requirements.mdx (Swahili)

* New translations tap.mdx (Romanian)

* New translations tap.mdx (French)

* New translations tap.mdx (Spanish)

* New translations tap.mdx (Arabic)

* New translations tap.mdx (Czech)

* New translations tap.mdx (German)

* New translations tap.mdx (Italian)

* New translations tap.mdx (Japanese)

* New translations tap.mdx (Korean)

* New translations tap.mdx (Dutch)

* New translations tap.mdx (Polish)

* New translations tap.mdx (Portuguese)

* New translations tap.mdx (Russian)

* New translations tap.mdx (Swedish)

* New translations tap.mdx (Turkish)

* New translations tap.mdx (Ukrainian)

* New translations tap.mdx (Chinese Simplified)

* New translations tap.mdx (Urdu (Pakistan))

* New translations tap.mdx (Vietnamese)

* New translations tap.mdx (Marathi)

* New translations tap.mdx (Swahili)

* New translations introduction.mdx (Romanian)

* New translations introduction.mdx (French)

* New translations introduction.mdx (Spanish)

* New translations introduction.mdx (Arabic)

* New translations introduction.mdx (Czech)

* New translations introduction.mdx (German)

* New translations introduction.mdx (Italian)

* New translations introduction.mdx (Japanese)

* New translations introduction.mdx (Korean)

* New translations introduction.mdx (Dutch)

* New translations introduction.mdx (Polish)

* New translations introduction.mdx (Portuguese)

* New translations introduction.mdx (Russian)

* New translations introduction.mdx (Swedish)

* New translations introduction.mdx (Turkish)

* New translations introduction.mdx (Ukrainian)

* New translations introduction.mdx (Chinese Simplified)

* New translations introduction.mdx (Urdu (Pakistan))

* New translations introduction.mdx (Vietnamese)

* New translations introduction.mdx (Marathi)

* New translations introduction.mdx (Swahili)

* New translations triggers-example.mdx (Romanian)

* New translations triggers-example.mdx (Spanish)

* New translations triggers-example.mdx (Arabic)

* New translations triggers-example.mdx (Czech)

* New translations triggers-example.mdx (German)

* New translations triggers-example.mdx (Italian)

* New translations triggers-example.mdx (Japanese)

* New translations triggers-example.mdx (Korean)

* New translations triggers-example.mdx (Dutch)

* New translations triggers-example.mdx (Polish)

* New translations triggers-example.mdx (Portuguese)

* New translations triggers-example.mdx (Swedish)

* New translations triggers-example.mdx (Turkish)

* New translations triggers-example.mdx (Ukrainian)

* New translations triggers-example.mdx (Chinese Simplified)

* New translations triggers-example.mdx (Urdu (Pakistan))

* New translations triggers-example.mdx (Vietnamese)

* New translations triggers-example.mdx (Marathi)

* New translations triggers-example.mdx (Swahili)

* New translations triggers.mdx (Swahili)

* New translations multiple-networks.mdx (French)

* New translations multiple-networks.mdx (Spanish)

* New translations multiple-networks.mdx (Czech)

* New translations multiple-networks.mdx (Italian)

* New translations multiple-networks.mdx (Japanese)

* New translations multiple-networks.mdx (Portuguese)

* New translations multiple-networks.mdx (Russian)

* New translations multiple-networks.mdx (Swedish)

* New translations multiple-networks.mdx (Chinese Simplified)

* New translations multiple-networks.mdx (Urdu (Pakistan))

* New translations multiple-networks.mdx (Marathi)

* New translations multiple-networks.mdx (Swahili)

* New translations transfer-a-subgraph.mdx (Romanian)

* New translations transfer-a-subgraph.mdx (French)

* New translations transfer-a-subgraph.mdx (Spanish)

* New translations transfer-a-subgraph.mdx (Arabic)

* New translations transfer-a-subgraph.mdx (Czech)

* New translations transfer-a-subgraph.mdx (German)

* New translations transfer-a-subgraph.mdx (Italian)

* New translations transfer-a-subgraph.mdx (Japanese)

* New translations transfer-a-subgraph.mdx (Korean)

* New translations transfer-a-subgraph.mdx (Dutch)

* New translations transfer-a-subgraph.mdx (Polish)

* New translations transfer-a-subgraph.mdx (Portuguese)

* New translations transfer-a-subgraph.mdx (Russian)

* New translations transfer-a-subgraph.mdx (Swedish)

* New translations transfer-a-subgraph.mdx (Ukrainian)

* New translations transfer-a-subgraph.mdx (Chinese Simplified)

* New translations transfer-a-subgraph.mdx (Urdu (Pakistan))

* New translations transfer-a-subgraph.mdx (Vietnamese)

* New translations transfer-a-subgraph.mdx (Marathi)

* New translations transfer-a-subgraph.mdx (Swahili)

* New translations deploy-using-subgraph-studio.mdx (Romanian)

* New translations deploy-using-subgraph-studio.mdx (French)

* New translations deploy-using-subgraph-studio.mdx (Spanish)

* New translations deploy-using-subgraph-studio.mdx (Arabic)

* New translations deploy-using-subgraph-studio.mdx (Czech)

* New translations deploy-using-subgraph-studio.mdx (German)

* New translations deploy-using-subgraph-studio.mdx (Italian)

* New translations deploy-using-subgraph-studio.mdx (Japanese)

* New translations deploy-using-subgraph-studio.mdx (Korean)

* New translations deploy-using-subgraph-studio.mdx (Dutch)

* New translations deploy-using-subgraph-studio.mdx (Polish)

* New translations deploy-using-subgraph-studio.mdx (Portuguese)

* New translations deploy-using-subgraph-studio.mdx (Russian)

* New translations deploy-using-subgraph-studio.mdx (Swedish)

* New translations deploy-using-subgraph-studio.mdx (Ukrainian)

* New translations deploy-using-subgraph-studio.mdx (Chinese Simplified)

* New translations deploy-using-subgraph-studio.mdx (Urdu (Pakistan))

* New translations deploy-using-subgraph-studio.mdx (Vietnamese)

* New translations deploy-using-subgraph-studio.mdx (Marathi)

* New translations deploy-using-subgraph-studio.mdx (Swahili)

* New translations enums.mdx (Spanish)

* New translations enums.mdx (Arabic)

* New translations enums.mdx (Czech)

* New translations enums.mdx (German)

* New translations enums.mdx (Japanese)

* New translations enums.mdx (Portuguese)

* New translations enums.mdx (Swedish)

* New translations enums.mdx (Turkish)

* New translations enums.mdx (Chinese Simplified)

* New translations enums.mdx (Urdu (Pakistan))

* New translations enums.mdx (Swahili)

* New translations tap.mdx (Hindi)

* New translations api.mdx (Czech)

* New translations deploy-using-subgraph-studio.mdx (Hindi)

* New translations avoid-eth-calls.mdx (Hindi)

* New translations pruning.mdx (Hindi)

* New translations assemblyscript-migration-guide.mdx (Russian)

* New translations billing.mdx (German)

* New translations graphql-validations-migration-guide.mdx (Chinese Simplified)

* New translations how-to-secure-api-keys-using-nextjs-server-components.mdx (Hindi)

* New translations multiple-networks.mdx (Hindi)

* New translations supported-networks.mdx (French)

* Run `pnpm check:fix`

website/pages/ar/about.mdx

@@ -2,46 +2,66 @@
 title: حول The Graph
 ---
 
-هذه الصفحة ستشرح The Graph وكيف يمكنك أن تبدأ.
-
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+The Graph is a powerful decentralized protocol that enables seamless querying and indexing of blockchain data. It simplifies the complex process of querying blockchain data, making dapp development faster and easier.
+
+## Understanding the Basics
+
+Projects with complex smart contracts such as [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it very difficult to read anything other than basic data directly from the blockchain.
+
+### Challenges Without The Graph
+
+In the case of the example listed above, Bored Ape Yacht Club, you can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). You can read the owner of a certain Ape, read the content URI of an Ape based on their ID, or read the total supply.
+
+- This can be done because these read operations are programmed directly into the smart contract itself. However, more advanced, specific, and real-world queries and operations like aggregation, search, relationships, and non-trivial filtering, **are not possible**.
+
+- For instance, if you want to inquire about Apes owned by a specific address and refine your search based on a particular characteristic, you would not be able to obtain that information by directly interacting with the contract itself.
+
+- To get more data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data.
 
-المشاريع ذات العقود الذكية المعقدة مثل [ Uniswap ](https://uniswap.org/) و NFTs مثل [ Bored Ape Yacht Club ](https://boredapeyachtclub.com/) تقوم بتخزين البيانات على Ethereum blockchain ، مما يجعل من الصعب قراءة أي شيء بشكل مباشر عدا البيانات الأساسية من blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+The Graph solves this challenge with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "subgraphs") can then be queried with a standard GraphQL API.
 
-To get this data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+Today, there is a decentralized protocol that is backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node) that enables this process.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+### How The Graph Functions
 
-**إن فهرسة بيانات الـ blockchain أمر صعب.**
+Indexing blockchain data is very difficult, but The Graph makes it easy. The Graph learns how to index Ethereum data by using subgraphs. Subgraphs are custom APIs built on blockchain data that extract data from a blockchain, processes it, and stores it so that it can be seamlessly queried via GraphQL.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution with a decentralized protocol that indexes and enables the efficient and high-performance querying of blockchain data. These APIs (indexed "subgraphs") can then be queried with a standard GraphQL API. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## كيف يعمل The Graph
+- The subgraph description outlines the smart contracts of interest for a subgraph, the events within those contracts to focus on, and how to map event data to the data that The Graph will store in its database.
 
-The Graph يفهرس بيانات الإيثيريوم بناء على أوصاف الـ subgraph ، والمعروفة باسم subgraph manifest. حيث أن وصف الـ subgraph يحدد العقود الذكية ذات الأهمية لـ subgraph ، ويحدد الأحداث في تلك العقود التي يجب الانتباه إليها ، وكيفية عمل map لبيانات الحدث إلى البيانات التي سيخزنها The Graph في قاعدة البيانات الخاصة به.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-بمجرد كتابة `subgraph manifest` ، يمكنك استخدام Graph CLI لتخزين التعريف في IPFS وإخبار المفهرس ببدء فهرسة البيانات لذلك الـ subgraph.
+- After writing the `subgraph manifest`, you can use the Graph CLI to store the definition in IPFS and instruct an Indexer to start indexing data for that subgraph.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+The diagram below provides more detailed information about the flow of data after a subgraph manifest has been deployed with Ethereum transactions.
 
 ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png)
 
 تدفق البيانات يتبع الخطوات التالية:
 
-1. A dapp adds data to Ethereum through a transaction on a smart contract.
-2. العقد الذكي يصدر حدثا واحدا أو أكثر أثناء معالجة الإجراء.
-3. يقوم الـ Graph Node بمسح الـ Ethereum باستمرار بحثا عن الكتل الجديدة وبيانات الـ subgraph الخاص بك.
-4. يعثر الـ Graph Node على أحداث الـ Ethereum لـ subgraph الخاص بك في هذه الكتل ويقوم بتشغيل mapping handlers التي قدمتها. الـ mapping عبارة عن وحدة WASM والتي تقوم بإنشاء أو تحديث البيانات التي يخزنها Graph Node استجابة لأحداث الـ Ethereum.
-5. The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats.
+1.  A dapp adds data to Ethereum through a transaction on a smart contract.
+2.  العقد الذكي يصدر حدثا واحدا أو أكثر أثناء معالجة الإجراء.
+3.  يقوم الـ Graph Node بمسح الـ Ethereum باستمرار بحثا عن الكتل الجديدة وبيانات الـ subgraph الخاص بك.
+4.  يعثر الـ Graph Node على أحداث الـ Ethereum لـ subgraph الخاص بك في هذه الكتل ويقوم بتشغيل mapping handlers التي قدمتها. الـ mapping عبارة عن وحدة WASM والتي تقوم بإنشاء أو تحديث البيانات التي يخزنها Graph Node استجابة لأحداث الـ Ethereum.
+5.  The dapp queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The dapp displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats.
 
 ## الخطوات التالية
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+Before you write your own subgraph, it's recommended to explore [Graph Explorer](https://thegraph.com/explorer) and review some of the already deployed subgraphs. Each subgraph's page includes a GraphQL playground, allowing you to query its data.

website/pages/ar/arbitrum/arbitrum-faq.mdx

@@ -4,17 +4,17 @@ title: الأسئلة الشائعة حول Arbitrum
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## لماذا يقوم The Graph بتطبيق حل L2؟
+## Why did The Graph implement an L2 Solution?
 
-By scaling The Graph on L2, network participants can expect:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
 - سرعة أكبر في المعاملات
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
 
 ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-اعتبارًا من 10 أبريل 2023 ، تم سك 5٪ من جميع مكافآت الفهرسة على Arbitrum. مع زيادة المشاركة في الشبكة ، وموافقة المجلس عليها ، ستتحول مكافآت الفهرسة تدريجياً من Ethereum إلى Arbitrum ، وستنتقل في النهاية بالكامل إلى Arbitrum.
-
-## إذا كنت أرغب في المشاركة في اشبكة L2 ، فماذا أفعل؟
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## هل توجد أي مخاطر مرتبطة بتوسيع الشبكة إلى L2؟
+## Were there any risks associated with scaling the network to L2?
 
 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).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## هل ستستمر ال subgraphs الموجودة على Ethereum في العمل؟
+## Are existing subgraphs on Ethereum working?
 
-نعم ، ستعمل عقود شبكة The Graph بالتوازي على كل من Ethereum و Arbitrum حتى الانتقال بشكل كامل إلى Arbitrum في وقت لاحق.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## هل سيكون لدى GRT عقد ذكي جديد يتم نشره على Arbitrum؟
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx

@@ -46,7 +46,7 @@ If you have the L1 transaction hash (which you can find by looking at the recent
 
 2. انتظر 20 دقيقة للتأكيد
 
-3. قم بتأكيد نقل الـ subgraph على Arbitrum \\ \*
+3. قم بتأكيد نقل الـ subgraph على Arbitrum \ \*
 
 4. قم بإنهاء نشر الـ subgraph على Arbitrum
 
@@ -200,11 +200,11 @@ The tokens that are being undelegated are "locked" and therefore cannot be trans
 
 1. ابدأ نقل الإشارة على شبكة Ethereum mainnet
 
-2. حدد عنوان L2 للمنسق \\ \*
+2. حدد عنوان L2 للمنسق \ \*
 
 3. انتظر 20 دقيقة للتأكيد
 
-\\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
+\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
 
 ### كيف سأعرف ما إذا كان الرسم البياني الفرعي الذي قمت بعمل إشارة تنسيق عليه قد انتقل إلى L2؟
 
@@ -250,7 +250,7 @@ The tokens that are being undelegated are "locked" and therefore cannot be trans
 
 ### كم من الوقت لدي لتأكيد تحويل حصتي إلى Arbitrum؟
 
-\\ _ \\ _ \\ \* يجب تأكيد معاملتك لإتمام تحويل الحصة على Arbitrum. يجب إكمال هذه الخطوة في غضون 7 أيام وإلا فقد يتم فقدان الحصة.
+\ _ \ _ \ \* يجب تأكيد معاملتك لإتمام تحويل الحصة على Arbitrum. يجب إكمال هذه الخطوة في غضون 7 أيام وإلا فقد يتم فقدان الحصة.
 
 ### ماذا لو كان لدي تخصيصات مفتوحة؟
 
@@ -366,13 +366,13 @@ Yes! The process is a bit different, because vesting contracts can't forward the
 
 3. امنح البروتوكول حق الوصول إلى عقد الاستحقاق (سيسمح لعقدك بالتفاعل مع أداة التحويل)
 
-4. حدد عنوان المستفيد على L2 \\ \* وابدأ في تحويل الرصيد على Ethereum mainnet
+4. حدد عنوان المستفيد على L2 \ \* وابدأ في تحويل الرصيد على Ethereum mainnet
 
 5. انتظر 20 دقيقة للتأكيد
 
 6. قم بتأكيد تحويل الرصيد على L2
 
-\\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
+\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
 
 \*\*\*\*You must confirm your transaction to complete the balance transfer on Arbitrum. This step must be completed within 7 days or the balance could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).