From 6a438e28e36ee84bf0c90b5f4d6d96efdef9e72f Mon Sep 17 00:00:00 2001
From: Yusuke Hayashi <yusuke8h@gmail.com>
Date: Sat, 3 Sep 2022 03:20:22 +0900
Subject: [PATCH] Fix typo in error/middleware-upgrade-guide.md (#40176)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

No Reponse Body -> No Response Body

<img width="330" alt="スクリーンショット 2022-09-02 16 40 04" src="https://user-images.githubusercontent.com/11132792/188084749-a1dd4ca6-b108-47ef-85d9-5f1602cb8cea.png">
---
 errors/middleware-upgrade-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/errors/middleware-upgrade-guide.md b/errors/middleware-upgrade-guide.md
index 8c04cc6c4f3b06..94af0bceeae512 100644
--- a/errors/middleware-upgrade-guide.md
+++ b/errors/middleware-upgrade-guide.md
@@ -388,4 +388,4 @@ Prior to Next.js `v12.2`, Middleware was not executed for `_next` requests.
 
 For cases where Middleware is used for authorization, you should migrate to use `rewrite`/`redirect` to Pages that show an authorization error, login forms, or to an API Route.
 
-See [No Reponse Body](#no-response-body) for an example of how to migrate to use `rewrite`/`redirect`.
+See [No Response Body](#no-response-body) for an example of how to migrate to use `rewrite`/`redirect`.