 
     * `broadcast_from(from, topic, event, msg)` - proxy to `Phoenix.Channel.broadcast_from/4`
       using this endpoint's configured pubsub server
-    * `broadcast_from!(from, topic, event, msg)` - proxy to `Phoenix.Channel.broadcast_from!/4`
+    * `broadcast_from!(from, topic, event, msg)` - proxies to `Phoenix.Channel.broadcast_from!/4`
       using this endpoint's configured pubsub server
-    * `broadcast(topic, event, msg)` - proxy to `Phoenix.Channel.broadcast/3`
+    * `broadcast(topic, event, msg)` - proxies to `Phoenix.Channel.broadcast/3`
       using this endpoint's configured pubsub server
-    * `broadcast!(topic, event, msg)` - proxy to `Phoenix.Channel.broadcast!/3`
+    * `broadcast!(topic, event, msg)` - proxies to `Phoenix.Channel.broadcast!/3`
       using this endpoint's configured pubsub server
 
   #### Endpoint configuration

  ## 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
  functions defined in your endpoint.

  #### Paths and URLs



  Overall, an endpoint has three responsibilities:

    * 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 `mix phoenix.new`
  generator, an endpoint was automatically generated as
  part of your application:

