diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js
index 33ff7aa81650..f15304085f70 100644
--- a/website/pages/en/_meta.js
+++ b/website/pages/en/_meta.js
@@ -18,9 +18,9 @@ export default {
   },
   '###2': {
     type: 'heading',
-    title: 'Substreams-Powered Subgraphs',
+    title: 'Substreams',
   },
-  sps: {
+  substreams: {
     type: 'children',
   },
   '---3': {
@@ -28,9 +28,9 @@ export default {
   },
   '###3': {
     type: 'heading',
-    title: 'Substreams',
+    title: 'Substreams-Powered Subgraphs',
   },
-  substreams: {
+  sps: {
     type: 'children',
   },
   '---4': {
diff --git a/website/pages/en/sps/introduction.mdx b/website/pages/en/sps/introduction.mdx
index aa44f605ce65..a4959772e560 100644
--- a/website/pages/en/sps/introduction.mdx
+++ b/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
 
diff --git a/website/pages/en/substreams/developing/devcontainer.mdx b/website/pages/en/substreams/developing/devcontainer.mdx
index cd65c8d046f8..5b07c96c97ae 100644
--- a/website/pages/en/substreams/developing/devcontainer.mdx
+++ b/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:
 
diff --git a/website/pages/en/substreams/introduction.mdx b/website/pages/en/substreams/introduction.mdx
index 25fcfa5a5c2c..088188773a08 100644
--- a/website/pages/en/substreams/introduction.mdx
+++ b/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