         end
       end
 
-  `Phoenix.Router` imports both `Plug.Conn` and `Phoenix.Controller`
-  functions to help define plugs. In the example above, `fetch_session/2`
+  `Phoenix.Router` imports functions from both `Plug.Conn` and `Phoenix.Controller`
+  to help define plugs. In the example above, `fetch_session/2`
   comes from `Plug.Conn` while `accepts/2` comes from `Phoenix.Controller`.
 
   By default, Phoenix ships with one pipeline, called `:before`,

  main responsibilities:

    * It defines a plug pipeline responsible for handling
      upcoming requests and dispatch those requests to
      controllers and other plugs

    * It hosts configuration for the router and related
      entities (like plugs)

    * It provides a wrapper for starting and stopping the
      router in a specific web server

  We will explore those responsibilities next.

  ## Routing

  The router provides a set of macros for generating routes
  that dispatches to a specific controller and action. Those
  macros are named after HTTP verbs. For example:

      defmodule MyApp.Router do

      user_path  PATCH  /users/:id       UserController.update/2
                 PUT    /users/:id       UserController.update/2

  One can also pass a router explicitly as an argument to the task:

      $ mix phoenix.router MyApp.Router

