From 7cee2a2158ec6dac8ced32e408352e4f2ef61572 Mon Sep 17 00:00:00 2001
From: Paul Sachs <11449728+paul-sachs@users.noreply.github.com>
Date: Thu, 18 Sep 2025 09:21:41 -0400
Subject: [PATCH] Clarify remote Markdown support in Astro

Only built in loaders (file and glob) support built in markdown parsing. Since content collections now allow defining remote collections, this link is misleading.
---
 src/content/docs/en/guides/markdown-content.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/en/guides/markdown-content.mdx b/src/content/docs/en/guides/markdown-content.mdx
index 4fc60b82e597d..ecf64b8c7153f 100644
--- a/src/content/docs/en/guides/markdown-content.mdx
+++ b/src/content/docs/en/guides/markdown-content.mdx
@@ -397,7 +397,7 @@ When using the frontmatter `layout` property, you must include the `<meta charse
 
 ## Fetching Remote Markdown
 
-Astro does not include built-in support for remote Markdown outside of [content collections](/en/guides/content-collections/).
+Astro does not include built-in support for remote Markdown.
 
 To fetch remote Markdown directly and render it to HTML, you will need to install and configure your own Markdown parser from NPM. This will not inherit from any of Astro's built-in Markdown settings that you have configured.