diff --git a/docs/guides/tagger.rst b/docs/guides/tagger.rst
index ef4cc435e..29bba2d89 100644
--- a/docs/guides/tagger.rst
+++ b/docs/guides/tagger.rst
@@ -262,7 +262,7 @@ If you think beets is ignoring an album that's listed in MusicBrainz, please
 I Hope That Makes Sense
 -----------------------
 
-I haven't made the process clear, please `drop me an email`_ and I'll try to
+If I haven't made the process clear, please `drop me an email`_ and I'll try to
 improve this guide.
 
 .. _drop me an email: mailto:adrian@radbox.org
diff --git a/docs/plugins/inline.rst b/docs/plugins/inline.rst
index fddd2c974..1a7adebe4 100644
--- a/docs/plugins/inline.rst
+++ b/docs/plugins/inline.rst
@@ -3,7 +3,7 @@ Inline Plugin
 
 The ``inline`` plugin lets you use Python to customize your path formats. Using
 it, you can define template fields in your beets configuration file and refer
-to them from your template strings in the ``[paths]`` section (see
+to them from your template strings in the ``paths:`` section (see
 :doc:`/reference/config/`).
 
 To use inline field definitions, first enable the plugin by putting ``inline``
diff --git a/docs/plugins/zero.rst b/docs/plugins/zero.rst
index 19ce28d09..8704d3d8e 100644
--- a/docs/plugins/zero.rst
+++ b/docs/plugins/zero.rst
@@ -6,12 +6,12 @@ can be nulled unconditionally or conditioned on a pattern match. For example,
 the plugin can strip useless comments like "ripped by MyGreatRipper." This
 plugin only affects files' tags; the beets database is unchanged.
 
-To use plugin, enable it by including ``zero`` into ``plugins`` line of your
-configuration file. To configure the plugin, use a ``zero:`` section in your
-configuration file. Set ``fields`` to the (whitespace-separated) list of fields
-to change. You can get the list of available fields by running ``beet fields``.
-To conditionally filter a field, use ``field: [regexp, regexp]`` to specify
-regular expressions.
+To use the plugin, enable it by including ``zero`` in the ``plugins`` line of
+your configuration file. To configure the plugin, use a ``zero:`` section in
+your configuration file. Set ``fields`` to the (whitespace-separated) list of
+fields to change. You can get the list of available fields by running ``beet
+fields``.  To conditionally filter a field, use ``field: [regexp, regexp]`` to
+specify regular expressions.
 
 For example::
 
@@ -20,7 +20,7 @@ For example::
         comments: [EAC, LAME, from.+collection, 'ripped by']
         genre: [rnb, 'power metal']
 
-If custom pattern is not defined for a given field, the field will be nulled
+If a custom pattern is not defined for a given field, the field will be nulled
 unconditionally.
 
 Note that the plugin currently does not zero fields when importing "as-is".
diff --git a/docs/reference/cli.rst b/docs/reference/cli.rst
index cf99b6351..4908b10b1 100644
--- a/docs/reference/cli.rst
+++ b/docs/reference/cli.rst
@@ -59,7 +59,7 @@ right now; this is something we need to work on. Read the
 * During a long tagging import, it can be useful to keep track of albums
   that weren't tagged successfully---either because they're not in the
   MusicBrainz database or because something's wrong with the files. Use the
-  ``-l`` option to specify a filename to log every time you skip and album
+  ``-l`` option to specify a filename to log every time you skip an album
   or import it "as-is" or an album gets skipped as a duplicate.
 
 * Relatedly, the ``-q`` (quiet) option can help with large imports by
@@ -86,7 +86,7 @@ right now; this is something we need to work on. Read the
   ``incremental`` configuration option.
 
 * By default, beets will proceed without asking if it finds a very close
-  metadata match. To disable this and have the importer as you every time,
+  metadata match. To disable this and have the importer ask you every time,
   use the ``-t`` (for *timid*) option.
 
 * The importer typically works in a whole-album-at-a-time mode. If you