diff --git a/Databases/GraphQL/Apollo/Apollo_Client.md b/Databases/GraphQL/Apollo/Apollo_Client.md
index 7ec9333..aae3aa8 100644
--- a/Databases/GraphQL/Apollo/Apollo_Client.md
+++ b/Databases/GraphQL/Apollo/Apollo_Client.md
@@ -2,7 +2,7 @@
 title: Apollo Client
 categories:
   - Databases
-tags: [graph-ql, apollo]
+tags: [graphql]
 ---
 
 # Apollo Client
diff --git a/Databases/GraphQL/Apollo/Apollo_Server.md b/Databases/GraphQL/Apollo/Apollo_Server.md
index 6b935e4..31ceed1 100644
--- a/Databases/GraphQL/Apollo/Apollo_Server.md
+++ b/Databases/GraphQL/Apollo/Apollo_Server.md
@@ -2,7 +2,7 @@
 title: Apollo Server
 categories:
   - Databases
-tags: [graph-ql, apollo]
+tags: [graphql]
 ---
 
 # Apollo Server
diff --git a/Databases/GraphQL/Apollo/Using_arguments_with_Apollo_Client.md b/Databases/GraphQL/Apollo/Using_arguments_with_Apollo_Client.md
index ce15014..7396218 100644
--- a/Databases/GraphQL/Apollo/Using_arguments_with_Apollo_Client.md
+++ b/Databases/GraphQL/Apollo/Using_arguments_with_Apollo_Client.md
@@ -2,7 +2,7 @@
 title: Using arguments with Apollo Client
 categories:
   - Databases
-tags: [graph-ql, apollo]
+tags: [graphql]
 ---
 
 # Using arguments with Apollo Client
@@ -114,7 +114,7 @@ const resolvers = {
 
 With the server changes complete, we can now issue a query with an argument from the client:
 
-```gql
+```js
 query track(id: 'xyz'){
   title
 }
@@ -126,7 +126,7 @@ This will return the `title` field from the track with the specific id. This que
 
 What about the following query:
 
-```gql
+```js
 query track(id: 'xyz'){
   title
   author {
@@ -137,7 +137,7 @@ query track(id: 'xyz'){
 
 It's not obvious how the resolver should respond to the nested query here since author name is not a field on `Track`, it is a field on `Author`:
 
-```gql
+```js
 type Track {
   id: ID!
   title: String!
@@ -159,7 +159,7 @@ type Author {
 
 This is where we use a **resolver chain**. Because `authorId` exists on `Track` we can use this to get the `name` part of the query. We already have a resolver for `author` under the `Track` resolver:
 
-```gql
+```js
 Track: {
     author: ({ authorId }, _, { dataSources }) => {
       return dataSources.trackApi.getAuthor(authorId);
@@ -167,8 +167,56 @@ Track: {
   },
 ```
 
-Notice that `authorId` is used in the place of the `parent` parameter. It already exists on the `Track` that we return from the query. So this can be invoked to fulfill `author` and thereby access the author name from the `graph`.
+Notice that `authorId` is used in the place of the `parent` parameter. It already exists on the `Track` type that wraps. So this can be invoked to fulfill `author` and thereby access the author name from the graph.
 
 > I don't really understand this but the general point seems to be that the resolvers outside of the main `Query` block in the resolver are tied to a data type and can be used to magically populate query requests for nested fields providing a key is on the main datatype returned.
 
 Now repeat this example with `modules`
+
+This process is also required for our extended schema. The `Track` type now has a `modules` field that comprises an array of the `Module` type.
+
+Here's a reminder of the `Module` type:
+
+```js
+type Module {
+    id: ID!
+    title: String!
+    length: Int
+}
+```
+
+The modules for a `Track` can be sourced from the track `id`. So we can again add a resolver chain function to the resolvers file:
+
+```js
+const resolvers = {
+  Query: {
+    tracksForHome: (_, __, { dataSources }) => {
+      return dataSources.trackApi.getTracksForHome();
+    },
+    track: (_, { id }, { dataSources }) => {
+      return dataSources.trackAPI.getTrack(id);
+    },
+  },
+  Track: {
+    author: ({ authorId }, _, { dataSources }) => {
+      return dataSources.trackApi.getAuthor(authorId);
+    },
+    modules: ({ id }, _, { dataSources }) => {
+      return dataSources.trackAPI.getTrackModules(id);
+    },
+  },
+};
+```
+
+Once again we are using a property on the parent `Track` type to use as a parameter in the resolver function.
+
+This setup would enables like the following to be run:
+
+```js
+query track(id: 'xyz'){
+  title
+  modules
+}
+```
+
+The '
diff --git a/Databases/GraphQL/Journey_of_GraphQL_query.md b/Databases/GraphQL/Journey_of_GraphQL_query.md
index 346328b..64c1122 100644
--- a/Databases/GraphQL/Journey_of_GraphQL_query.md
+++ b/Databases/GraphQL/Journey_of_GraphQL_query.md
@@ -1,9 +1,9 @@
 ---
 categories:
   - Databases
-tags: [graph-ql]
+tags: [graphql]
 ---
 
 # The journey of a GraphQL query
 
-![](/img/graphql-journey-two.svg)
\ No newline at end of file
+![](/img/graphql-journey-two.svg)
diff --git a/Databases/GraphQL/Schema_Definition_Language.md b/Databases/GraphQL/Schema_Definition_Language.md
index 97bdbe9..4b7279f 100644
--- a/Databases/GraphQL/Schema_Definition_Language.md
+++ b/Databases/GraphQL/Schema_Definition_Language.md
@@ -1,7 +1,7 @@
 ---
 categories:
   - Databases
-tags: [graph-ql]
+tags: [graphql]
 ---
 
 # Schema Definition Language
diff --git a/Databases/GraphQL/Using_GraphQL_with_Node.md b/Databases/GraphQL/Using_GraphQL_with_Node.md
index f959463..9260ea4 100644
--- a/Databases/GraphQL/Using_GraphQL_with_Node.md
+++ b/Databases/GraphQL/Using_GraphQL_with_Node.md
@@ -2,7 +2,7 @@
 title: Using GraphQL with Node.js
 categories:
   - Databases
-tags: [graph-ql, node-js]
+tags: [graphql, node-js]
 ---
 
 # Using GraphQL with Node.js