minor edits

Author: idalithb

website/pages/en/quick-start.mdx

@@ -87,9 +87,9 @@ The `init` command in the previous step creates a scaffold subgraph that you can
 
 When making changes to the subgraph, you will mainly work with three files:
 
-- Manifest (`subgraph.yaml`) - defines what datasources your subgraphs will index.
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraphs will index.
 - Schema (`schema. graphql`) - defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - translates data from your datasources to the entities defined in the schema.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
 For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
@@ -107,7 +107,7 @@ Remember, deploying is not the same as publishing.
     graph build
     ```
 
-2.  Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+2.  Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
 
     ```sh
 
@@ -117,7 +117,7 @@ Remember, deploying is not the same as publishing.
     ```
 
 - The CLI will ask for a version label.
-  - It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. That said, you can choose any string for the version such as: `v1, version1, asdf`, ect.
+  - It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`. That said, you can choose any string for the version such as: `v1,` `version1,` `asdf`, etc.
 
 ### 6. Review Your Subgraph