diff --git a/docs/extensions/_formats-common.qmd b/docs/extensions/_formats-common.qmd
index 130194fbb..67b04f370 100644
--- a/docs/extensions/_formats-common.qmd
+++ b/docs/extensions/_formats-common.qmd
@@ -12,7 +12,7 @@ If you have a GitHub repository containing the files enumerated above in the `{{
 quarto use template {{< meta example-org >}}/{{< meta example-format >}}
 ```
 
-This is often the preferred way to get started with a format as it provides the user with a working document right out of the box. It's also possible to install *only* the format if you working with an existing project:
+This is often the preferred way to get started with a format as it provides the user with a working document right out of the box. It's also possible to install *only* the format if you are working with an existing project:
 
 ``` {.bash filename="Terminal"}
 quarto add {{< meta example-org >}}/{{< meta example-format >}}
@@ -80,6 +80,6 @@ quarto-journals/jss
         └── partials
 ```
 
-This will add the `quarto-ext/fancy-text` extension into the `jss` extension in the `_extensions` folder. By embedding an extension you make it available without creating the potential for conflict with other versions of the extension that uses might already have installed.
+This will add the `quarto-ext/fancy-text` extension into the `jss` extension in the `_extensions` folder. By embedding an extension you make it available without creating the potential for conflict with other versions of the extension that users might already have installed.
 
 [^_formats-common-1]: This is most common in the the case of PDF based formats which have a secondary step of converting the LaTeX produced by Pandoc into a PDF. If there are files that are referenced indirectly by the LaTeX, they will need to be discoverable and should typically be copied into the same directory that contains the LaTeX input.
diff --git a/docs/journals/formats.qmd b/docs/journals/formats.qmd
index 5fb94dbaf..8f29e014e 100644
--- a/docs/journals/formats.qmd
+++ b/docs/journals/formats.qmd
@@ -8,7 +8,7 @@ example-format: acm
 
 ## Overview
 
-This article provide a guide to creating your own custom Journal formats. As a supplement to this guide we also recommend the following learning resources:
+This article provides a guide to creating your own custom Journal formats. As a supplement to this guide we also recommend the following learning resources:
 
 -   The source code for the Journal article formats available from the [quarto-journals](https://github.com/quarto-journals/) GitHub organization.
 
@@ -177,7 +177,7 @@ _extensions/
 
 For the time being we'll ignore all of the files above the `_extensions` directory (those files aren't strictly part of the extension but rather provide documentation and a starter template---we'll describe their usage below).
 
--   The `_extensions` directory contains one or more extension---in this case it contains the `acm` format extension.
+-   The `_extensions` directory contains one or more extensions---in this case it contains the `acm` format extension.
 
 -   The `_extension.yml` file declares the format extension and provides default metadata and options for articles created for the format (we'll do a deep dive into its contents below).