Update README.md

README.md

@@ -27,7 +27,7 @@ cd pubsub
 
 The bootstrapper creates a new libp2p node, subscribes to the shared topic string, spawns a go routine to emit any publishes to that topic, and then waits forever.
 
-(Note that the node ID of `pubsub-interop` is going to be `Qm...6aJ9oRuEzWa`.  Node IDs in libp2p are just public keys, and the public key `Qm...6aJ9oRuEzWa` is derived from the private key file `../util/private_key.bin.bootstrapper.Wa`.  That file is just an X.509 keypair generated by the included program `util/private-key-gen`).  We use fixed public/private keypairs for each node in this example to keep things simple.)
+(Note that the node ID of `raven` is going to be `Qm...6aJ9oRuEzWa`.  Node IDs in libp2p are just public keys, and the public key `Qm...6aJ9oRuEzWa` is derived from the private key file `../util/private_key.bin.bootstrapper.Wa`.  That file is just an X.509 keypair generated by the included program `util/private-key-gen`).  We use fixed public/private keypairs for each node in this example to keep things simple.)
 
 **Second terminal**:  Create a go peer to connect to bootstrapper and publish on the topic
 
@@ -75,7 +75,7 @@ DEBUG="libp2p:floodsub*,libp2p:switch*,mss:*" node index.js [args...]
 
 **Go** To see debug messages in Go programs, do this at runtime:
 ```
-IPFS_LOGGING=debug ./pubsub-interop [args...]
+IPFS_LOGGING=debug ./raven [args...]
 ```
 
 (**TODO**:  describe custom instrumenting the local go code for complex debugging)