Repository: vercel/next.js
Pull request: Fix spelling in robots.mdx documentation

This pull request makes minor documentation improvements to the `robots.mdx` API reference, correcting a typo and clarifying the description of `robots.js` route handler behavior.

- Documentation clarity and typo fixes:
  * Corrected "Route Handlers" to "Route Handler" in the description of `robots.js` and updated the explanation for clarity.
  * Fixed the spelling of "customise" to "customize" for consistency with American English.* Fixed spelling on some words of the robots.mdx documentation: 
- Handlers (plural) to Handler (singular)
- customise = customize

<!-- 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/03-file-conventions/01-metadata/robots.mdx
patch: @@ -19,7 +19,7 @@ Sitemap: https://acme.com/sitemap.xml
 
 Add a `robots.js` or `robots.ts` file that returns a [`Robots` object](#robots-object).
 
-> **Good to know**: `robots.js` is a special Route Handlers that is cached by default unless it uses a [Dynamic API](/docs/app/guides/caching#dynamic-apis) or [dynamic config](/docs/app/guides/caching#segment-config-options) option.
+> **Good to know**: `robots.js` is a special Route Handler that is cached by default unless it uses a [Dynamic API](/docs/app/guides/caching#dynamic-apis) or [dynamic config](/docs/app/guides/caching#segment-config-options) option.
 
 ```ts filename="app/robots.ts" switcher
 import type { MetadataRoute } from 'next'
@@ -61,7 +61,7 @@ Sitemap: https://acme.com/sitemap.xml
 
 ### Customizing specific user agents
 
-You can customise how individual search engine bots crawl your site by passing an array of user agents to the `rules` property. For example:
+You can customize how individual search engine bots crawl your site by passing an array of user agents to the `rules` property. For example:
 
 ```ts filename="app/robots.ts" switcher
 import type { MetadataRoute } from 'next'