   main responsibilities:
 
     * It defines a plug pipeline responsible for handling
-      upcoming requests and dispatch those requests to
-      controllers and other plugs
+      upcoming requests and dispatching those requests to
+      controllers and other plugs.
 
     * It hosts configuration for the router and related
-      entities (like plugs)
+      entities (like plugs).
 
     * It provides a wrapper for starting and stopping the
-      router in a specific web server
+      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
+  that dispatch to specific controllers and actions. Those
   macros are named after HTTP verbs. For example:
 
       defmodule MyApp.Router do


  Phoenix configuration is split in two categories. Compile-time
  configuration means the configuration is read during compilation
  and changed it at runtime has no effect. Most of the compile-time
  configuration is related to pipelines and plugs.

  On the other hand, runtime configuration is accessed during or

        resources "/users", UserController, except: [:destroy]
      end

  Finally, Phoenix ships with a `mix phoenix.routes` task that nicely
  formats all routes in a given router. We can use it to verify all
  routes included in the router above:

