Fix newline and unbalanced inline literals issues

Author: snejus

docs/_templates/autosummary/base.rst

@@ -1,3 +1,3 @@
 {{ fullname | escape | underline}}
 .. currentmodule:: {{ module }}
-.. auto{{ objtype }}:: {{ objname }}
+.. auto{{ objtype }}:: {{ objname }}

docs/_templates/autosummary/module.rst

@@ -8,4 +8,4 @@
 
 {%- endfor %}
 {% endif %}
-{% endblock %}
+{% endblock %}

docs/api/database.rst

@@ -44,4 +44,4 @@ Queries
 
     Query
     FieldQuery
-    AndQuery
+    AndQuery

docs/changelog.rst

@@ -4851,7 +4851,7 @@ below, for a plethora of new features.
 * **Queries can now contain whitespace.** Spaces passed as shell arguments are
   now preserved, so you can use your shell's escaping syntax (quotes or
   backslashes, for instance) to include spaces in queries. For example,
-  typing``beet ls "the knife"`` or ``beet ls the\ knife``. Read more in
+  ``beet ls "the knife"`` or ``beet ls the\ knife``. Read more in
   :doc:`/reference/query`.
 
 * Queries can **match items from the library by directory**. A ``path:`` prefix
@@ -5134,7 +5134,7 @@ issue involves correct ordering of autotagged albums.
 * Fixed a Unicode encoding error when entering special characters into the
   "manual search" prompt.
 
-* Added `` beet version`` command that just shows the current release version.
+* Added ``beet version`` command that just shows the current release version.
 
 .. _upstream bug: https://github.com/quodlibet/mutagen/issues/7
 .. _Bluelet: https://github.com/sampsyo/bluelet
@@ -5343,7 +5343,7 @@ BPD). To "upgrade" an old database, you can use the included ``albumify`` plugin
 * Fixed some bugs with encoding paths on Windows. Also, ``:`` is now replaced
   with ``-`` in path names (instead of ``_``) for readability.
 
-* ``MediaFile``s now have a ``format`` attribute, so you can use ``$format`` in
+* ``MediaFile`` now has a ``format`` attribute, so you can use ``$format`` in
   your library path format strings like ``$artist - $album ($format)`` to get
   directories with names like ``Paul Simon - Graceland (FLAC)``.
 

docs/plugins/limit.rst

@@ -42,17 +42,23 @@ Examples
 
 First 10 tracks
 
-    $ beet ls | head -n 10
-    $ beet lslimit --head 10
-    $ beet ls '<10'
+.. code-block:: sh
+
+   $ beet ls | head -n 10
+   $ beet lslimit --head 10
+   $ beet ls '<10'
 
 Last 10 tracks
 
+.. code-block:: sh
+
     $ beet ls | tail -n 10
     $ beet lslimit --tail 10
 
 100 mostly recently released tracks
 
+.. code-block:: sh
+
     $ beet lslimit --head 100 year- month- day-
     $ beet ls year- month- day- '<100'
     $ beet lslimit --tail 100 year+ month+ day+

docs/plugins/substitute.rst

@@ -21,7 +21,7 @@ replacement string. For example, you might use:
 The replacement can be an expression utilising the matched regex, allowing us
 to create more general rules. Say for example, we want to sort all albums by
 multiple artists into the directory of the first artist. We can thus capture
-everything before the first ``,``, `` &`` or `` and``, and use this capture
+everything before the first ``,``, ``\ &`` or ``\ and``, and use this capture
 group in the output, discarding the rest of the string.
 
 .. code-block:: yaml

docs/reference/cli.rst

@@ -95,7 +95,7 @@ Optional command flags:
   normal autotagger mode would ask for confirmation, the quiet mode
   performs a fallback action that can be configured using the
   ``quiet_fallback`` configuration or ``--quiet-fallback`` CLI option.
-  By default it pessimistically ``skip``s the file.
+  By default it pessimistically skips the file.
   Alternatively, it can be used as is, by configuring ``asis``.
 
 * Speaking of resuming interrupted imports, the tagger will prompt you if it

docs/reference/query.rst

@@ -181,8 +181,8 @@ shell).
 Numeric Range Queries
 ---------------------
 
-For numeric fields, such as year, bitrate, and track, you can query using one-
-or two-sided intervals. That is, you can find music that falls within a
+For numeric fields, such as year, bitrate, and track, you can query using
+one-or two-sided intervals. That is, you can find music that falls within a
 *range* of values. To use ranges, write a query that has two dots (``..``) at
 the beginning, middle, or end of a string of numbers. Dots in the beginning
 let you specify a maximum (e.g., ``..7``); dots at the end mean a minimum