 
   Overall, an endpoint has three responsibilities:
 
-    * It provides a wrapper for starting and stopping the
-      endpoint as part of a supervision tree.
-
-    * To define an initial plug pipeline where requests
-      are sent to.
-
-    * To host web specific configuration for your
+    * to provide a wrapper for starting and stopping the
+      endpoint as part of a supervision tree;
+
+    * to define an initial plug pipeline where requests
+      are sent through;
+
+    * to host web specific configuration for your
       application.
 
   ## Endpoints
 
   An endpoint is simply a module defined with the help
-  of Phoenix.Endpoint. If you have used the phoenix.new
+  of `Phoenix.Endpoint`. If you have used the `mix phoenix.new`
   generator, an endpoint was automatically generated as
   part of your application:
 

  and changing it at runtime has no effect. The compile-time
  configuration is mostly related to error handling.

  On the other hand, runtime configuration is accessed during or
  after your application is started and can be read through the
  `config/2` function:

      YourApp.Endpoint.config(:port)
      YourApp.Endpoint.config(:some_config, :default_value)

  ### Compile-time

    * `:debug_errors` - when true, uses `Plug.Debugger` functionality for
      debugging failures in the application. Recomended to be set to true
      only in development as it allows listing of the application source
      code during debugging. Defaults to false.

    * `:render_errors` - a module representing a view to render templates
      whenever there is a failure in the application. For example, if the

  ## Endpoint API

  In the previous section, we have used the `config/2` function which is
  automatically generated in your endpoint. Here is a summary of all the
  functions that are automatically defined in your endpoint.

  #### Paths and URLs

