quarto-dev · github-actions · Aug 6, 2025
diff --git a/docs/authoring/language.qmd b/docs/authoring/language.qmd
@@ -6,7 +6,7 @@ title: "Document Language"
 
 Document language plays a role in Pandoc's processing of most formats, and controls hyphenation in PDF output when using LaTeX (through [`babel`](https://ctan.org/pkg/babel) and [`polyglossia`](https://ctan.org/pkg/polyglossia)) or ConTeXt.
 
-Additonally, Quarto, Pandoc, and LaTeX will sometimes generate textual output that requires localization. For example, "Figure" or "List of Figures" for cross references, callout captions like "Note" or "Warning", or the "Code" caption for folded code chunks.
+Additionally, Quarto, Pandoc, and LaTeX will sometimes generate textual output that requires localization. For example, "Figure" or "List of Figures" for cross references, callout captions like "Note" or "Warning", or the "Code" caption for folded code chunks.
 
 ## `lang` Option
 

diff --git a/docs/authoring/title-blocks.qmd b/docs/authoring/title-blocks.qmd
@@ -38,7 +38,7 @@ title-block-banner: true
 
 will render a title block like:
 
-![](images/document-title-block-banner.png){.border fig-alt="Title block with title and description against a blue background up top, and below a section with author, affilitation, and date published."}
+![](images/document-title-block-banner.png){.border fig-alt="Title block with title and description against a blue background up top, and below a section with author, affiliation, and date published."}
 
 ### Custom Backgrounds
 
@@ -52,7 +52,7 @@ title-block-banner: images/banner.jpeg
 
 which would render a banner title block like:
 
-![](images/document-title-block-banner-custom.png){.border fig-alt="Title block with title and description against an image background up top, and below a section with author, affilitation, and date published."}
+![](images/document-title-block-banner-custom.png){.border fig-alt="Title block with title and description against an image background up top, and below a section with author, affiliation, and date published."}
 
 When you provide an explicit background color or image, Quarto assumes that the color of the background will contrast with the body background color and automatically uses the body background color as the text color over the banner.
 

diff --git a/docs/computations/julia.qmd b/docs/computations/julia.qmd
@@ -490,7 +490,7 @@ engine via integrations with the
 [RCall](https://github.com/JuliaInterop/RCall.jl) and
 [PythonCall](https://github.com/JuliaPy/PythonCall.jl) packages respectively.
 Using this feature requires the notebook author to explicitly `import` those
-packages into their notebooks in a `{{julia}}` cell afterwhich they can use
+packages into their notebooks in a `{{julia}}` cell after which they can use
 `{{r}}` and `{{python}}` cells.
 
 ````markdown

diff --git a/docs/dashboards/_examples/gapminder-notebook.ipynb b/docs/dashboards/_examples/gapminder-notebook.ipynb
diff --git a/docs/download/changelog/1.1/_changelog.md b/docs/download/changelog/1.1/_changelog.md
@@ -152,7 +152,7 @@
 - Development version cleans old vendor directory on success (https://github.com/quarto-dev/quarto-cli/pull/1863#issuecomment-1215452392)
 - properly support YAML scalar syntax (#1838)
 - Add support for Giscus lazy loading (use `loading: lazy` #1357)
-- Properly handle duplicated affilations in author metadata (#1286)
+- Properly handle duplicated affiliations in author metadata (#1286)
 - Display image path when an error occurs reading PNG metadata
 - `quarto run *.ts` preserves stdout and stderr (#1954)
 - Lua filters: quarto.utils.dump does not loop on circular structures (#1958)
diff --git a/docs/download/changelog/1.3/_changelog.md b/docs/download/changelog/1.3/_changelog.md
@@ -198,7 +198,7 @@
 - Don't discard the first chapter header when a chapter title is declared using YAML.
 - Support for rendering to Asciidoc
 - Support for rendering to LaTeX
-- Properly support localized appendex name in book website navigation ([#4578](https://github.com/quarto-dev/quarto-cli/issues/4578))
+- Properly support localized appendix name in book website navigation ([#4578](https://github.com/quarto-dev/quarto-cli/issues/4578))
 - Don't emit duplicate bibliography heading when LaTeX/PDF books are rendering using `natbib` or `biblatex` ([#2770](https://github.com/quarto-dev/quarto-cli/issues/2770))
 
 ## Preview

diff --git a/docs/extensions/lua.qmd b/docs/extensions/lua.qmd
@@ -151,7 +151,7 @@ You can keep these calls in your filter since they won't produce output unless `
 
 ## Native Format {#native-format}
 
-A great tool for understanding the behavior of a Lua filter or shortcode in more depth is to target the `native` format (as opposed to `html`, `pdf`, etc.). The `native` format will show you the raw contents of the Pandoc AST. For example, here's a simple markdown document alongside it's `native` output:
+A great tool for understanding the behavior of a Lua filter or shortcode in more depth is to target the `native` format (as opposed to `html`, `pdf`, etc.). The `native` format will show you the raw contents of the Pandoc AST. For example, here's a simple markdown document alongside its `native` output:
 
 ::: {layout-ncol="2"}
 <div>

diff --git a/docs/get-started/computations/positron.qmd b/docs/get-started/computations/positron.qmd
@@ -288,7 +288,7 @@ You can see examples of other options that control code appearance in the HTML f
 Figures produced by code cells are automatically included in the rendered output.
 Code cell options provide additional control over how figures are displayed. 
 
-For example, update the code cell for the scatter plot by adding a caption with `fig-cap`, and improve accessability by adding [alternative text](https://medium.com/nightingale/writing-alt-text-for-data-visualization-2a218ef43f81) with `fig-alt`:
+For example, update the code cell for the scatter plot by adding a caption with `fig-cap`, and improve accessibility by adding [alternative text](https://medium.com/nightingale/writing-alt-text-for-data-visualization-2a218ef43f81) with `fig-alt`:
 
 ```yml
 #| fig-cap: City and highway mileage for 38 popular models of cars.

diff --git a/docs/interactive/ojs/shiny.qmd b/docs/interactive/ojs/shiny.qmd
@@ -86,7 +86,7 @@ Here are some examples that demonstrate various ways to use OJS with Shiny:
 |----------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------|
 | [K-Means](https://jjallaire.shinyapps.io/kmeans-shiny-ojs/)    | [Code](https://git.io/J0kPK) | Simple example of binding OJS inputs to Shiny inputs and shiny reactives to OJS plots.                             |
 | [Binning](https://jjallaire.shinyapps.io/binning-shiny-ojs/)   | [Code](https://git.io/J0kPu) | Demonstrates fast binning of a medium sized dataset (32mb) on the server.                                          |
-| [Data Binding](https://jjallaire.shinyapps.io/data-shiny-ojs/) | [Code](https://git.io/J0kPl) | Demonstrates importing a notebook from <https://observablehq.com> and binding it's data field to a Shiny reactive. |
+| [Data Binding](https://jjallaire.shinyapps.io/data-shiny-ojs/) | [Code](https://git.io/J0kPl) | Demonstrates importing a notebook from <https://observablehq.com> and binding its data field to a Shiny reactive.  |
 
 ## Bindings
 

diff --git a/docs/projects/scripts.qmd b/docs/projects/scripts.qmd
@@ -27,7 +27,7 @@ Available script interpreters for `quarto run` include:
 
 Using TypeScript or Lua enables you to create scripts with no additional installation requirements. On the other hand, if your project is already using Python or R then scripts in those languages might be more convenient.
 
-If you are using TypeScript, please be sure to consult the section below on [Deno Scripts](#deno-scripts) for additonal details on the Deno standard library and importing external scripts.
+If you are using TypeScript, please be sure to consult the section below on [Deno Scripts](#deno-scripts) for additional details on the Deno standard library and importing external scripts.
 
 ## Pre and Post Render
 
@@ -170,4 +170,4 @@ const { readLines } = await multiImport(
   "stdlib/io", // Quarto 1.6 syntax
   "https://deno.land/std/io/mod.ts", // Quarto 1.5 syntax
 );
-```
+```
diff --git a/docs/reference/formats/dashboard.qmd b/docs/reference/formats/dashboard.qmd
@@ -124,7 +124,7 @@ Card options enable you to specify a title and various layout behaviors:
 | `expandable` | Make card content expandable (default: `true`)                                                                                                                |
 | `width`      | Percentage or absolute pixel width (default distributes space evenly across elements in a row)                                                                |
 | `height`     | Percentage or absolute pixel height (default distributes space evenly across elements in a column)                                                            |
-| `fill`       | Whether the card should fill it's container or 'flow', matching the height of its content. (Quarto determines the default value based upon the card contents) |
+| `fill`       | Whether the card should fill its container or 'flow', matching the height of its content. (Quarto determines the default value based upon the card contents)  |
 
 For example:
 

diff --git a/docs/tools/neovim.qmd b/docs/tools/neovim.qmd
@@ -63,7 +63,7 @@ Use <kbd>Tab</kbd> and <kbd>Shift+Tab</kbd> to iterate through the suggestions.
 ![](./images/neovim-code-completion.png)
 
 ::: {.callout-note}
-The otter in the completion list means that the completion plugin [cmp](https://github.com/hrsh7th/nvim-cmp) got it's completion suggestions from the [otter.nvim](https://github.com/jmbuhr/otter.nvim) plugin, which keeps track of the code in your Quarto document behind the scenes by writing only the code parts to another (an otter) document.
+The otter in the completion list means that the completion plugin [cmp](https://github.com/hrsh7th/nvim-cmp) got its completion suggestions from the [otter.nvim](https://github.com/jmbuhr/otter.nvim) plugin, which keeps track of the code in your Quarto document behind the scenes by writing only the code parts to another (an otter) document.
 :::
 
 ## Code Snippets
@@ -92,7 +92,7 @@ For the full range of options, refer to the documentation of vim/neovim and of t
 - Press <kbd>space l o</kbd> to toggle a section overview
 - Navigate to the next code chunk with <kbd>[c</kbd> or the previous one with <kbd>]c</kbd>
 - Delete/Change/Yank the code of a chunk with <kbd>dio</kbd>/<kbd>cio</kbd>/<kbd>yio</kbd>
-- Delete/Change/Yank a whole code chunk with it's delimiters with <kbd>dao</kbd>/<kbd>cao</kbd>/<kbd>yao</kbd>
+- Delete/Change/Yank a whole code chunk with its delimiters with <kbd>dao</kbd>/<kbd>cao</kbd>/<kbd>yao</kbd>
 
 Take a look at the files of the kickstarter configuration for more inspiration.
 

diff --git a/docs/websites/website-navigation.qmd b/docs/websites/website-navigation.qmd
@@ -147,7 +147,7 @@ website:
         contents:
           - raw-code.qmd
           - custom-theme.qmd
-      - acknowlegment.qmd
+      - acknowledgment.qmd
 ```
 
 There are two styles of side navigation available: "docked" which shows the navigation in a sidebar with a distinct background color, and "floating" which places it closer to the main body text. Here's what the "docked" and "floating" styles look like (respectively):