         plug :token_authentication
       end
 
-  Where `plug :super` will invoke the previously defined pipeline.
-  In general though, it is preferred to define new pipelines then
-  modify existing ones.
+  Where `plug :super` will invoke the existing pligs in the api
+  pipeline. In general though, it is preferred to define new pipelines
+  then modify existing ones.
 
   ## Router configuration
 

  A router is the heart of a Phoenix application. It has three
  main responsibilities:

    * It provides routes and named route conveniences for
      routing requests to controllers

    * It defines a plug pipelines responsible for handling
      upcoming requests

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

    * It provides a wrapper for starting and stopping a
      web server specific to this router

  We will explore those responsibilities next.



  ### :browser pipeline

  The following plugs are in the browser pipeline:

    * `:fetch_session` - calls the `Plug.Conn.fetch_session/2` that
      effectively fetches the session and makes it available in the
      connection

  ### :api pipeline

  Currently there are no plugs in the `:api` pipeline.

  ### Customizing pipelines

