Fixes for leftover v1.8 documentation issues (#1946)

* fix quarto-cli/issues/10084

* fix quarto-dev/quarto-cli/issues/10565

* fix for quarto-cli/issues/13162

* fix for quarto-cli/issues/13295

Author: cscheid

docs/authoring/includes.qmd

@@ -104,8 +104,6 @@ A couple of important things to remember when using computational includes:
 
 2)  Computational includes work only in `.qmd` files (they don't work in `.ipynb` notebook files)
 
-Note that you can't use  the `include` shortcode within a computational code block itself - as the example above shows, the executable code block needs to be inside the included document.
-
 ```{=html}
 <style type="text/css">
 code span.in {

docs/authoring/tables.qmd

@@ -773,6 +773,16 @@ Note that grid tables are quite awkward to write with a plain text editor (becau
 -   Quarto [Visual Editor](/docs/visual-editor/content.qmd#editing-tables)
 -   Tables Generator's [Plain Text mode](https://www.tablesgenerator.com/text_tables) with `Use reStructuredText syntax` enabled
 
+::: callout-warning
+
+## Shortcodes are not supported
+
+In Quarto, shortcodes are processed internally by transforming the Markdown text ahead of Pandoc.
+Unfortunately, it's not possible to do this transformation in a way that preserves the grid table structure.
+As a result, shortcodes are not supported inside grid tables. Consider using [list tables](#list-tables) instead.
+
+:::
+
 ## HTML Tables
 
 Quarto can process HTML tables in `html` `RawBlock` nodes (_i.e._, `{=html}`) and convert them to Markdown tables, regardless of the output format (intentionally including non-HTML formats).

docs/extensions/distributing.qmd

@@ -83,6 +83,27 @@ Here are all of the fields that can be specified in the `_extension.yml` file:
 `formats`
 
 :   A record containing the key value pairs of output formats and the metadata associated with that output format.
+
+`project`
+
+:   Information about a [custom Quarto project type](./project-types.qmd).
+
+`revealjs-plugins`
+
+:   Information about a [RevealJS plugin](./revealjs.qmd).
+
+`metadata`
+
+:   [Metadata](./metadata.qmd) to be merged into the Quarto project using the extension.
+
+`brand`
+
+:   Information about a [brand extension](./brand.qmd).
+
+`engine`
+
+:   Information about a [custom engine](./engine.qmd).
+
 :::
 
 :::{.callout-note}

docs/extensions/filters.qmd

@@ -27,28 +27,28 @@ You can write Pandoc filters using Lua (via Pandoc's built-in Lua interpreter) o
 
 ## Activating Filters
 
-If you've developed a filter and want to use it within a document you need to add it to the list of `filters` for the document. For example, here we arrange for the [spellcheck](https://github.com/pandoc/lua-filters/tree/master/spellcheck) filter to run:
+If you've developed a filter and want to use it within a document you need to add it to the list of `filters` for the document. For example, here we arrange for the [lilypond](https://github.com/pandoc/lua-filters/tree/master/lilypond) music-engraving filter to run:
 
 ``` yaml
 ---
 filters:
-  - spellcheck.lua
+  - lilypond.lua
 ---
 ```
 
-By default, user filters are run before Quarto's built-in filters. For some filters you'll want to modify this behavior. For example, here we arrange to run `spellcheck` before Quarto's filters and `fontawesome` after:
+By default, user filters are run before Quarto's built-in filters. For some filters you'll want to modify this behavior. For example, here we arrange to run `lilypond` before Quarto's filters and `fontawesome` after:
 
 ``` yaml
 filters:
-  - spellcheck.lua
+  - lilypond.lua
   - quarto
   - fontawesome
 ```
 
 Beyond a running filters before or after Quarto's filters, you can also
 precisely target the location in the AST processing. Read more in [Targeting of AST Processing Phases](/docs/advanced/quarto-ast.qmd#targeting-of-ast-processing-phases).
 
-You'll notice that one of the extensions (`spellcheck.lua`) has a file extension and the other (`fontawesome`) does not. This difference stems from how the extensions are distributed: an extension distributed as a plain Lua file uses `.lua` whereas a filter distributed as a [Quarto Extension](index.qmd) does not. The next section explores how to create filters as extensions.
+You'll notice that one of the extensions (`lilypond.lua`) has a file extension and the other (`fontawesome`) does not. This difference stems from how the extensions are distributed: an extension distributed as a plain Lua file uses `.lua` whereas a filter distributed as a [Quarto Extension](index.qmd) does not. The next section explores how to create filters as extensions.
 
 
 ## Filter Extensions