From f2531a2b6617c3ff2b5e003d612bca0ddcbf5083 Mon Sep 17 00:00:00 2001
From: Matheus Souza <37983247+souzasmatheus@users.noreply.github.com>
Date: Sun, 7 Mar 2021 17:44:50 -0300
Subject: [PATCH 1/2] Fix grammar mistake

---
 docs/api/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/api/index.md b/docs/api/index.md
index 38632fa81..232985a43 100644
--- a/docs/api/index.md
+++ b/docs/api/index.md
@@ -46,7 +46,7 @@ app.listen(3000);
   control flows back "upstream".
 
   The following example responds with "Hello World", however first the request flows through
-  the `x-response-time` and `logging` middleware to mark when the request started, then continue
+  the `x-response-time` and `logging` middleware to mark when the request started, then continues
   to yield control through the response middleware. When a middleware invokes `next()`
   the function suspends and passes control to the next middleware defined. After there are no more
   middleware to execute downstream, the stack will unwind and each middleware is resumed to perform

From 5a8569da02421f8b2ecfb24dde71ee01ee296120 Mon Sep 17 00:00:00 2001
From: Matheus Souza <37983247+souzasmatheus@users.noreply.github.com>
Date: Wed, 24 Mar 2021 13:47:59 -0300
Subject: [PATCH 2/2] Simplify correction

---
 docs/api/index.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/api/index.md b/docs/api/index.md
index 232985a43..d1b3a9b59 100644
--- a/docs/api/index.md
+++ b/docs/api/index.md
@@ -46,8 +46,7 @@ app.listen(3000);
   control flows back "upstream".
 
   The following example responds with "Hello World", however first the request flows through
-  the `x-response-time` and `logging` middleware to mark when the request started, then continues
-  to yield control through the response middleware. When a middleware invokes `next()`
+  the `x-response-time` and `logging` middleware to mark when the request started, then yields control through the response middleware. When a middleware invokes `next()`
   the function suspends and passes control to the next middleware defined. After there are no more
   middleware to execute downstream, the stack will unwind and each middleware is resumed to perform
   its upstream behaviour.