diff --git a/website/pages/en/indexing/overview.mdx b/website/pages/en/indexing/overview.mdx index ae9f6cd286b7..288842f65a1a 100644 --- a/website/pages/en/indexing/overview.mdx +++ b/website/pages/en/indexing/overview.mdx @@ -258,7 +258,7 @@ indexer= cat > terraform.tfvars < Note: `indexer-agent` does not currently handle the indexing of this subgraph like it does for the network subgraph deployement. As a result, you have to index it manually. +> Note: `indexer-agent` does not currently handle the indexing of this subgraph like it does for the network subgraph deployment. As a result, you have to index it manually. ## Migration Guide diff --git a/website/pages/en/indexing/tooling/graph-node.mdx b/website/pages/en/indexing/tooling/graph-node.mdx index 003a17e22ec4..0e8664f688c4 100644 --- a/website/pages/en/indexing/tooling/graph-node.mdx +++ b/website/pages/en/indexing/tooling/graph-node.mdx @@ -287,7 +287,7 @@ During indexing subgraphs might fail, if they encounter data that is unexpected, In some cases a failure might be resolvable by the indexer (for example if the error is a result of not having the right kind of provider, adding the required provider will allow indexing to continue). However in others, a change in the subgraph code is required. -> Deterministic failures are considered "final", with a Proof of Indexing generated for the failing block, while non-determinstic failures are not, as the subgraph may manage to "unfail" and continue indexing. In some cases, the non-deterministic label is incorrect, and the subgraph will never overcome the error; such failures should be reported as issues on the Graph Node repository. +> Deterministic failures are considered "final", with a Proof of Indexing generated for the failing block, while non-deterministic failures are not, as the subgraph may manage to "unfail" and continue indexing. In some cases, the non-deterministic label is incorrect, and the subgraph will never overcome the error; such failures should be reported as issues on the Graph Node repository. #### Block and call cache diff --git a/website/pages/en/subgraphs/developing/creating/advanced.mdx b/website/pages/en/subgraphs/developing/creating/advanced.mdx index 97437ad1a3f8..3296b94335e6 100644 --- a/website/pages/en/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/en/subgraphs/developing/creating/advanced.mdx @@ -272,7 +272,7 @@ You can now create file data sources during execution of chain-based handlers: - Import the template from the auto-generated `templates` - call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave -For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`). +For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifiers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`). For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing). diff --git a/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx index 8158751c35c1..2e22f85a18c0 100644 --- a/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx @@ -37,7 +37,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | | 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | -| 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | +| 0.0.3 | Added `from` field to the Ethereum Call object
`ethereum.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | ### Built-in Types diff --git a/website/pages/en/subgraphs/developing/creating/graph-ts/common-issues.mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/common-issues.mdx index 5b99efa8f493..f8d0c9c004c2 100644 --- a/website/pages/en/subgraphs/developing/creating/graph-ts/common-issues.mdx +++ b/website/pages/en/subgraphs/developing/creating/graph-ts/common-issues.mdx @@ -4,5 +4,5 @@ title: Common AssemblyScript Issues There are certain [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) issues that are common to run into during subgraph development. They range in debug difficulty, however, being aware of them may help. The following is a non-exhaustive list of these issues: -- `Private` class variables are not enforced in [AssembyScript](https://www.assemblyscript.org/status.html#language-features). There is no way to protect class variables from being directly changed from the class object. +- `Private` class variables are not enforced in [AssemblyScript](https://www.assemblyscript.org/status.html#language-features). There is no way to protect class variables from being directly changed from the class object. - Scope is not inherited into [closure functions](https://www.assemblyscript.org/status.html#on-closures), i.e. variables declared outside of closure functions cannot be used. Explanation in [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s). diff --git a/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx index 3b59ee1398b9..2133c1d4b5c9 100644 --- a/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx @@ -2,7 +2,7 @@ title: Unit Testing Framework --- -Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs. +Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and successfully deploy their subgraphs. ## Benefits of Using Matchstick @@ -392,7 +392,7 @@ describe('handleUpdatedGravatars', () => { gravatar.save() }) - test('Upates the displayName', () => { + test('Updates the displayName', () => { assert.fieldEquals('Gravatar', '0x0', 'displayName', 'First Gravatar') // code that should update the displayName to 1st Gravatar @@ -441,7 +441,7 @@ describe("handleNewGravatar", () => { }) describe("handleUpdatedGravatar", () => { - test("Upates the displayName", () => { + test("Updates the displayName", () => { assert.fieldEquals("Gravatar", "0x0", "displayName", "First Gravatar") // code that should update the displayName to 1st Gravatar @@ -481,7 +481,7 @@ describe("handleUpdatedGravatar", () => { store.remove("Gravatar", "0x0") }) - test("Upates the displayName", () => { + test("Updates the displayName", () => { assert.fieldEquals("Gravatar", "0x0", "displayName", "First Gravatar") // code that should update the displayName to 1st Gravatar @@ -603,7 +603,7 @@ export function createNewGravatarEvent( newGravatarEvent.parameters = new Array() let idParam = new ethereum.EventParam('id', ethereum.Value.fromI32(id)) let addressParam = new ethereum.EventParam( - 'ownderAddress', + 'ownerAddress', ethereum.Value.fromAddress(Address.fromString(ownerAddress)), ) let displayNameParam = new ethereum.EventParam('displayName', ethereum.Value.fromString(displayName)) @@ -1160,7 +1160,7 @@ test('ethereum/contract dataSource creation example', () => { #### Testing `file/ipfs` templates -Similarly to contract dynamic data sources, users can test test file datas sources and their handlers +Similarly to contract dynamic data sources, users can test test file data sources and their handlers ##### Example `subgraph.yaml` diff --git a/website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx b/website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx index 6afcdeeb303d..c8eed0425d03 100644 --- a/website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx +++ b/website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx @@ -35,7 +35,7 @@ To transfer ownership of a subgraph, do the following: 2. Choose the address that you would like to transfer the subgraph to: - ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png) + ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-2.png) Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea: diff --git a/website/pages/en/subgraphs/querying/graphql-api.mdx b/website/pages/en/subgraphs/querying/graphql-api.mdx index 8813e2eeb3f3..cf112123c610 100644 --- a/website/pages/en/subgraphs/querying/graphql-api.mdx +++ b/website/pages/en/subgraphs/querying/graphql-api.mdx @@ -29,7 +29,7 @@ Query for a single `Token` entity defined in your schema: } ``` -> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string. +> Note: When querying for a single entity, the `id` field is required, and it must be written as a string. Query all `Token` entities: @@ -389,7 +389,7 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021 ## Schema -The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). +The schema of your dataSources, i.e. the entity types, values, and relationships that are available to query, are defined through the [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System). GraphQL schemas generally define root types for `queries`, `subscriptions` and `mutations`. The Graph only supports `queries`. The root `Query` type for your subgraph is automatically generated from the GraphQL schema that's included in your [subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). diff --git a/website/pages/en/subgraphs/querying/python.mdx b/website/pages/en/subgraphs/querying/python.mdx index 4fb618510070..c10d7a0e57ab 100644 --- a/website/pages/en/subgraphs/querying/python.mdx +++ b/website/pages/en/subgraphs/querying/python.mdx @@ -53,4 +53,4 @@ Since subgrounds has a large feature set to explore, here are some helpful start - [Concurrent Queries](https://docs.playgrounds.network/subgrounds/getting_started/async/) - Learn how to level up your queries by parallelizing them. - [Exporting Data to CSVs](https://docs.playgrounds.network/subgrounds/faq/exporting/) - - A quick article on how to seemlessly save your data as CSVs for further analysis. + - A quick article on how to seamlessly save your data as CSVs for further analysis. diff --git a/website/pages/en/substreams/sps/triggers.mdx b/website/pages/en/substreams/sps/triggers.mdx index e5e510a6a7ad..a923fe40ec78 100644 --- a/website/pages/en/substreams/sps/triggers.mdx +++ b/website/pages/en/substreams/sps/triggers.mdx @@ -10,7 +10,7 @@ The following code demonstrates how to define a `handleTransactions` function in ```tsx export function handleTransactions(bytes: Uint8Array): void { - let transactions = assembly.eth.transaction.v1.Transactions.decode(bytes.buffer).trasanctions // 1. + let transactions = assembly.eth.transaction.v1.Transactions.decode(bytes.buffer).transactions // 1. if (transactions.length == 0) { log.info('No transactions found', []) return