docs: inline-link existing terms in Common errors descriptions

Co-Authored-By: Devin Logan <devinannlogan@gmail.com>

Author: devin-ai-integration[bot]

fern/products/docs/pages/authentication/rbac.mdx

@@ -80,7 +80,7 @@ You can also combine `roles` with `products` and `versions` props.
 ## Common errors
 
 <Accordion title='Role "X" is used but not declared at the top level of the docs.yml file.'>
-  A `viewers:` entry or `<If roles={[...]}>` reference uses a role that isn't listed under the top-level `roles:` key in `docs.yml`. Add the role to the `roles` list:
+  A [`viewers:`](#in-navigation) entry or [`<If roles={[...]}>`](/learn/docs/writing-content/components/if) reference uses a role that isn't listed under the top-level `roles:` key in `docs.yml`. Add the role to the [`roles`](#setup) list:
 
   ```yaml title="docs.yml"
   roles:

fern/products/docs/pages/navigation/frontmatter.mdx

@@ -40,7 +40,7 @@ Frontmatter uses YAML syntax, but values are also processed as MDX. Some charact
 | `"` `'` | Opposite style or `\` | `title: 'The "best" practices'` |
 
 <Info title='Error: "Failed to parse frontmatter"'>
-  If `fern check` reports `Failed to parse frontmatter`, the YAML between the `---` markers is invalid. The most common cause is an unquoted value containing one of the special characters above. Wrap the value in quotes or escape the character and re-run `fern check`.
+  If `fern check` reports `Failed to parse frontmatter`, the [YAML](#frontmatter-syntax) between the `---` markers is invalid. The most common cause is an unquoted value containing one of the [special characters](#special-characters) above. Wrap the value in quotes or escape the character and re-run `fern check`.
 </Info>
 
 ## Title

fern/products/docs/pages/navigation/tabs.mdx

@@ -131,13 +131,13 @@ theme:
 
 <AccordionGroup>
   <Accordion title='Tab "X" is missing from the tabs configuration.'>
-    The `navigation` list references a tab key that isn't declared under the top-level `tabs` object. Add the tab to `tabs:` in `docs.yml` (with at least a `display-name`), or update the `- tab:` reference in `navigation` to match an existing key.
+    The [`navigation`](/learn/docs/configuration/navigation) list references a tab key that isn't declared under the top-level `tabs` object. Add the tab to `tabs:` in `docs.yml` (with at least a [`display-name`](#tab-properties)), or update the `- tab:` reference in `navigation` to match an existing key.
   </Accordion>
   <Accordion title='Tab "X" has both a href and layout. Only one should be used.'>
-    A tab entry combines `href` with `layout` or `variants`. Use `href` for external links, or `layout`/`variants` for internal content — not both.
+    A tab entry combines [`href`](#tab-properties) with [`layout`](#tab-properties) or [`variants`](#tab-variants). Use `href` for external links, or `layout`/`variants` for internal content — not both.
   </Accordion>
   <Accordion title='Tab "X" is missing a href, layout, or variants.'>
-    Every tab in `navigation` must point somewhere. Add a `layout`, `variants`, or `href` to the tab entry.
+    Every tab in [`navigation`](/learn/docs/configuration/navigation) must point somewhere. Add a [`layout`](#tab-properties), [`variants`](#tab-variants), or [`href`](#tab-properties) to the tab entry.
   </Accordion>
 </AccordionGroup>
 

fern/products/docs/pages/preview-publish/preview-changes-locally.mdx

@@ -52,21 +52,21 @@ Some features are disabled in local development:
 
 <AccordionGroup>
   <Accordion title="No docs.yml file found. Please make sure your project has one.">
-    `fern docs dev` and `fern generate --docs` must be run from a directory that contains a `fern/` folder with a `docs.yml` inside. Change into your project directory, or create a `docs.yml` — see [Project structure](/learn/docs/getting-started/project-structure).
+    `fern docs dev` and `fern generate --docs` must be run from a directory that contains a [`fern/` folder](/learn/docs/getting-started/project-structure) with a `docs.yml` inside. Change into your project directory, or add a `docs.yml`.
   </Accordion>
   <Accordion title="Broken link to /some/path (resolved path: ...)">
     `fern check` reports this when a link in a Markdown page doesn't resolve to a real page, anchor, or file in your docs.
 
-    - For internal pages, use the [published URL path](/learn/docs/writing-content/markdown-basics#link-format) from your `docs.yml` config (for example, `/learn/docs/configuration/navigation`) — not a relative path or on-disk file path.
-    - For images and other assets, use a path relative to the Markdown file.
+    - For [internal pages](/learn/docs/writing-content/markdown-basics#link-format), use the published URL path from your `docs.yml` config (for example, `/learn/docs/configuration/navigation`) — not a relative path or on-disk file path.
+    - For [images and other assets](/learn/docs/writing-content/markdown-media), use a path relative to the Markdown file.
 
     Broken internal links fail by default. Use [`fern generate --docs --no-strict-broken-links`](/learn/cli-api-reference/cli-reference/commands#fern-generate) to downgrade the failure to a warning while you fix them.
   </Accordion>
   <Accordion title="Invalid URL: /some/path">
     A Markdown link or `<img src>` uses a value that isn't a valid URL. Check for typos, unescaped characters, or missing protocols on external links.
   </Accordion>
   <Accordion title="Path ./pages/foo.mdx does not exist">
-    A `path:` in `docs.yml` points to a file that isn't on disk. Fix the path or create the missing file. Paths are relative to the YAML file that defines them.
+    A [`path:`](/learn/docs/configuration/navigation) in `docs.yml` points to a file that isn't on disk. Fix the path or create the missing file. Paths are relative to the YAML file that defines them.
   </Accordion>
 </AccordionGroup>
 

fern/products/docs/pages/preview-publish/publishing-your-docs.mdx

@@ -196,10 +196,10 @@ To unpublish a docs site, navigate to the **Settings** page for your site in the
 
 <AccordionGroup>
   <Accordion title="No token found. Please set the FERN_TOKEN environment variable or run `fern login`.">
-    `fern generate --docs` needs an authenticated session to publish. Run `fern login` locally, or set `FERN_TOKEN` in your shell or CI environment. Use [`fern token`](/learn/cli-api-reference/cli-reference/commands#fern-token) to generate a CI-friendly token.
+    `fern generate --docs` needs an authenticated session to publish. Run [`fern login`](/learn/cli-api-reference/cli-reference/commands#fern-login) locally, or set `FERN_TOKEN` in your shell or CI environment. Use [`fern token`](/learn/cli-api-reference/cli-reference/commands#fern-token) to generate a CI-friendly token.
   </Accordion>
   <Accordion title="OpenAPI spec validation failed with N errors. Fix the errors above before generating docs.">
-    One or more OpenAPI specs referenced by the docs have fatal validation errors. The individual `<file>: <message>` lines above this message identify the exact problem — fix those in your spec, then re-run `fern generate --docs`.
+    One or more [OpenAPI specs](/learn/docs/api-references/overview) referenced by the docs have fatal validation errors. The individual `<file>: <message>` lines above this message identify the exact problem — fix those in your spec, then re-run `fern generate --docs`.
   </Accordion>
 </AccordionGroup>
 

fern/products/docs/pages/preview-publish/setting-up-your-domain.mdx

@@ -206,7 +206,7 @@ Errors below are surfaced by `fern check` and `fern generate --docs` when valida
     The `url` is missing a subdomain or uses an unexpected shape. Use `<your-org>.docs.buildwithfern.com` (for example, `plantstore.docs.buildwithfern.com`). Don't include `https://`.
   </Accordion>
   <Accordion title='Invalid domain in URL "X". The URL must end with one of: docs.buildwithfern.com, docs.dev.buildwithfern.com'>
-    The `url` doesn't end with a supported Fern domain. Update the `url` to end with `docs.buildwithfern.com`. Configure your vanity domain with `custom-domain`.
+    The `url` doesn't end with a supported Fern domain. Update the `url` to end with `docs.buildwithfern.com`. Configure your vanity domain with [`custom-domain`](#multiple-custom-domains).
   </Accordion>
   <Accordion title='Invalid URL "X". A subdomain is required before docs.buildwithfern.com'>
     The `url` is set to the bare domain. Add a subdomain prefix such as `<your-org>.docs.buildwithfern.com`.
@@ -227,4 +227,4 @@ instances:
 
 <Info>
 After configuring multiple domains in your `docs.yml`, contact Fern via your dedicated Slack channel or [email](mailto:support@buildwithfern.com) to complete the setup. You'll receive DNS configuration details for each domain.
-</Info>                                                                                                
+</Info>                                                                                                                                                

fern/products/docs/pages/seo/redirects.mdx

@@ -18,16 +18,16 @@ Errors below are surfaced by `fern check` and `fern generate --docs`.
 
 <AccordionGroup>
   <Accordion title='Page "X" was moved from "/old" to "/new". The old URL will return 404 without a redirect.'>
-    A page's slug changed relative to the last published version of your docs. Add a redirect in `docs.yml` so existing links keep working:
+    A page's [slug](/learn/docs/seo/configuring-slugs) changed relative to the last [published version](/learn/docs/preview-publish/publishing-your-docs) of your docs. Add a [redirect](/learn/docs/configuration/site-level-settings#redirects-configuration) in `docs.yml` so existing links keep working:
 
     ```yaml title="docs.yml"
     redirects:
       - source: /old
         destination: /new
     ```
   </Accordion>
-  <Accordion title='Page "X" was removed. The previously published URL "/old" will return 404 without a redirect.'>
-    A published page no longer exists in the navigation. Add a redirect to another relevant page to avoid breaking incoming links:
+  <Accordion title='Page "X" was removed. The previously [published](/learn/docs/preview-publish/publishing-your-docs) URL "/old" will return 404 without a redirect.'>
+    A published page no longer exists in the [navigation](/learn/docs/configuration/navigation). Add a [redirect](/learn/docs/configuration/site-level-settings#redirects-configuration) to another relevant page to avoid breaking incoming links:
 
     ```yaml title="docs.yml"
     redirects:
@@ -36,10 +36,10 @@ Errors below are surfaced by `fern check` and `fern generate --docs`.
     ```
   </Accordion>
   <Accordion title='Redirect from "/path" to "/path" creates an infinite loop (source equals destination).'>
-    A redirect's `source` and `destination` are the same path. Remove the redirect or point the `destination` at a different URL.
+    A [redirect](/learn/docs/configuration/site-level-settings#redirects-configuration)'s `source` and `destination` are the same path. Remove the redirect or point the `destination` at a different URL.
   </Accordion>
   <Accordion title="Circular redirect chain detected: /a → /b → /a">
-    Two or more redirects form a cycle. Update the chain so each `source` eventually resolves to a single final `destination`.
+    Two or more [redirects](/learn/docs/configuration/site-level-settings#redirects-configuration) form a cycle. Update the chain so each `source` eventually resolves to a single final `destination`.
   </Accordion>
 </AccordionGroup>