From 753b4786cfea7b13c661eec57f96a9385eb90392 Mon Sep 17 00:00:00 2001 From: Adrian Faustino Date: Thu, 7 Nov 2024 23:26:50 -0800 Subject: [PATCH] Fix typo in 03-server-actions-and-mutations.mdx --- .../02-data-fetching/03-server-actions-and-mutations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01-app/02-building-your-application/02-data-fetching/03-server-actions-and-mutations.mdx b/docs/01-app/02-building-your-application/02-data-fetching/03-server-actions-and-mutations.mdx index 31a02375f9c1d..128ea733b9bf3 100644 --- a/docs/01-app/02-building-your-application/02-data-fetching/03-server-actions-and-mutations.mdx +++ b/docs/01-app/02-building-your-application/02-data-fetching/03-server-actions-and-mutations.mdx @@ -882,7 +882,7 @@ See [additional examples](/docs/app/api-reference/functions/cookies#deleting-coo ## Security By default, when a Server Action is created and exported, it creates a public HTTP endpoint -and should be treated with the same security assumptions and authorization checks. This means, even if a Server Action or utility function is not imported elsewhere in your code, it’s still a publicly accessible. +and should be treated with the same security assumptions and authorization checks. This means, even if a Server Action or utility function is not imported elsewhere in your code, it’s still publicly accessible. To improve security, Next.js has the following built-in features: