diff --git a/README.md b/README.md
index 15d830d2897b272b6e5bb72bba7d5b5344c3c9fe..f96664d8b31a06363d6bbbce05f5831bf1f9542e 100644
--- a/README.md
+++ b/README.md
@@ -129,8 +129,8 @@ gorilla/websocket requires you to constantly read from the connection to respond
 even if you don't expect the peer to send any messages.
 
 The ping API is also much nicer. Unlike gorilla/websocket, you don't need to register a
-callback for pongs, there is a single exported Ping method on the Conn you use that sends
-a ping and waits for the pong. 
+callback for pongs which makes the control flow awkward. There is Ping method on the Conn
+that sends a ping and waits for the pong.
 
 In terms of performance, the differences depend on your application code. nhooyr/websocket
 reuses buffers efficiently out of the box if you use the wsjson and wspb subpackages whereas