   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
+  Runtime configuration, instead, is accessed during or
+  after your application is started and can be read and written 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
+  ### Compile-time configuration
+
+    * `:debug_errors` - when `true`, uses `Plug.Debugger` functionality for
+      debugging failures in the application. Recommended to be set to `true`
       only in development as it allows listing of the application source
-      code during debugging. Defaults to false.
+      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


    * `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`
      using this endpoint's configured pubsub server
    * `broadcast(topic, event, msg)` - proxy to `Phoenix.Channel.broadcast/3`
      using this endpoint's configured pubsub server
    * `broadcast!(topic, event, msg)` - proxy 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 the
  functions that are automatically defined in your endpoint.

  #### Paths and URLs

