From cb6852f67b5fa4a71ceffb00ff2742ad8725fbe4 Mon Sep 17 00:00:00 2001 From: Boyan Bratvanov <6027160+bratvanov@users.noreply.github.com> Date: Sun, 29 Dec 2024 21:36:32 +0200 Subject: [PATCH] docs: fix typo in route-segment-config --- .../03-file-conventions/route-segment-config.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01-app/04-api-reference/03-file-conventions/route-segment-config.mdx b/docs/01-app/04-api-reference/03-file-conventions/route-segment-config.mdx index f0f9d1f2d9019..5c972446fbe4f 100644 --- a/docs/01-app/04-api-reference/03-file-conventions/route-segment-config.mdx +++ b/docs/01-app/04-api-reference/03-file-conventions/route-segment-config.mdx @@ -204,7 +204,7 @@ By default, Next.js does not limit the execution of server-side logic (rendering Deployment platforms can use `maxDuration` from the Next.js build output to add specific execution limits. For example, on [Vercel](https://vercel.com/docs/functions/serverless-functions/runtimes#max-duration). -**Note**: This settings requires Next.js `13.4.10` or higher. +**Note**: This setting requires Next.js `13.4.10` or higher. ```tsx filename="layout.tsx | page.tsx | route.ts" switcher export const maxDuration = 5