   The child specification describes how the supervisor starts, shuts down,
   and restarts child processes.
 
-  The child specification contains 5 keys. The first two are required,
+  The child specification contains 6 keys. The first two are required,
   and the remaining ones are optional:
 
-    * `:id` - a value used to identify the child specification
+    * `:id` - any term used to identify the child specification
       internally by the supervisor; defaults to the given module.
       In the case of conflicting `:id` values, the supervisor will refuse
       to initialize and require explicit IDs. This key is required.

  has been replaced by the `DynamicSupervisor`. The `:simple_one_for_one`
  supervisor was similar to `:one_for_one` but suits better when dynamically
  attaching children. Many functions in this module behaved slightly
  differently when this strategy is used. See the `DynamicSupervisor` module
  for more information and migration strategies.

  ## Name registration

      restarts in transient mode, and linked processes exit with the same
      reason unless they're trapping exits

  Notice that the supervisor that reaches maximum restart intensity will exit with
  `:shutdown` reason. In this case the supervisor will only be restarted if its
  child specification was defined with the `:restart` option set to `:permanent`
  (the default).
