diff --git a/src/content/blog/2020-12-08-defer-stream.md b/src/content/blog/2020-12-08-defer-stream.md
index 1fa6527914..0aceaa61a9 100644
--- a/src/content/blog/2020-12-08-defer-stream.md
+++ b/src/content/blog/2020-12-08-defer-stream.md
@@ -24,6 +24,7 @@ query {
   person(id: "cGVvcGxlOjE=") {
     name
     ...HomeworldFragment @defer(label: "homeworldDefer")
+  }
 }
 
 fragment HomeworldFragment on Person {
diff --git a/src/content/blog/2022-11-07-graphql-http.md b/src/content/blog/2022-11-07-graphql-http.md
index dd9cde0af7..27e96f0234 100644
--- a/src/content/blog/2022-11-07-graphql-http.md
+++ b/src/content/blog/2022-11-07-graphql-http.md
@@ -29,7 +29,7 @@ fallen behind.
 Luckily, thanks to the focused efforts of [Denis Badurina](https://github.com/enisdenjo),
 we have an alternative in [graphql-http](https://github.com/graphql/graphql-http).
 Denis has been part of the committee working on the GraphQL over HTTP
-specification, and sought to build a depenency-free compliant GraphQL server
+specification, and sought to build a dependency-free compliant GraphQL server
 that works with most all existing Node and Deno HTTP frameworks.
 
 The decision was made to adopt the [graphql-http](https://github.com/graphql/graphql-http)
diff --git a/src/content/learn/BestPractice-NodeInterface.md b/src/content/learn/BestPractice-NodeInterface.md
index 0557bb37d5..f24351eba9 100644
--- a/src/content/learn/BestPractice-NodeInterface.md
+++ b/src/content/learn/BestPractice-NodeInterface.md
@@ -27,6 +27,7 @@ objects "nodes." Here is an example query for a node:
       name
     }
   }
+}
 ```
 
 - The GraphQL schema is formatted to allow fetching any object via the `node` field on the root query object. This