readme: note how to configure node addresses

README.md

@@ -72,7 +72,7 @@ not "drain" from the simulation.
     {
       "LND": {
         "id": "Alice",
-        "address": "https://localhost:10011",
+        "address": "https://127.0.0.1:10011",
         "macaroon": "/path/admin.macaroon",
         "cert": "/path/tls.cert"
       }
@@ -90,6 +90,8 @@ not "drain" from the simulation.
 }
 ```
 
+**Note that node addresses must be declare with HTTPS transport, i.e. <https://ip-or-domain>**
+
 Nodes can be identified by an arbitrary string ("Alice", "CLN1", etc) or
 by their node public key. If a valid public key is provided it *must* 
 match the public key reported by the node.
@@ -134,7 +136,7 @@ The example simulation file below sets up the following simulation:
     {
       "CLN": {
         "id": "0230a16a05c5ca120136b3a770a2adfdad88a68d526e63448a9eef88bddd6a30d8",
-        "address": "https://localhost:10013",
+        "address": "https://127.0.0.1:10013",
         "ca_cert": "/path/ca.pem",
         "client_cert": "/path/client.pem",
         "client_key": "/path/client-key.pem"
@@ -164,6 +166,8 @@ The example simulation file below sets up the following simulation:
 }
 ```
 
+**Note that node addresses must be declare with HTTPS transport, i.e <https://ip-or-domain>**
+
 Nodes can be identified by their public key or an id string (as 
 described above). Activity sources and destinations may reference the 
 `id` defined in `nodes`, but destinations that are not listed in `nodes`