Small fix in README

Author: larskanis

README.md

@@ -244,7 +244,7 @@ It also uses Ruby's DNS resolution instead of libpq's builtin functions.
 
 Internally Pg always uses the nonblocking connection mode of libpq.
 It then behaves like running in blocking mode but ensures, that all blocking IO is handled in Ruby through a possibly registered `Fiber.scheduler`.
-When `PG::Connection.setnonblocking(true)` is called then the nonblocking state stays enabled, but the additional handling of blocking states is disabled, so that the calling program has to handle blocking states on its own.
+When `PG::Connection#setnonblocking(true)` is called then the nonblocking state stays enabled, but the additional handling of blocking states is disabled, so that the calling program has to handle blocking states on its own.
 
 An exception to this rule are the methods for large objects like `PG::Connection#lo_create` and authentication methods using external libraries (like GSSAPI authentication).
 They are not compatible with `Fiber.scheduler`, so that blocking states are not passed to the registered IO scheduler.