update some comments

c++/src/capnp/ez-rpc.h

@@ -90,7 +90,7 @@ class EzRpcClient {
   // Some of these restrictions will probably be lifted in future versions, but some things will
   // always require using the low-level interfaces directly.  If you are interested in working
   // at a lower level, start by looking at these interfaces:
-  // - `kj::startAsyncIo()` in `kj/async-io.h`.
+  // - `kj::setupAsyncIo()` in `kj/async-io.h`.
   // - `RpcSystem` in `capnp/rpc.h`.
   // - `TwoPartyVatNetwork` in `capnp/rpc-twoparty.h`.
 

c++/src/kj/async-io.h

@@ -473,7 +473,7 @@ AsyncIoContext setupAsyncIo();
 //
 //       // And we can wait for the promise to complete.  Note that you can only use `wait()`
 //       // from the top level, not from inside a promise callback.
-//       String text = textPromise.wait();
+//       String text = textPromise.wait(ioContext.waitScope);
 //       print(text);
 //       return 0;
 //     }

c++/src/kj/async.h

@@ -597,7 +597,7 @@ class EventLoop {
   //       return 0;
   //     }
   //
-  // Most applications that do I/O will prefer to use `setupIoEventLoop()` from `async-io.h` rather
+  // Most applications that do I/O will prefer to use `setupAsyncIo()` from `async-io.h` rather
   // than allocate an `EventLoop` directly.
 
 public: