From 7ef73342806b0331d100b774337b7741f2e1d81e Mon Sep 17 00:00:00 2001
From: TheOtherBrian1 <91111415+TheOtherBrian1@users.noreply.github.com>
Date: Thu, 26 Mar 2026 20:04:34 -0400
Subject: [PATCH] Update
 apps/docs/content/troubleshooting/edge-function-504-error-response.mdx

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

diff --git a/apps/docs/content/troubleshooting/edge-function-504-error-response.mdx b/apps/docs/content/troubleshooting/edge-function-504-error-response.mdx
index f879355f8be..7a75ec315e9 100644
--- a/apps/docs/content/troubleshooting/edge-function-504-error-response.mdx
+++ b/apps/docs/content/troubleshooting/edge-function-504-error-response.mdx
@@ -143,7 +143,7 @@ GROUP BY req.pathname, res.status_code
 limit 10
 ```
 
-### When Optimization Is not enough
+### When optimization Is not enough
 
 Edge Functions have a hard runtime ceiling that cannot be raised. If your use case genuinely requires more, consider:
 - using a serverless/edge function service, such as [AWS Lambda](https://aws.amazon.com/pm/lambda/), with fewer restrictions