       `false` also disables hot code upgrades. Therefore, `:include_erts` should be
       set to `false` with caution and only if you are assembling the release on the
       same server that runs it.
+
+  Also see the "Customization" section for other options and the hooks
+  available to customize your release.
 
   Other features, such as runtime configuration, may introduce their
   options. Those will be listed in their own respective sections.

    * `:config_providers` - a list of tuples with custom config providers.
      See `Config.Provider` for more information. Defaults to `[]`.

  ## Steps

  TODO: Implement :steps.

  ## vm.args

  TODO: Implement custom vm.args.


      information, documentation chunks and other non-essential metadata removed.
      Defaults to `true`.

    * `:cookie` - a string representing the Erlang Distribution cookie. If no cookie
      is set, one is automatically generated when the first release is assembled. The
      cookie will be written to `releases/COOKIE` and shared across multiple release
