New caps (#886)

* Archive

* Indexing

* Resources

* SPS

* Best practices

* Cookbook

* Developing

* Everything else

* Looks like some were missed

---------

Co-authored-by: benface <[email protected]>

website/src/pages/en/about.mdx

@@ -30,38 +30,38 @@ Blockchain properties, such as finality, chain reorganizations, and uncled block
 
 ## The Graph Provides a Solution
 
-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.
+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.
 
 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.
 
 ### How The Graph Functions
 
-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.
+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.
 
 #### Specifics
 
-- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
+- The Graph uses Subgraph descriptions, which are known as the Subgraph manifest inside the Subgraph.
 
-- 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 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.
 
-- When creating a subgraph, you need to write a subgraph manifest.
+- When creating a Subgraph, you need to write a Subgraph manifest.
 
-- 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.
+- 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.
 
-The diagram below provides more detailed information about the flow of data after a subgraph manifest has been deployed 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)
 
 The flow follows these steps:
 
 1.  A dapp adds data to Ethereum through a transaction on a smart contract.
 2.  The smart contract emits one or more events while processing the transaction.
-3.  Graph Node continually scans Ethereum for new blocks and the data for your subgraph they may contain.
-4.  Graph Node finds Ethereum events for your subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events.
+3.  Graph Node continually scans Ethereum for new blocks and the data for your Subgraph they may contain.
+4.  Graph Node finds Ethereum events for your Subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events.
 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.
 
 ## Next Steps
 
-The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
+The following sections provide a more in-depth look at Subgraphs, their deployment and data querying.
 
-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.
+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/src/pages/en/archived/arbitrum/arbitrum-faq.mdx

@@ -14,7 +14,7 @@ By scaling The Graph on L2, network participants can now benefit from:
 
 - 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 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.
+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.
 
@@ -38,7 +38,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle
 
 ![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?
+## As a Subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
 Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support.
 
@@ -50,9 +50,9 @@ All smart contracts have been thoroughly [audited](https://github.com/graphproto
 
 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).
 
-## Are existing subgraphs on Ethereum working?
+## Are existing Subgraphs on Ethereum working?
 
-All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
+All Subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your Subgraphs operate seamlessly.
 
 ## Does GRT have a new smart contract deployed on Arbitrum?