graphprotocol
diff --git a/‎.nvmrc
Lines changed: 1 addition & 1 deletion b/‎.nvmrc
Lines changed: 1 addition & 1 deletion
diff --git a/‎website/pages/ar/about.mdx
Lines changed: 1 addition & 1 deletion b/‎website/pages/ar/about.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎website/pages/ar/arbitrum-faq.mdx
Lines changed: 3 additions & 3 deletions b/‎website/pages/ar/arbitrum-faq.mdx
Lines changed: 3 additions & 3 deletions
diff --git a/‎website/pages/ar/cookbook/arweave.mdx
Lines changed: 2 additions & 2 deletions b/‎website/pages/ar/cookbook/arweave.mdx
Lines changed: 2 additions & 2 deletions
diff --git a/‎website/pages/ar/cookbook/base-testnet.mdx
Lines changed: 1 addition & 1 deletion b/‎website/pages/ar/cookbook/base-testnet.mdx
Lines changed: 1 addition & 1 deletion
diff --git a/‎website/pages/ar/cookbook/cosmos.mdx
Lines changed: 6 additions & 6 deletions b/‎website/pages/ar/cookbook/cosmos.mdx
Lines changed: 6 additions & 6 deletions
diff --git a/‎website/pages/ar/cookbook/grafting.mdx
Lines changed: 5 additions & 5 deletions b/‎website/pages/ar/cookbook/grafting.mdx
Lines changed: 5 additions & 5 deletions
@@ -1 +1 @@
-18.15
+18
@@ -28,7 +28,7 @@ The Graph يفهرس بيانات الإيثيريوم بناء على أوصا
 
 بمجرد كتابة `subgraph manifest` ، يمكنك استخدام Graph CLI لتخزين التعريف في IPFS وإخبار المفهرس ببدء فهرسة البيانات لذلك الـ subgraph.
 
-يقدم هذا الرسم البياني مزيدًا من التفاصيل حول تدفق البيانات عند نشر الـsubgraph manifest ، والتعامل مع إجراءات الـ Ethereum:
+This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
 
 ![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png)
 
 
@@ -31,15 +31,15 @@ Users bridge their GRT and ETH  using one of the following methods:
 
 To take advantage of using The Graph on L2, use this dropdown switcher to toggle between chains.
 
-{/* Insert an image */} ![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png)
+![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png)
 
 ### As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
 There is no immediate action required.
 
-Core developer teams are working to create migration helpers that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect migration helpers to be available in April 2023.
+Core developer teams are working to create migration helpers that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect migration helpers to be available soon.
 
-The Graph community can also expect indexing rewards to be enabled on Arbitrum in February or March 2023.
+As of April 10th, 2023, 5% of all indexing rewards are being minted on Arbitrum. As network participation increases, and as the Council approves it, indexing rewards will gradually shift from Ethereum to Arbitrum, eventually moving entirely to Arbitrum.
 
 ### If I would like to participate in the network on L2, what should I do?
 
 
@@ -46,7 +46,7 @@ The requirements for Arweave subgraphs are covered by the [existing documentatio
 
 This is the logic that determines how data should be retrieved and stored when someone interacts with the data sources you are listening to. The data gets translated and is stored based off the schema you have listed.
 
-أثناء تطوير الـ الرسم البياني الفرعي هناك أمران رئيسان:
+أثناء تطوير الـ subgraph ، هناك أمران رئيسيان:
 
 ```
 $ graph codegen # generates types from the schema file identified in the manifest
@@ -162,7 +162,7 @@ graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph
 
 The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information.
 
-## مثال الفرعية رسم بياني
+## أمثلة على الـ Subgraphs
 
 Here is an example subgraph for reference:
 
 
@@ -11,7 +11,7 @@ What you'll need:
 
 ## Subgraph Studio
 
-### 1. قم بتثبيت رسم بياني CLI
+### 1. Install the Graph CLI
 
 The Graph CLI (>=v0.41.0) is written in JavaScript and you will need to have either `npm` or `yarn` installed to use it.
 
 
@@ -43,7 +43,7 @@ There are three key parts when it comes to defining a subgraph:
 
 **AssemblyScript Mappings**: [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) code that translates from blockchain data to the entities defined in your schema.
 
-### تعريف الفرعية رسم بياني يظهر
+### تعريف Subgraph Manifest
 
 The subgraph manifest (`subgraph.yaml`) identifies the data sources for the subgraph, the triggers of interest, and the functions (`handlers`) that should be run in response to those triggers. See below for an example subgraph manifest for a Cosmos subgraph:
 
@@ -81,9 +81,9 @@ dataSources:
 
 Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graph-ql-schema).
 
-### أسيمبلي سكريبت التعيينات
+### AssemblyScript Mappings
 
-تمت كتابة المعالجات الخاصة بمعالجة الأحداث بـ[ أسيمبلي سكريبت ](https://www.assemblyscript.org/).
+تمت كتابة المعالجات(handlers) الخاصة بمعالجة الأحداث بـ[ AssemblyScript ](https://www.assemblyscript.org/).
 
 Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/assemblyscript-api/).
 
@@ -208,7 +208,7 @@ graph create account/subgraph-name --product hosted-service
 graph deploy account/subgraph-name --product hosted-service
 ```
 
-**رسم بياني العقدة المحلية (على أساس التكوين الافتراضي):**
+**Graph Node المحلية (على أساس التكوين الافتراضي):**
 
 ```bash
 graph create subgraph-name --node http://localhost:8020
@@ -246,9 +246,9 @@ Cosmos Hub mainnet is `cosmoshub-4`. Cosmos Hub current testnet is `theta-testne
 
 Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`.
 
-## مثال الفرعية رسم بياني
+## أمثلة على الـ Subgraphs
 
-فيما يلي بعض مثال الفرعية رسم بياني للرجوع إليها:
+فيما يلي بعض الأمثلة على الـ subgraphs للرجوع إليها:
 
 [Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)
 
 
@@ -12,15 +12,15 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o
 
 - يضيف أو يزيل أنواع الكيانات
 - يزيل الصفات من أنواع الكيانات
-- يضيف صفات لاغية لأنواع الكيانات
-- يحول صفات غير لاغية إلى صفات لاغية
-- يضيف قيما إلى تعداد
+- يضيف صفات nullable لأنواع الكيانات
+- يحول صفات non-nullable إلى صفات nullable
+- يضيف قيما إلى enums
 - يضيف أو يزيل الواجهات
 - يغير للكيانات التي يتم تنفيذ الواجهة لها
 
 For more information, you can check:
 
-- [گرافتنگ](https://thegraph.com/docs/en/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
+- [تطعيم(Grafting)](https://thegraph.com/docs/en/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
 In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
@@ -32,7 +32,7 @@ Building subgraphs is an essential part of The Graph, described more in depth [h
 
 > Note: The contract used in the subgraph was taken from the following [Hackathon Starterkit](https://github.com/schmidsi/hackathon-starterkit).
 
-## تعريف الفرعية رسم بياني يظهر
+## تعريف Subgraph Manifest
 
 The subgraph manifest `subgraph.yaml` identifies the data sources for the subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example subgraph manifest that you will use: