From 4e34bed230fa02c154eb0761cbb1a76be3479e98 Mon Sep 17 00:00:00 2001
From: TheOtherBrian1 <91111415+TheOtherBrian1@users.noreply.github.com>
Date: Thu, 26 Mar 2026 11:52:03 -0400
Subject: [PATCH] Update
 apps/docs/content/troubleshooting/edge-function-404-error-response.mdx

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 .../troubleshooting/edge-function-404-error-response.mdx        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx b/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx
index 66dd7259b29..956d54bd5de 100644
--- a/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx
+++ b/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx
@@ -96,7 +96,7 @@ return new Response(JSON.stringify({ error: 'Not found' }), {
 **How to fix:**
 
 1. Search your function code for `404`. Look for explicit status codes on `Response` objects.
-2. Trace the condition that triggered it. If your function calls external APIs, it may simply be passing along errors returned by those services.
+2. Trace the condition that triggered it. If your function calls external APIs, it may be passing along errors returned by those services.
 3. Add logging before the return so future occurrences leave a trace:
 
 ```js