From 9c4afc31924e11bd7bdd4152d9854c24d8011e10 Mon Sep 17 00:00:00 2001 From: GH Lee Date: Mon, 21 Sep 2020 11:33:02 +0900 Subject: [PATCH] Update cdn-support-with-asset-prefix.md (#17237) Modified paths to absolute paths. - Deploying to Vercel - Base path --- .../next.config.js/cdn-support-with-asset-prefix.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api-reference/next.config.js/cdn-support-with-asset-prefix.md b/docs/api-reference/next.config.js/cdn-support-with-asset-prefix.md index fe8b1ce0d1a66..60ebbed5abd2e 100644 --- a/docs/api-reference/next.config.js/cdn-support-with-asset-prefix.md +++ b/docs/api-reference/next.config.js/cdn-support-with-asset-prefix.md @@ -4,10 +4,10 @@ description: A custom asset prefix allows you serve static assets from a CDN. Le # CDN Support with Asset Prefix -> **Attention**: [Deploying to Vercel](docs/deployment.md) automatically configures a global CDN for your Next.js project. +> **Attention**: [Deploying to Vercel](/docs/deployment.md) automatically configures a global CDN for your Next.js project. > You do not need to manually setup an Asset Prefix. -> **Note**: Next.js 9.5+ added support for a customizable [Base Path](docs/api-reference/next.config.js/basepath.md), which is better +> **Note**: Next.js 9.5+ added support for a customizable [Base Path](/docs/api-reference/next.config.js/basepath.md), which is better > suited for hosting your application on a sub-path like `/docs`. > We do not suggest you use a custom Asset Prefix for this use case.