Updates to Substreams docs and to New Chain Integrations (#862)

* Updates to Substreams docs and to New Chain Integrations

* First round of copy, formatting, and build edits.

* quick-start, intro, and publishing done

* Dev Container, Solana,  Trans copy edits done. Found several broken links need to be fixed, but need to identify source.

* Solana Account Changes & Sinks done (more broken links need fixing)

* adding sps section (as requested) & some copy edits

* Updating copy & some links

* adjusting for all languages

* removing one solana doc

* Update website/pages/en/_meta.js

Co-authored-by: Benoît Rouleau <[email protected]>

* fixes

* Updating sps links

* Fixed links

* fixed minimal explanation

* fix

* fix to add studio link

* clarifying the non-minimal path

* Updating left-nav

* fix

* `pnpm check:fix`

---------

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

Author: 3 people

website/pages/en/_meta.js

@@ -18,19 +18,19 @@ export default {
   },
   '###2': {
     type: 'heading',
-    title: 'Substreams-Powered Subgraphs',
+    title: 'Substreams',
   },
-  sps: {
+  substreams: {
     type: 'children',
   },
   '---3': {
     type: 'separator',
   },
   '###3': {
     type: 'heading',
-    title: 'Substreams',
+    title: 'Substreams-Powered Subgraphs',
   },
-  substreams: {
+  sps: {
     type: 'children',
   },
   '---4': {

website/pages/en/sps/introduction.mdx

@@ -2,11 +2,11 @@
 title: Introduction to Substreams-Powered Subgraphs
 ---
 
-Boost your subgraph’s efficiency and scalability by using [Substreams](/substreams/introduction/) to stream pre-indexed blockchain data.
+Boost your subgraph's efficiency and scalability by using [Substreams](/substreams/introduction/) to stream pre-indexed blockchain data.
 
 ## Overview
 
-Use a Substreams package (`.spkg`) as a data source, to give your subgraph access to a stream of pre-indexed blockchain data. This enables more efficient and scalable data handling, especially with large or complex blockchain networks.
+Use a Substreams package (`.spkg`) as a data source to give your subgraph access to a stream of pre-indexed blockchain data. This enables more efficient and scalable data handling, especially with large or complex blockchain networks.
 
 ### Specifics
 

website/pages/en/substreams/developing/devcontainer.mdx

@@ -21,7 +21,7 @@ In the Dev Container, you can either build or import your own `substreams.yaml`
 ### Options
 
 - **Minimal**: Starts you with the raw block `.proto` and requires development. This path is intended for experienced users.
-- **Non-Minimal**: Extracts filtered data using network-specific cache and Protobufs from the corresponding Foundational Modules that are built and maintained by the StreamingFast team.
+- **Non-Minimal**: Extracts filtered data using network-specific caches and Protobufs taken from corresponding foundational modules (maintained by the StreamingFast team). This path generates a working Substreams out of the box.
 
 To share your work with the broader community, publish your `.spkg` to [Substreams registry](https://substreams.dev/) using:
 

website/pages/en/substreams/introduction.mdx

@@ -10,7 +10,7 @@ To start coding right away, check out the [Substreams Quick Start](/substreams/g
 
 Substreams is a powerful parallel blockchain indexing technology designed to enhance performance and scalability within The Graph Network.
 
-## Substreams Capabilities
+## Substreams Benefits
 
 - **Accelerated Indexing**: Boost subgraph indexing time with a parallelized engine for quicker data retrieval and processing.
 - **Multi-Chain Support**: Expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
@@ -37,7 +37,7 @@ fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
 
 3. The WASM container is sent to a Substreams endpoint for execution. The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
-4. You select a [sink](https://docs.substreams.dev/how-to-guides/sinks), a place where you want to send the transformed data (for example a SQL database or a Subgraph).
+4. You select a [sink](https://docs.substreams.dev/how-to-guides/sinks), a place where you want to send the transformed data (such as a SQL database or a Subgraph).
 
 ## Additional Resources