rsocket
diff --git a/‎README.md
Lines changed: 3 additions & 3 deletions b/‎README.md
Lines changed: 3 additions & 3 deletions
diff --git a/‎rsocket-core/src/jmh/java/io/rsocket/RSocketPerf.java
Lines changed: 0 additions & 199 deletions b/‎rsocket-core/src/jmh/java/io/rsocket/RSocketPerf.java
Lines changed: 0 additions & 199 deletions
diff --git a/‎rsocket-core/src/jmh/java/io/rsocket/fragmentation/FragmentationPerformanceTest.java
Lines changed: 0 additions & 152 deletions b/‎rsocket-core/src/jmh/java/io/rsocket/fragmentation/FragmentationPerformanceTest.java
Lines changed: 0 additions & 152 deletions
@@ -82,7 +82,7 @@ public class ExampleClient {
 
 ## Zero Copy
 By default to make RSocket easier to use it copies the incoming Payload. Copying the payload comes at cost to performance
-and latency. If you want to use zero copy you must disable this. To disable copying you must include a `frameDecoder`
+and latency. If you want to use zero copy you must disable this. To disable copying you must include a `payloadDecoder`
 argument in your `RSocketFactory`. This will let you manage the Payload without copying the data from the underlying
 transport. You must free the Payload when you are done with them
 or you will get a memory leak. Used correctly this will reduce latency and increase performance.
@@ -91,7 +91,7 @@ or you will get a memory leak. Used correctly this will reduce latency and incre
 ```java
 RSocketFactory.receive()
         // Enable Zero Copy
-        .frameDecoder(Frame::retain)
+        .payloadDecoder(Frame::retain)
         .acceptor(new PingHandler())
         .transport(TcpServerTransport.create(7878))
         .start()
@@ -105,7 +105,7 @@ RSocketFactory.receive()
 Mono<RSocket> client =
         RSocketFactory.connect()
             // Enable Zero Copy
-            .frameDecoder(Frame::retain)
+            .payloadDecoder(Frame::retain)
             .transport(TcpClientTransport.create(7878))
             .start();
 ```