From bbe7fddf3950122e7d9d116570e52766cd48c1e9 Mon Sep 17 00:00:00 2001 From: Steven Tey Date: Thu, 27 Oct 2022 14:02:27 -0700 Subject: [PATCH] Fix broken link in `@next/font` docs (#42002) As per https://twitter.com/pbshgthm/status/1585728924499480576 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) --- docs/api-reference/next/font.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-reference/next/font.md b/docs/api-reference/next/font.md index 97a324fedc56..426b6055852e 100644 --- a/docs/api-reference/next/font.md +++ b/docs/api-reference/next/font.md @@ -294,7 +294,7 @@ import { greatVibes, sourceCodePro400 } from '@/fonts'; ## Next Steps
- + Font Optmization Learn how to optimize fonts with the Font module.