Fix typos.

c++/src/capnp/capability.h

@@ -105,7 +105,7 @@ class Request: public Params::Builder {
   // structure with a method send() that actually sends it.
   //
   // Given a Cap'n Proto method `foo(a :A, b :B): C`, the generated client interface will have
-  // a method `Request<FooParams, C> startFoo()` (as well as a convenience method
+  // a method `Request<FooParams, C> fooRequest()` (as well as a convenience method
   // `RemotePromise<C> foo(A::Reader a, B::Reader b)`).
 
 public:
@@ -298,7 +298,7 @@ public:
   //
   // Keep in mind that asynchronous cancellation cannot occur while the method is synchronously
   // executing on a local thread.  The method must perform an asynchronous operation or call
-  // `EventLoop::current().runLater()` to yield control.
+  // `EventLoop::current().evalLater()` to yield control.
   //
   // Note:  You might think that we should offer `onCancel()` and/or `isCanceled()` methods that
   // provide notification when the caller cancels the request without forcefully killing off the

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

@@ -146,8 +146,8 @@ class UnixEventPort::FdObserver {
   // else, it means that read() (or recv()) will return data.
   //
   // The presence of out-of-band data should NOT fire this event. However, the event may
-  // occasionally fire spurriously (when there is actually no data to read), and one thing that can
-  // cause such spurrious events is the arrival of OOB data on certain platforms whose event
+  // occasionally fire spuriously (when there is actually no data to read), and one thing that can
+  // cause such spurious events is the arrival of OOB data on certain platforms whose event
   // interfaces fail to distinguish between regular and OOB data (e.g. Mac OSX).
   //
   // WARNING: The exact behavior of this class differs across systems, since event interfaces