diff --git a/docs/src/main/asciidoc/spring-cloud-stream.adoc b/docs/src/main/asciidoc/spring-cloud-stream.adoc
index f137ea2b1..9d0680f77 100644
--- a/docs/src/main/asciidoc/spring-cloud-stream.adoc
+++ b/docs/src/main/asciidoc/spring-cloud-stream.adoc
@@ -588,10 +588,8 @@ source of the data may be a classic REST endpoint. How do we bridge such source
 Spring Cloud Stream provides two mechanisms, so let's look at them in more details
 
 Here, for both samples we'll use a standard MVC endpoint method called `delegateToSupplier` bound to the root web context,
-delegating incoming requests to stream via two different mechanisms -
-imperative (via StreamBridge) and reactive (via EmitterProcessor).
+delegating incoming requests to stream via StreamBridge mechanism.
 
-====== Using StreamBridge
 
 [source, java]
 ----
@@ -663,47 +661,6 @@ As you can see the preceding example is very similar to the previous one with th
 Here we're sending data to `myDestination` name which does not exist as a binding. Therefore such name will be treated as dynamic destination
 as described in <<Routing FROM Consumer>> section.
 
-====== Using reactor API
-
-Another approach that can be used to send arbitrary data to the output is using Reactor API.
-
-All we need to do is declare a `Supplier<Flux<whatever>>` which returns https://projectreactor.io/docs/core/release/api/reactor/core/publisher/EmitterProcessor.html[EmitterProcessor]
-from the reactor API (see <<Reactive Functions support>> for more details) to effectively provide a
-bridge between the actual event source (_foreign source_) and spring-cloud-stream.
-All you need to do now is feed the `EmitterProcessor` with data via `EmitterProcessor#onNext(data)` operation.
-
-For example,
-
-[source, java]
-----
-public class SampleApplication {
-
-    public static void main(String[] args) {
-               SpringApplication.run(SampleApplication.class);
-    }
-
-    EmitterProcessor<String> processor = EmitterProcessor.create();
-
-    @Bean
-    public ApplicationRunner runner() {
-        Message<String> msg1 = MessageBuilder.withPayload("foo")
-                .setHeader("*.events", "test1.events.billing")
-                .build();
-        Message<String> msg2 = MessageBuilder.withPayload("bar")
-                .setHeader("*.events", "test2.events.messages")
-                .build();
-        return args -> {
-            this.processor.onNext(msg1);
-            this.processor.onNext(msg2);
-        };
-    }
-
-    @Bean
-    public Supplier<Flux<String>> supplier() {
-               return () -> this.processor;
-    }
-}
-----
 
 In the preceding example, we are using `ApplicationRunner` as a _foreign source_ to feed the stream.
 
@@ -720,23 +677,20 @@ public class WebSourceApplication {
 		SpringApplication.run(WebSourceApplication.class);
 	}
 
-	EmitterProcessor<String> processor = EmitterProcessor.create();
+	@Autowired
+	private StreamBridge streamBridge;
 
 	@RequestMapping
 	@ResponseStatus(HttpStatus.ACCEPTED)
 	public void delegateToSupplier(@RequestBody String body) {
-		processor.onNext(body);
-	}
-
-	@Bean
-	public Supplier<Flux<String>> supplier() {
-		return () -> this.processor;
+		//processor.onNext(body);
+		streamBridge.send("myBinidng", body);
 	}
 }
 ----
 
-Same as before we declare a `Supplier` bean which returns `Flux<String>`. But given that this is a REST endpoint
-we send messages by simply posting to this REST endpoint.
+As you can see inside of `delegateToSupplier` method we're using StreamBridge to send data to `myBinidng` binding. And here you're also benefiting from 
+the dynamic features of StreamBridge where if `myBinidng` doesn't exist it will be created automatically, otherwise existing binding will be used.
 
 ----
 curl -H "Content-Type: text/plain" -X POST -d "hello from the other side" http://localhost:8080/