diff --git a/4.0/docs/content/custom.md b/4.0/docs/content/custom.md
index 9019ca08..2534c4a3 100644
--- a/4.0/docs/content/custom.md
+++ b/4.0/docs/content/custom.md
@@ -32,7 +32,7 @@ let hello = try req.content.decode(Hello.self, using: decoder)
 
 ## Custom Coders
 
-Application's and third-party packages can add support for media types that Vapor does not support by default by creating custom coders.
+Applications and third-party packages can add support for media types that Vapor does not support by default by creating custom coders.
 
 ### Content
 
diff --git a/4.0/docs/content/query.md b/4.0/docs/content/query.md
index 8fda5b1b..751a8b2f 100644
--- a/4.0/docs/content/query.md
+++ b/4.0/docs/content/query.md
@@ -4,14 +4,14 @@ Vapor's Content APIs support handling URL encoded data in the URL's query string
 
 ## Decoding
 
-To understand how decoding a URL query string works, take a look at the follow example request.
+To understand how decoding a URL query string works, take a look at the following example request.
 
 ```http
 GET /hello?name=Vapor HTTP/1.1
 content-length: 0
 ```
 
-Just like the APIs for handling HTTP message body content, the first step for parsing URL query strings is to create a `struct` that matches the expectd structure.
+Just like the APIs for handling HTTP message body content, the first step for parsing URL query strings is to create a `struct` that matches the expected structure.
 
 ```swift
 struct Hello: Content {