   This is an option determining the prompt displayed to the user
   when awaiting input.
 
-  The value is a keyword list. Two prompt types:
-
-    * `:default_prompt` - used when `Node.alive?` returns `false`
-    * `:alive_prompt`   - used when `Node.alive?` returns `true`
+  The value is a keyword list with two possible keys representing prompt types:
+
+    * `:default_prompt` - used when `Node.alive?/0` returns `false`
+    * `:alive_prompt`   - used when `Node.alive?/0` returns `true`
 
   The following values in the prompt string will be replaced appropriately:
 

  shell. See documentation for the `IO.ANSI` module for the list of
  supported colors and attributes.

  The value is a keyword list. List of supported keys:

    * `:enabled`      - boolean value that allows for switching the coloring on and off
    * `:eval_result`  - color for an expression's resulting value


  ## The .iex.exs file

  When starting, IEx looks for a local `.iex.exs` file (located in the current
  working directory), then a global one (located at `~/.iex.exs`) and loads the
  first one it finds (if any). The code in the loaded `.iex.exs` file is
  evaluated in the shell's context. So, for instance, any modules that are
  loaded or variables that are bound in the `.iex.exs` file will be available in the
  shell after it has booted.

  For example, take the following `.iex.exs` file:

      # Load another ".iex.exs" file
      import_file "~/.iex.exs"

      # Import some module from lib that may not yet have been defined
      import_if_available MyApp.Mod

      # Print something before the shell starts
      IO.puts "hello world"

      # Bind a variable that'll be accessible in the shell
      value = 13

  Running IEx in the directory where the above `.iex.exs` file is located
  results in:

      $ iex
      Erlang 19 [...]

      hello world
      Interactive Elixir - press Ctrl+C to exit (type h() ENTER for help)
