       iex(1)> binary_to_atom((fn() -> 1 end).())
       ** (ArgumentError) argument error
 
-  What DocTest will be looking for is a line starting with "** (" and it
-  will parse it accordingly to extract the exception name and the message.
+  What DocTest will be looking for is a line starting with `** (` and it
+  will parse it accordingly to extract the exception name and message.
   At this moment, the exception parser would make the parser treat the next
-  line as a start of a completely new expression (if it is prefixed with iex>)
+  line as a start of a completely new expression (if it is prefixed with `iex>`)
   or a no-op line with documentation. Thus, multiline messages are not
   supported.
 


  The `doctest` macro is going to loop through all functions and
  macros defined in `MyModule`, parsing their documentation in
  search for code examples.

  A very basic example is:


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

  * `:only`   — generate tests only for functions 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 module like
                Kernel. In these cases, `import` should be set to `false`
                and a full `M.f` construct should be used.

