graphprotocol
diff --git a/‎pages/ar/about.mdx‎
Lines changed: 1 addition & 1 deletion b/‎pages/ar/about.mdx‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/ar/network/overview.mdx‎
Lines changed: 1 addition & 1 deletion b/‎pages/ar/network/overview.mdx‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎pages/en/cookbook/subgraph-uncrashable.mdx‎
Lines changed: 7 additions & 8 deletions b/‎pages/en/cookbook/subgraph-uncrashable.mdx‎
Lines changed: 7 additions & 8 deletions
diff --git a/‎pages/en/developing/creating-a-subgraph.mdx‎
Lines changed: 4 additions & 5 deletions b/‎pages/en/developing/creating-a-subgraph.mdx‎
Lines changed: 4 additions & 5 deletions
diff --git a/‎pages/es/about.mdx‎
Lines changed: 6 additions & 6 deletions b/‎pages/es/about.mdx‎
Lines changed: 6 additions & 6 deletions
@@ -1,5 +1,5 @@
 ---
-title: مقدمة
+title: حول The Graph
 ---
 
 هذه الصفحة ستشرح The Graph وكيف يمكنك أن تبدأ.
 
@@ -1,6 +1,6 @@
 ---
 title: نظرة عامة حول الشبكة
-navTitle: Overview
+navTitle: نظره عامة
 ---
 
 شبكة The Graph هو بروتوكول فهرسة لامركزي لتنظيم بيانات الـ blockchain. التطبيقات تستخدم GraphQL للاستعلام عن APIs المفتوحة والتي تسمى subgraphs ، لجلب البيانات المفهرسة على الشبكة. باستخدام The Graph ، يمكن للمطورين إنشاء تطبيقات بدون خادم تعمل بالكامل على البنية الأساسية العامة.
 
@@ -4,27 +4,26 @@ title: Safe Subgraph Code Generator
 
 [Subgraph Uncrashable](https://float-capital.github.io/float-subgraph-uncrashable/) is a code generation tool that generates a set of helper functions from the graphql schema of a project. It ensures that all interactions with entities in your subgraph are completely safe and consistent.
 
-
 ### Why integrate with Subgraph Uncrashable?
 
-  - **Continuous Uptime**. Mishandled entities may cause subgraphs to crash, which can be disruptive for projects that are dependent on The Graph. Set up helper functions to make your subgraphs “uncrashable” and ensure business continuity.
+- **Continuous Uptime**. Mishandled entities may cause subgraphs to crash, which can be disruptive for projects that are dependent on The Graph. Set up helper functions to make your subgraphs “uncrashable” and ensure business continuity.
 
-  - **Completely Safe**. Common problems seen in subgraph development are issues of loading undefined entities, not setting or initializing all values of entities, and race conditions on loading and saving entities. Ensure all interactions with entities are completely atomic.
+- **Completely Safe**. Common problems seen in subgraph development are issues of loading undefined entities, not setting or initializing all values of entities, and race conditions on loading and saving entities. Ensure all interactions with entities are completely atomic.
 
-  - **User Configurable** Set default values and configure the level of security checks that suits your individual project's needs. Warning logs are recorded indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
+- **User Configurable** Set default values and configure the level of security checks that suits your individual project's needs. Warning logs are recorded indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 **Key Features**
 
-  - The code generation tool accommodates **all** subgraph types and is configurable for users to set sane defaults on values. The code generation will use this config to generate helper functions that are to the users specification.
+- The code generation tool accommodates **all** subgraph types and is configurable for users to set sane defaults on values. The code generation will use this config to generate helper functions that are to the users specification.
 
-  - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
+- The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-  - Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 
 ```sh
 graph codegen -u [options] [<subgraph-manifest>]
 ```
 
-Visit the [subgraph uncrashable documentation](https://float-capital.github.io/float-subgraph-uncrashable/docs/) or watch this [video tutorial](https://float-capital.github.io/float-subgraph-uncrashable/docs/tutorial) to learn more and to get started with developing safer subgraphs. 
+Visit the [subgraph uncrashable documentation](https://float-capital.github.io/float-subgraph-uncrashable/docs/) or watch this [video tutorial](https://float-capital.github.io/float-subgraph-uncrashable/docs/tutorial) to learn more and to get started with developing safer subgraphs.
@@ -562,7 +562,6 @@ import { Gravatar } from '../generated/schema'
 
 Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to the Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.
 
-
 ## Data Source Templates
 
 A common pattern in Ethereum smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events. The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
@@ -1067,10 +1066,10 @@ Example handler:
 
 ```typescript
 import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
-import { TokenMetadata } from "../generated/schema"
+import { TokenMetadata } from '../generated/schema'
 
 export function handleMetadata(content: Bytes): void {
-  let tokenMetadata = new TokenMetadata(dataSource.stringParam());
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
   const value = json.fromBytes(content).toObject()
   if (value) {
     const image = value.get('image')
@@ -1104,7 +1103,7 @@ Example:
 ```typescript
 import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
 
-const ipfshash = "QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm"
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
 //This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
 
 export function handleTransfer(event: TransferEvent): void {
@@ -1116,7 +1115,7 @@ export function handleTransfer(event: TransferEvent): void {
     token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
     const tokenIpfsHash = ipfshash + token.tokenURI
     //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
-    
+
     token.ipfsURI = tokenIpfsHash
 
     TokenMetadataTemplate.create(tokenIpfsHash)
 
@@ -1,5 +1,5 @@
 ---
-title: Introducción
+title: Acerca de The Graph
 ---
 
 En esta página se explica qué es The Graph y cómo puedes empezar a utilizarlo.
@@ -28,20 +28,20 @@ The Graph aprende, qué y cómo indexar los datos de Ethereum, basándose en las
 
 Una vez que has escrito el `subgraph manifest`, utilizas el CLI de The Graph para almacenar la definición en IPFS y decirle al indexador que empiece a indexar los datos de ese subgrafo.
 
-Este diagrama ofrece más detalles sobre el flujo de datos una vez que se ha desplegado en el manifiesto para un subgrafo, que trata de las transacciones en Ethereum:
+Este diagrama ofrece más detalles sobre el flujo de datos una vez que se ha deployado en el manifiesto para un subgrafo, que trata de las transacciones en Ethereum:
 
 ![](/img/graph-dataflow.png)
 
 El flujo sigue estos pasos:
 
 1. Una aplicación descentralizada añade datos a Ethereum a través de una transacción en un contrato inteligente.
 2. El contrato inteligente emite uno o más eventos mientras procesa la transacción.
-3. Graph Node escanea continuamente la red de Ethereum en busca de nuevos bloques y los datos de su subgrafo que puedan contener.
+3. Graph Node escanea continuamente la red de Ethereum en busca de nuevos bloques y los datos de tu subgrafo que puedan contener.
 4. Graph Node encuentra los eventos de la red Ethereum, a fin de proveerlos en tu subgrafo mediante estos bloques y ejecuta los mapping handlers que proporcionaste. El mapeo (mapping) es un módulo WASM que crea o actualiza las entidades de datos que Graph Node almacena en respuesta a los eventos de Ethereum.
-5. La aplicación descentralizada consulta a través de Graph Node los datos indexados de la blockchain, utilizando el [GraphQL endpoint](https://graphql.org/learn/) del nodo. El Nodo de The Graph, a su vez, traduce las consultas GraphQL en consultas para su almacenamiento de datos subyacentes con el fin de obtener estos datos, haciendo uso de las capacidades de indexación que ofrece el almacenamiento. La aplicación descentralizada muestra estos datos en una interfaz muy completa para el usuario, a fin de que los cliente que usan este subgrafo puedan emitir nuevas transacciones en Ethereum. Y así... el ciclo se repite continuamente.
+5. La aplicación descentralizada consulta a través de Graph Node los datos indexados de la blockchain, utilizando el [GraphQL endpoint](https://graphql.org/learn/) del nodo. El Nodo de The Graph, a su vez, traduce las consultas GraphQL en consultas para su almacenamiento de datos subyacentes con el fin de obtener estos datos, haciendo uso de las capacidades de indexación que ofrece el almacenamiento. La aplicación descentralizada muestra estos datos en una interfaz muy completa para el usuario, a fin de que los end users que usan este subgrafo puedan emitir nuevas transacciones en Ethereum. Y así... el ciclo se repite continuamente.
 
 ## Próximos puntos
 
-En las siguientes secciones entraremos en más detalles sobre cómo definir subgrafos, cómo desplegarlos y cómo consultar los datos de los índices que construye el Graph Node.
+En las siguientes secciones entraremos en más detalles sobre cómo definir subgrafos, cómo deployarlos y cómo consultar los datos de los índices que construye el Graph Node.
 
-Antes de que empieces a escribir tu propio subgrafo, es posible que debas echar un vistazo a The Graph Explorer para explorar algunos de los subgrafos que ya han sido desplegados. La página de cada subgrafo contiene un playground que te permite consultar los datos de ese subgrafo usando GraphQL.
+Antes de que empieces a escribir tu propio subgrafo, es posible que debas echar un vistazo a The Graph Explorer para explorar algunos de los subgrafos que ya han sido deployados. La página de cada subgrafo contiene un playground que te permite consultar los datos de ese subgrafo usando GraphQL.