   doctest](http://docs.python.org/2/library/doctest.html).
 
   In a nutshell, it allows us to generate tests from the code
-  examples existing in module/function/macro's documentation.
-  In order to do that, one needs to invoke `doctest/1` macro
+  examples existing in a module/function/macro's documentation.
+  In order to do that, one needs to invoke the `doctest/1` macro
   from their test case and write their examples according
   to some guidelines.
 
   The syntax for examples is as follows. Every new test starts
-  on a new line, with an "iex>" prefix. Multiline expressions
+  on a new line, with an `iex>` prefix. Multiline expressions
   can be employed if the following lines start with either
-  "...>" (recommended) or "iex>" prefix.
-
-  The expected result should start at the next line after "iex>"
-  or "...>" line(s) and is terminated either by a newline, new
-  "iex>" prefix or end of the string literal.
+  `...>` (recommended) or `iex>` prefix.
+
+  The expected result should start at the next line after `iex>`
+  or `...>` line(s) and is terminated either by a newline, new
+  `iex>` prefix or end of the string literal.
 
   ## Examples
 

  * `:except` — generate tests for all functions except those listed
                (list of `{function, arity}` tuples)

  * `:only`   — generate tests only forfunctions listed
                (list of `{function, arity}` tuples)

  * `:import` — when true, one can test a function defined in the module
                without referring to the module name. However, this is not
                feasible when there is a clash with a number module like
                Kernel. In these cases, `import` should be set to `false`
                and a full `M.f` construct should be used.


      iex> a + 1
      2

  If you want to keep any two tests separate,
  add an empty line between them:

      iex> a = 1
