diff --git a/_docs/fields.md b/_docs/fields.md
index 73c3aeeb6..3a3bfa55a 100644
--- a/_docs/fields.md
+++ b/_docs/fields.md
@@ -3561,8 +3561,8 @@ assume that clicking the link didn't do anything, and the app is
 broken.
 
 There are three other special commands that you can use in a list of
-variables in a `review` item: `set`, `undefine`, and `invalidate`.
-The following example illustrates `set`:
+variables in a `review` item: `sets`, `undefine`, and `invalidate`.
+The following example illustrates `sets`:
 
 {% include side-by-side.html demo="review-8" %}
 
@@ -3578,7 +3578,7 @@ app.  However, if the user edits the underlying attributes of the
 address, you need to "reset" the geocoding in order to get it to run
 again.
 
-In the above interview, the `set` command sets `address.geocoded` to
+In the above interview, the `sets` command sets `address.geocoded` to
 `False`, which means that when the `address.county` is recomputed, and
 the [`.geocode()`] method is run again by the `code` block, then the
 [`.geocode()`] method will actually geocode the new address.
@@ -3637,7 +3637,7 @@ review:
 
 This enables you to use tables in your `review` screen.  Ordinarily,
 tables are always undefined (so that their contents always reflect the
-current state of the list, so a `review` screen would never display them.
+current state of the list), so a `review` screen would never display them.
 
 ### <a name="resume button label"></a>Customizing the Resume button
 
diff --git a/_docs/initial.md b/_docs/initial.md
index dec699618..a4f522b50 100644
--- a/_docs/initial.md
+++ b/_docs/initial.md
@@ -1462,7 +1462,7 @@ though their `amount` was zero, and then the other items are listed in
 
 # <a name="sections"></a>Defining the sections for the navigation bar
 
-You can add use the [`navigation bar`] feature or the
+You can use the [`navigation`] bar feature or the
 [`nav.show_sections()`] function to show your users the "sections" of
 the interview and what the current section of the interview is.
 
@@ -2794,7 +2794,6 @@ contained:
 [Python names]: {{ site.baseurl }}/docs/fields.html#variable names
 [`event`]: {{ site.baseurl }}/docs/fields.html#event
 [`review`]: {{ site.baseurl }}/docs/fields.html#review
-[`navigation bar`]: #navigation bar
 [`navigation bar html`]: #navigation bar html
 [`nav.set_sections()`]: {{ site.baseurl }}/docs/functions.html#DANav.set_sections
 [action]: {{ site.baseurl }}/docs/functions.html#actions
diff --git a/_docs/modifiers.md b/_docs/modifiers.md
index b0d546906..346b19cb3 100644
--- a/_docs/modifiers.md
+++ b/_docs/modifiers.md
@@ -939,7 +939,7 @@ the ones that are later in the file first, unless an [`order` initial
 block] or a [`supersedes` modifier] alters that order.
 
 Sometimes, however, a block that **docassemble** tries to use to
-define a variable is one that you don't **docassemble** to even
+define a variable is one that you don't want **docassemble** to even
 consider when looking for a way to define a variable.
 
 This is particularly likely to happen when you have code that changes