From 1c79575c7c81fa129c403e4ef7c71b8b2eb32e21 Mon Sep 17 00:00:00 2001 From: "Luke W. Johnston" Date: Tue, 25 Feb 2025 11:18:25 +0100 Subject: [PATCH] docs: minor edits for clarification of text --- docs/authoring/contents.qmd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/authoring/contents.qmd b/docs/authoring/contents.qmd index bee2c40456..9140e012fa 100644 --- a/docs/authoring/contents.qmd +++ b/docs/authoring/contents.qmd @@ -43,10 +43,10 @@ The code above produces the following output: ## Why `{{{< contents >}}}` increases your freedom in defining the document the most comfortable way you can. -It can simply because you want to write the code in the middle of a different explanation, but you want to result to appear elsewhere. +It can simply be because you want to write the code in the middle of a different explanation, but you want the result to appear elsewhere. -One particularly important reason is that Jupyter notebooks do not allow code cells to "nest" inside markdown, and many of Quarto's features -are defined in terms of fenced divs, Markdown that looks like this: +One particularly important reason is that Jupyter notebooks do not allow code cells to "nest" inside Markdown. +Many of Quarto's features are defined in terms of fenced divs, with Markdown that looks like this: ````markdown ::: {#div-id .class1 .class2 key1="value1"}