Remove double commas in docs for link syntax

Author: artembilan

src/reference/asciidoc/chain.adoc

@@ -121,7 +121,7 @@ In this case, it is 'somethingChain$child#1'.
 Note, this transformer is not registered as a bean within the application context, so it does not get a `beanName`.
 However its `componentName` has a value that is useful for logging and other purposes.
 
-The `id` attribute for `<chain>` elements lets them be eligible for <<./jmx.adoc#jmx-mbean-exporter,,JMX export>>, and they are trackable in the <<./message-history.adoc#message-history,,message history>>.
+The `id` attribute for `<chain>` elements lets them be eligible for <<./jmx.adoc#jmx-mbean-exporter,JMX export>>, and they are trackable in the <<./message-history.adoc#message-history,message history>>.
 You can access them from the `BeanFactory` by using the appropriate bean name, as discussed earlier.
 
 TIP: It is useful to provide an explicit `id` attribute on `<chain>` elements to simplify the identification of sub-components in logs and to provide access to them from the `BeanFactory` etc.

src/reference/asciidoc/changes-2.1-2.2.adoc

@@ -27,10 +27,10 @@ For more information, see <<./mongodb.adoc#mongodb-outbound-channel-adapter,Mong
 Spring Integration now includes components for the Java Persistence API (JPA) for retrieving and persisting JPA entity objects.
 The JPA Adapter includes the following components:
 
-* <<./jpa.adoc#jpa-inbound-channel-adapter,,Inbound channel adapter>>
-* <<./jpa.adoc#jpa-outbound-channel-adapter,,Outbound channel adapter>>
-* <<./jpa.adoc#jpa-updating-outbound-gateway,,Updating outbound gateway>>
-* <<./jpa.adoc#jpa-retrieving-outbound-gateway,,Retrieving outbound gateway>>
+* <<./jpa.adoc#jpa-inbound-channel-adapter,Inbound channel adapter>>
+* <<./jpa.adoc#jpa-outbound-channel-adapter,Outbound channel adapter>>
+* <<./jpa.adoc#jpa-updating-outbound-gateway,Updating outbound gateway>>
+* <<./jpa.adoc#jpa-retrieving-outbound-gateway,Retrieving outbound gateway>>
 
 For more information, see <<./jpa.adoc#jpa,JPA Support>>.
 

src/reference/asciidoc/changes-4.3-5.0.adoc

@@ -129,7 +129,7 @@ See <<./jms.adoc#jms,JMS Support>> for more information.
 ===== Mail Changes
 
 Some inconsistencies with rendering IMAP mail content have been resolved.
-See <<./mail.adoc#imap-format-important,,the note in the "`Mail-receiving Channel Adapter`" section>> for more information.
+See <<./mail.adoc#imap-format-important,the note in the "`Mail-receiving Channel Adapter`" section>> for more information.
 
 ===== Feed Changes
 

src/reference/asciidoc/configuration.adoc

@@ -152,7 +152,7 @@ The next section describes what happens if exceptions occur within the asynchron
 [[namespace-errorhandler]]
 === Error Handling
 
-As described in the <<./overview.adoc#overview,,overview>> at the very beginning of this manual, one of the main motivations behind a message-oriented framework such as Spring Integration is to promote loose coupling between components.
+As described in the <<./overview.adoc#overview,overview>> at the very beginning of this manual, one of the main motivations behind a message-oriented framework such as Spring Integration is to promote loose coupling between components.
 The message channel plays an important role, in that producers and consumers do not have to know about each other.
 However, the advantages also have some drawbacks.
 Some things become more complicated in a loosely coupled environment, and one example is error handling.
@@ -210,7 +210,7 @@ Starting with version 4.3.10, Spring Integration provides the `ErrorMessagePubli
 You can use them as a general mechanism for publishing `ErrorMessage` instances.
 You can call or extend them in any error handling scenarios.
 The `ErrorMessageSendingRecoverer` extends this class as a `RecoveryCallback` implementation that can be used with retry, such as the
-<<./handler-advice.adoc#retry-advice,, `RequestHandlerRetryAdvice`>>.
+<<./handler-advice.adoc#retry-advice,`RequestHandlerRetryAdvice`>>.
 The `ErrorMessageStrategy` is used to build an `ErrorMessage` based on the provided exception and an `AttributeAccessor` context.
 It can be injected into any `MessageProducerSupport` or `MessagingGatewaySupport`.
 The `requestMessage` is stored under `ErrorMessageUtils.INPUT_MESSAGE_CONTEXT_KEY` in the `AttributeAccessor` context.
@@ -415,7 +415,7 @@ The processing of these annotations creates the same beans as the corresponding
 See <<annotations_on_beans>>.
 The bean names are generated from the following pattern: `[componentName].[methodName].[decapitalizedAnnotationClassShortName]`
 (for example, for the preceding example the bean name is `thingService.otherThing.serviceActivator`) for the `AbstractEndpoint` and the same name with an additional `.handler` (`.source`) suffix for the `MessageHandler` (`MessageSource`) bean.
-The `MessageHandler` instances (`MessageSource` instances) are also eligible to be tracked by <<./message-history.adoc#message-history,, the message history>>.
+The `MessageHandler` instances (`MessageSource` instances) are also eligible to be tracked by <<./message-history.adoc#message-history,the message history>>.
 
 Starting with version 4.0, all messaging annotations provide `SmartLifecycle` options (`autoStartup` and `phase`) to allow endpoint lifecycle control on application context initialization.
 They default to `true` and `0`, respectively.

src/reference/asciidoc/content-enrichment.adoc

@@ -11,9 +11,9 @@ The Spring Integration `Core` module includes two enrichers:
 
 It also includes three adapter-specific header enrichers:
 
-* <<./xml.adoc#xml-xpath-header-enricher,,XPath Header Enricher (XML Module)>>
-* <<./mail.adoc#mail-namespace,,Mail Header Enricher (Mail Module)>>
-* <<./xmpp.adoc#xmpp-message-outbound-channel-adapter,,XMPP Header Enricher (XMPP Module)>>
+* <<./xml.adoc#xml-xpath-header-enricher,XPath Header Enricher (XML Module)>>
+* <<./mail.adoc#mail-namespace,Mail Header Enricher (Mail Module)>>
+* <<./xmpp.adoc#xmpp-message-outbound-channel-adapter,XMPP Header Enricher (XMPP Module)>>
 
 See the adapter-specific sections of this reference manual to learn more about those adapters.
 

src/reference/asciidoc/file.adoc

@@ -608,7 +608,7 @@ By default, they append `.writing` to the file name and remove it when the trans
 Another common technique is to write a second "`marker`" file to indicate that the file transfer is complete.
 In this scenario, you should not consider `somefile.txt` (for example) to be available for use until `somefile.txt.complete` is also present.
 Spring Integration version 5.0 introduced new filters to support this mechanism.
-Implementations are provided for the file system (`FileSystemMarkerFilePresentFileListFilter`), <<./ftp.adoc#ftp-incomplete,, FTP>> and <<./sftp.adoc#sftp-incomplete,, SFTP>>.
+Implementations are provided for the file system (`FileSystemMarkerFilePresentFileListFilter`), <<./ftp.adoc#ftp-incomplete,FTP>> and <<./sftp.adoc#sftp-incomplete,SFTP>>.
 They are configurable such that the marker file can have any name, although it is usually related to the file being transferred.
 See the https://docs.spring.io/spring-integration/api/org/springframework/integration/file/filters/FileSystemMarkerFilePresentFileListFilter.html[Javadoc] for more information.
 
@@ -950,7 +950,7 @@ It is often better to use a sequence of transformers than to put all transformat
 In that case the `File` to `byte[]` conversion might be a logical first step.
 
 `FileToStringTransformer` extends `AbstractFilePayloadTransformer` convert a `File` object to a `String`.
-If nothing else, this can be useful for debugging (consider using it with a <<./channel.adoc#channel-wiretap,,wire tap>>).
+If nothing else, this can be useful for debugging (consider using it with a <<./channel.adoc#channel-wiretap,wire tap>>).
 
 To configure file-specific transformers, you can use the appropriate elements from the file namespace, as the following example shows:
 
@@ -1057,7 +1057,7 @@ This line is not included in the sequence header (if `applySequence` is true) no
 If a file contains only the header line, the file is treated as empty and, therefore, only `FileMarker` instances are emitted during splitting (if markers are enabled -- otherwise, no messages are emitted).
 By default (if no header name is set), the first line is considered to be data and becomes the payload of the first emitted message.
 
-If you need more complex logic about header extraction from the file content (not first line, not the whole content of the line, not one particular header, and so on), consider using  <<./content-enrichment.adoc#header-enricher,, header enricher>> ahead of the `FileSplitter`.
+If you need more complex logic about header extraction from the file content (not first line, not the whole content of the line, not one particular header, and so on), consider using  <<./content-enrichment.adoc#header-enricher,header enricher>> ahead of the `FileSplitter`.
 Note that the lines that have been moved to the headers might be filtered downstream from the normal content process.
 
 ==== Configuring with Java Configuration

src/reference/asciidoc/ftp.adoc

@@ -354,7 +354,7 @@ The default `MetadataStore` is a `SimpleMetadataStore`, which stores state in me
 Since version 4.1.5, these filters have a new property (`flushOnUpdate`) that causes them to flush the
 metadata store on every update (if the store implements `Flushable`).
 
-IMPORTANT: Further, if you use a distributed `MetadataStore` (such as <<./redis.adoc#redis-metadata-store,,Redis>> or <<./gemfire.adoc#gemfire-metadata-store,,GemFire>>), you can have multiple instances of the same adapter or application and be sure that each file is processed only once.
+IMPORTANT: Further, if you use a distributed `MetadataStore` (such as <<./redis.adoc#redis-metadata-store,Redis>> or <<./gemfire.adoc#gemfire-metadata-store,GemFire>>), you can have multiple instances of the same adapter or application and be sure that each file is processed only once.
 
 The actual local filter is a `CompositeFileListFilter` that contains the supplied filter and a pattern filter that prevents processing files that are in the process of being downloaded (based on the `temporary-file-suffix`).
 Files are downloaded with this suffix (the default is `.writing`), and the file is renamed to its final name when the transfer is complete, making it 'visible' to the filter.
@@ -805,7 +805,7 @@ When all files are consumed, the remote fetch is attempted again, to pick up any
 IMPORTANT: When you deploy multiple instances of an application, we recommend a small `max-fetch-size`, to avoid one instance "`grabbing`" all the files and starving other instances.
 
 Another use for `max-fetch-size` is if you want to stop fetching remote files but continue to process files that have already been fetched.
-Setting the `maxFetchSize` property on the `MessageSource` (programmatically, with JMX, or with a <<./control-bus.adoc#control-bus,,control bus>>) effectively stops the adapter from fetching more files but lets the poller continue to emit messages for files that have previously been fetched.
+Setting the `maxFetchSize` property on the `MessageSource` (programmatically, with JMX, or with a <<./control-bus.adoc#control-bus,control bus>>) effectively stops the adapter from fetching more files but lets the poller continue to emit messages for files that have previously been fetched.
 If the poller is active when the property is changed, the change takes effect on the next poll.
 
 Starting with version 5.1, the synchronizer can be provided with a `Comparator<FTPFile>`.
@@ -1068,10 +1068,10 @@ The `file_remoteDirectory` header provides the remote directory name, and the `f
 
 The message payload resulting from a `get` operation is a `File` object that represents the retrieved file or an `InputStream` when you use the `-stream` option.
 The `-stream` option allows retrieving the file as a stream.
-For text files, a common use case is to combine this operation with a <<./file.adoc#file-splitter,,file splitter>> or a <<./transformer.adoc#stream-transformer,,stream transformer>>.
+For text files, a common use case is to combine this operation with a <<./file.adoc#file-splitter,file splitter>> or a <<./transformer.adoc#stream-transformer,stream transformer>>.
 When consuming remote files as streams, you are responsible for closing the `Session` after the stream is consumed.
 For convenience, the `Session` is provided in the `closeableResource` header, which you can access with a convenience method on `IntegrationMessageHeaderAccessor`
-The following example shows how to do use the covenience method:
+The following example shows how to use the convenience method:
 
 ====
 [source, java]
@@ -1083,7 +1083,7 @@ if (closeable != null) {
 ----
 ====
 
-Framework components such as the <<./file.adoc#file-splitter,,file splitter>> and the <<./transformer.adoc#stream-transformer,,stream transformer>> automatically close the session after the data is transferred.
+Framework components such as the <<./file.adoc#file-splitter,file splitter>> and the <<./transformer.adoc#stream-transformer,stream transformer>> automatically close the session after the data is transferred.
 
 The following example shows how to consume a file as a stream:
 

src/reference/asciidoc/functions-support.adoc

@@ -3,7 +3,7 @@
 
 Starting with version 5.1, Spring Integration provides direct support for interfaces in the `java.util.function` package.
 All messaging endpoints, (Service Activator, Transformer, Filter, etc.) can now refer to `Function` (or `Consumer`) beans.
-The <<./configuration.adoc#annotations,,Messaging Annotations>> can be applied directly on these beans similar to regular `MessageHandler` definitions.
+The <<./configuration.adoc#annotations,Messaging Annotations>> can be applied directly on these beans similar to regular `MessageHandler` definitions.
 For example if you have this `Function` bean definition:
 
 

src/reference/asciidoc/gateway.adoc

@@ -46,7 +46,7 @@ It lets you configure an interface as a service, as the following example shows:
 
 With this configuration defined, the `cafeService` can now be injected into other beans, and the code that invokes the methods on that proxied instance of the `Cafe` interface has no awareness of the Spring Integration API.
 The general approach is similar to that of Spring Remoting (RMI, HttpInvoker, and so on).
-See the <<./samples.adoc#samples,,"`Samples`">> Appendix for an example that uses the `gateway` element (in the Cafe demo).
+See the <<./samples.adoc#samples,"`Samples`">> Appendix for an example that uses the `gateway` element (in the Cafe demo).
 
 The defaults in the preceding configuration are applied to all methods on the gateway interface.
 If a reply timeout is not specified, the calling thread waits indefinitely for a reply.
@@ -79,7 +79,7 @@ By defining a `default-reply-channel` you can point to a channel of your choosin
 In this case, that is a `publish-subscribe-channel`.
 The gateway creates a bridge from it to the temporary, anonymous reply channel that is stored in the header.
 
-You might also want to explicitly provide a reply channel for monitoring or auditing through an interceptor (for example, <<./channel.adoc#channel-wiretap,, wiretap>>).
+You might also want to explicitly provide a reply channel for monitoring or auditing through an interceptor (for example, <<./channel.adoc#channel-wiretap,wiretap>>).
 To configure a channel interceptor, you need a named channel.
 
 [[gateway-configuration-annotations]]

src/reference/asciidoc/handler-advice.adoc

@@ -682,9 +682,9 @@ The following example shows `<transactional>` in use:
 </bean>
 ----
 
-If you are familiar with the <<./jpa.adoc#jpa,, JPA integration components>>, such a configuration is not new, but now we can start a transaction from any point in our flow -- not only from the `<poller>` or a message-driven channel adapter such as <<./jms.adoc#jms-message-driven-channel-adapter,, JMS>>.
+If you are familiar with the <<./jpa.adoc#jpa,JPA integration components>>, such a configuration is not new, but now we can start a transaction from any point in our flow -- not only from the `<poller>` or a message-driven channel adapter such as <<./jms.adoc#jms-message-driven-channel-adapter,JMS>>.
 
-Java configuration can be simplified by using the `TransactionInterceptorBuilder`, and the result bean name can be used in the <<./configuration.adoc#annotations,, messaging annotations>> `adviceChain` attribute, as the following example shows:
+Java configuration can be simplified by using the `TransactionInterceptorBuilder`, and the result bean name can be used in the <<./configuration.adoc#annotations,messaging annotations>> `adviceChain` attribute, as the following example shows:
 
 [source,java]
 ----

src/reference/asciidoc/ip.adoc

@@ -636,7 +636,7 @@ The following example shows how to configure a connection interceptor factory ch
 === TCP Connection Events
 
 Beginning with version 3.0, changes to `TcpConnection` instances are reported by `TcpConnectionEvent` instances.
-`TcpConnectionEvent` is a subclass of `ApplicationEvent` and can thus be received by any `ApplicationListener` defined in the `ApplicationContext` -- for example <<./event.adoc#appevent-inbound,,an event inbound channel adapter>>.
+`TcpConnectionEvent` is a subclass of `ApplicationEvent` and can thus be received by any `ApplicationListener` defined in the `ApplicationContext` -- for example <<./event.adoc#appevent-inbound,an event inbound channel adapter>>.
 
 `TcpConnectionEvents` have the following properties:
 
@@ -743,7 +743,7 @@ Two additional attributes support this mechanism.
 The `retry-interval` specifies (in milliseconds) how often the framework attempts to reconnect after a connection failure.
 The `scheduler` supplies a `TaskScheduler` to schedule the connection attempts and to test that the connection is still active.
 
-If you don't provide a scheduler, the framework's default <<./configuration.adoc#namespace-taskscheduler,, taskScheduler>> bean is used.
+If you don't provide a scheduler, the framework's default <<./configuration.adoc#namespace-taskscheduler,taskScheduler>> bean is used.
 
 For an outbound adapter, the connection is normally established when the first message is sent.
 The `client-mode="true"` on an outbound adapter causes the connection to be established when the adapter is started.

src/reference/asciidoc/jdbc.adoc

@@ -1094,10 +1094,10 @@ You can use the `JdbcMetadataStore` to maintain the metadata state across applic
 This `MetadataStore` implementation can be used with adapters such as the following:
 
 
-* <<./feed.adoc#feed-inbound-channel-adapter,,Feed inbound channel adapters>>
-* <<./file.adoc#file-reading,,files>>
-* <<./ftp.adoc#ftp-inbound,,FTP inbound channel adapters>>
-* <<./sftp.adoc#sftp-inbound,,SFTP inbound channel adapters>>
+* <<./feed.adoc#feed-inbound-channel-adapter,Feed inbound channel adapters>>
+* <<./file.adoc#file-reading,File inbound channel adapters>>
+* <<./ftp.adoc#ftp-inbound,FTP inbound channel adapters>>
+* <<./sftp.adoc#sftp-inbound,SFTP inbound channel adapters>>
 
 To configure these adapters to use the `JdbcMetadataStore`, declare a Spring bean by using a bean name of `metadataStore`.
 The Feed inbound channel adapter and the feed inbound channel adapter both automatically pick up and use the declared `JdbcMetadataStore`, as the following example shows:

src/reference/asciidoc/message-store.adoc

@@ -13,7 +13,7 @@ Spring Integration provides support for the message store pattern by:
 * Providing several implementations of this interface
 * Exposing a `message-store` attribute on all components that have the capability to buffer messages so that you can inject any instance that implements the `MessageStore` interface.
 
-Details on how to configure a specific message store implementation and how to inject a `MessageStore` implementation into a specific buffering component are described throughout the manual (see the specific component, such as <<./channel.adoc#channel-configuration-queuechannel,,QueueChannel>>, <<./aggregator.adoc#aggregator,,Aggregator>>, <<./delayer.adoc#delayer,,Delayer>>, and others).
+Details on how to configure a specific message store implementation and how to inject a `MessageStore` implementation into a specific buffering component are described throughout the manual (see the specific component, such as <<./channel.adoc#channel-configuration-queuechannel,QueueChannel>>, <<./aggregator.adoc#aggregator,Aggregator>>, <<./delayer.adoc#delayer,Delayer>>, and others).
 The following pair of examples show how to add a reference to a message store for a `QueueChannel` and for an aggregator:
 
 .QueueChannel