From f13b253c2f1d1e20d524e414d79329071920b307 Mon Sep 17 00:00:00 2001
From: Artem Bilan <abilan@pivotal.io>
Date: Wed, 5 Apr 2017 14:41:32 -0400
Subject: [PATCH] Fix Reference Manual for wrong format and links

---
 src/reference/asciidoc/amqp.adoc      | 31 +++++++++++++++++++++++++--
 src/reference/asciidoc/http.adoc      |  2 +-
 src/reference/asciidoc/whats-new.adoc |  2 +-
 3 files changed, 31 insertions(+), 4 deletions(-)

diff --git a/src/reference/asciidoc/amqp.adoc b/src/reference/asciidoc/amqp.adoc
index 6ec9d2e03c..4fc2919820 100644
--- a/src/reference/asciidoc/amqp.adoc
+++ b/src/reference/asciidoc/amqp.adoc
@@ -1095,7 +1095,34 @@ The following Spring Boot application provides an example of configuring the out
 
 [source, java]
 ----
-// To be supplied when the DSL Amqp factory class adds support for the async gateway.
+@SpringBootApplication
+public class AmqpAsyncApplication {
+
+    public static void main(String[] args) {
+         ConfigurableApplicationContext context =
+                 new SpringApplicationBuilder(AmqpAsyncApplication.class)
+                      .web(false)
+                      .run(args);
+         MyGateway gateway = context.getBean(MyGateway.class);
+         String reply = gateway.sendToRabbit("foo");
+         System.out.println(reply);
+    }
+
+    @Bean
+    public IntegrationFlow asyncAmqpOutbound(AsyncRabbitTemplate asyncRabbitTemplate) {
+        return f -> f
+                .handle(Amqp.asyncOutboundGateway(asyncRabbitTemplate)
+                        .routingKey("foo")); // default exchange - route to queue 'foo'
+    }
+
+    @MessagingGateway(defaultRequestChannel = "asyncAmqpOutbound.input")
+    public interface MyGateway {
+
+        String sendToRabbit(String data);
+
+    }
+
+}
 ----
 
 [[content-type-conversion-outbound]]
@@ -1140,7 +1167,7 @@ JSON converter to be selected.
 
 This applies to both the outbound channel adapter and gateway.
 
-NOTE
+[NOTE]
 ====
 Starting with _version 5.0_, headers that are added to the `MessageProperties` of the outbound message are never overwritten by mapped headers (by default).
 Previously, this was only the case if the message converter was a `ContentTypeDelegatingMessageConverter` (in that case, the header was mapped first, so that the proper converter could be selected).
diff --git a/src/reference/asciidoc/http.adoc b/src/reference/asciidoc/http.adoc
index 53d70662d4..ed17e08fc5 100644
--- a/src/reference/asciidoc/http.adoc
+++ b/src/reference/asciidoc/http.adoc
@@ -226,7 +226,7 @@ Otherwise, it is treated as an `async` mode and the `Mono` response is adapted t
 
 See http://docs.spring.io/spring/docs/5.0.0.M5/spring-framework-reference/html/web-reactive.html#web-reactive-client[WebFlux documentation] and https://projectreactor.io/[Project Reactor] for more information.
 
-For other settings like cookie, uri variables, etc, please see <<HttpRequestExecutingMessageHandler>> above.
+For other settings like cookie, uri variables, etc, please see `HttpRequestExecutingMessageHandler` above.
 
 [[http-namespace]]
 === HTTP Namespace Support
diff --git a/src/reference/asciidoc/whats-new.adoc b/src/reference/asciidoc/whats-new.adoc
index 9f3c9cdab9..1cb3cba0e1 100644
--- a/src/reference/asciidoc/whats-new.adoc
+++ b/src/reference/asciidoc/whats-new.adoc
@@ -30,7 +30,7 @@ See <<mongodb-outbound-gateway>> for more information.
 ==== HTTP Reactive Outbound Gateway and Channel Adapter
 
 The new `ReactiveHttpRequestExecutingMessageHandler` adds support for WebFlux `WebClient` for outbound channel adapter and gateway.
-See <<ReactiveHttpRequestExecutingMessageHandler>> for more information.
+See <<http-outbound>> for more information.
 
 ==== Content Type Conversion