Minor documentation fixes (#907)

Author: chrisrink10

docs/compiler.rst

@@ -13,7 +13,7 @@ Since the compiler cannot reason about larger units of code, it cannot make infe
 
 There are three steps to the Basilisp compiler: analysis, generation, and optimization.
 After a Basilisp form is read in by the :ref:`reader`, it is passed off to the analyzer to produce an abstract syntax tree.
-The generator reads the AST and produces Python code (_not_ bytecode) using Python's builtin `ast <https://docs.python.org/3/library/ast.html>`_ module.
+The generator reads the AST and produces Python code (*not* bytecode) using Python's builtin `ast <https://docs.python.org/3/library/ast.html>`_ module.
 Afterwards, the compiler passes the generated AST through a quick optimization phase to remove redundant branches and other artifacts of code generation.
 From there, the compiler injects the compiled code into a dynamically-generated Python module which is associated with a Basilisp Namespace and executes the code so the generated objects are available.
 

docs/contributing.rst

@@ -60,7 +60,7 @@ To prepare your `poetry` environment, you need to install dependencies:
    poetry install
 
 Afterwards, you can open a new Poetry shell to start up the REPL for development.
-The ``make repl`` target _may_ be sufficient for local development, though developers working on the Basilisp compiler or standard library are encouraged to enable a more verbose set of configurations for detecting issues during development.
+The ``make repl`` target *may* be sufficient for local development, though developers working on the Basilisp compiler or standard library are encouraged to enable a more verbose set of configurations for detecting issues during development.
 The command below enables the highest level of logging and disables namespace caching, both of which can help reveal otherwise hidden issues during development.
 
 .. code-block:: bash

docs/reader.rst

@@ -233,7 +233,7 @@ nil
     basilisp.user=> (python/type nil)
     <class 'NoneType'>
 
-The special value ``nil`` correspond's to Python's ``None``.
+The special value ``nil`` corresponds to Python's ``None``.
 
 .. _whitespace:
 
@@ -327,7 +327,7 @@ Maps
     {1 "2" :three 3}
 
 Maps are denoted with the ``{}`` characters.
-Sets may contain 0 or more heterogenous key-value pairs.
+Maps may contain 0 or more heterogenous key-value pairs.
 Basilisp maps are modeled after Clojure's persistent map implementation.
 
 .. _sets:
@@ -354,7 +354,7 @@ Line Comments
 Line comments are specified with the ``;`` character.
 All of the text to the end of the line are ignored.
 
-For a convenience in writing shell scripts with Basilisp, the standard \*NIX `shebang <https://en.wikipedia.org/wiki/Shebang_(Unix)>` (``#!``) is also treated as a single-line comment.
+For a convenience in writing shell scripts with Basilisp, the standard \*NIX `shebang <https://en.wikipedia.org/wiki/Shebang_(Unix)>`_ (``#!``) is also treated as a single-line comment.
 
 .. _metadata:
 
@@ -390,7 +390,7 @@ Reader macros are always dispatched using the ``#`` character.
 
 * ``#'form`` is rewritten as ``(var form)``.
 * ``#_form`` causes the reader to completely ignore ``form``.
-* ``#!form`` is treated as a single-line comment (like ``;form``) as a convenience to support `shebangs <https://en.wikipedia.org/wiki/Shebang_(Unix)>` at the top of Basilisp scripts.
+* ``#!form`` is treated as a single-line comment (like ``;form``) as a convenience to support `shebangs <https://en.wikipedia.org/wiki/Shebang_(Unix)>`_ at the top of Basilisp scripts.
 * ``#"str"`` causes the reader to interpret ``"str"`` as a regex and return a Python `re.pattern <https://docs.python.org/3/library/re.html>`_.
 * ``#(...)`` causes the reader to interpret the contents of the list as an anonymous function. Anonymous functions specified in this way can name arguments using ``%1``, ``%2``, etc. and rest args as ``%&``. For anonymous functions with only one argument, ``%`` can be used in place of ``%1``.
 

docs/specialforms.rst

@@ -370,7 +370,8 @@ Primary Special Forms
       The Basilisp compiler makes attempts to verify whether a ``set!`` is legal at compile time, but there are cases which must be deferred to runtime due to the dynamic nature of the language.
       In particular, due to the non-lexical nature of dynamic Var bindings, it can be difficult to establish if a Var is thread-bound when it is ``set!``, so this check is deferred to runtime.
 
-.. lpy:specialform:: (throw exc cause?)
+.. lpy:specialform:: (throw exc)
+                     (throw exc cause)
 
    Throw the exception named by ``exc``.
    The semantics of ``throw`` are identical to those of Python's `raise <https://docs.python.org/3/reference/simple_stmts.html#the-raise-statement>`_ statement with exception.