Update docs for opts for HashRing.Managed.new/2

Author: davidwebster48

lib/managed_ring.ex

@@ -26,7 +26,8 @@ defmodule HashRing.Managed do
           nodes: node_list,
           monitor_nodes: boolean,
           node_blacklist: pattern_list,
-          node_whitelist: pattern_list
+          node_whitelist: pattern_list,
+          node_type: :all | :hidden | :visible
         ]
 
   @type child_spec_options :: [
@@ -65,6 +66,7 @@ defmodule HashRing.Managed do
   It takes an optional set of options which control how the ring behaves.
   Valid options are as follows:
 
+  * `nodes: list` - a list of nodes to initialize the ring.
   * `monitor_nodes: boolean` - will automatically monitor Erlang node membership,
     if new nodes are connected or nodes are disconnected, the ring will be updated automatically.
     In this configuration, nodes cannot be added or removed via the API. Those requests will be ignored.
@@ -74,7 +76,7 @@ defmodule HashRing.Managed do
     is provided, the blacklist has no effect.
   * `node_whitelist: [String.t | Regex.t]` - The same as `node_blacklist`, except the opposite; only nodes
     which match a pattern in the whitelist will result in the ring being updated.
-  - `node_type: :all | :hidden | :visible`: refers what kind of nodes will be monitored
+  * `node_type: :all | :hidden | :visible`: refers what kind of nodes will be monitored
     when `monitor_nodes` is `true`. For more information, see `:net_kernel.monitor_nodes/2`.
 
   An error is returned if the ring already exists or if bad ring options are provided.