From cfb64142ddefba1a6c596c145b047dacbc9f885a Mon Sep 17 00:00:00 2001
From: Jonas Smedegaard <dr@jones.dk>
Date: Mon, 26 May 2025 22:18:44 +0200
Subject: clarify Quarto import plugin constraints, thanks to Bernelle

---
 _pandoc.qmd | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to '_pandoc.qmd')

diff --git a/_pandoc.qmd b/_pandoc.qmd
index 0d3c911..74dfea2 100644
--- a/_pandoc.qmd
+++ b/_pandoc.qmd
@@ -194,11 +194,11 @@ with the most commonly used Reader and Writer components.
 This is exacerbated when using wrapper tools
 since their extensions are likely tailored to those same
 most commonly used Reader and Writer components.
-The Quarto framework, specifically,
-allows using any Reader same as Pandoc itself,
-but only when using default Reader --
-a custom derivative of the Pandoc default Markdown Reader --
-do you benefit from Quarto-specific macro expansions.
+The Quarto framework, like Pandoc,
+allows using any Reader.
+However, Quarto-specific macro expansions
+are only available when using the default Reader --
+a custom derivative of the Pandoc default Markdown Reader.
 
 Despite the Reader API being specifically tailored
 for implementing a custom source format parser,
-- 
cgit v1.2.3

