Repository: vercel/next.js
Pull request: Update cookies.mdx

delete is reserved word

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->


Changed files:
filename: docs/01-app/03-api-reference/04-functions/cookies.mdx
patch: @@ -229,8 +229,9 @@ Using the `delete()` method:
 
 import { cookies } from 'next/headers'
 
-export async function delete(data) {
-  (await cookies()).delete('name')
+export async function deleteCookie(data) {
+  const cookieStore = await cookies()
+  cookieStore.delete('name')
 }
 ```
 
@@ -239,8 +240,9 @@ export async function delete(data) {
 
 import { cookies } from 'next/headers'
 
-export async function delete(data) {
-  (await cookies()).delete('name')
+export async function deleteCookie(data) {
+  const cookieStore = await cookies()
+  cookieStore.delete('name')
 }
 ```
 
@@ -251,8 +253,9 @@ Setting a new cookie with the same name and an empty value:
 
 import { cookies } from 'next/headers'
 
-export async function delete(data) {
-  (await cookies()).set('name', '')
+export async function deleteCookie(data) {
+  const cookieStore = await cookies()
+  cookieStore.set('name', '')
 }
 ```
 
@@ -261,8 +264,9 @@ export async function delete(data) {
 
 import { cookies } from 'next/headers'
 
-export async function delete(data) {
-  (await cookies()).set('name', '')
+export async function deleteCookie(data) {
+  const cookieStore = await cookies()
+  cookieStore.set('name', '')
 }
 ```
 
@@ -273,8 +277,9 @@ Setting the `maxAge` to 0 will immediately expire a cookie. `maxAge` accepts a v
 
 import { cookies } from 'next/headers'
 
-export async function delete(data) {
-  (await cookies()).set('name', 'value', { maxAge: 0 })
+export async function deleteCookie(data) {
+  const cookieStore = await cookies()
+  cookieStore.set('name', 'value', { maxAge: 0 })
 }
 ```
 
@@ -283,9 +288,9 @@ export async function delete(data) {
 
 import { cookies } from 'next/headers'
 
-export async function delete(data) {
-  (await cookies()).set('name', 'value', { maxAge: 0 })
-``
+export async function deleteCookie(data) {
+  const cookieStore = await cookies()
+  cookieStore.set('name', 'value', { maxAge: 0 })
 }
 ```