Fix plural words rendering in docs

src/reference/antora/modules/ROOT/pages/aggregator.adoc

@@ -697,7 +697,7 @@ If `send-partial-result-on-expiry` is `true`, existing messages in the (partial)
 Otherwise, it is discarded.
 
 There is a difference between `groupTimeout` behavior and `MessageGroupStoreReaper` (see xref:aggregator.adoc#aggregator-xml[Configuring an Aggregator with XML]).
-The reaper initiates forced completion for all `MessageGroup` s in the `MessageGroupStore` periodically.
+The reaper initiates forced completion for all ``MessageGroup``s in the `MessageGroupStore` periodically.
 The `groupTimeout` does it for each `MessageGroup` individually if a new message does not arrive during the `groupTimeout`.
 Also, the reaper can be used to remove empty groups (those retained in order to discard late messages if `expire-groups-upon-completion` is false).
 

src/reference/antora/modules/ROOT/pages/changes-5.0-5.1.adoc

@@ -224,7 +224,7 @@ See xref:metrics.adoc#micrometer-integration[Micrometer Integration] for more in
 [[x51.-integration-graph]]
 == Integration Graph Customization
 
-It is now possible to add additional properties to the `IntegrationNode` s via `Function<NamedComponent, Map<String, Object>> additionalPropertiesCallback` on the `IntegrationGraphServer`.
+It is now possible to add additional properties to the ``IntegrationNode``s via `Function<NamedComponent, Map<String, Object>> additionalPropertiesCallback` on the `IntegrationGraphServer`.
 See xref:graph.adoc#integration-graph[Integration Graph] for more information.
 
 [[x51.-global-properties]]

src/reference/antora/modules/ROOT/pages/changes-5.1-5.2.adoc

@@ -71,7 +71,7 @@ See xref:control-bus.adoc[Control Bus] for more information.
 The `Function<MessageGroup, Map<String, Object>>` strategy has been introduced for the aggregator component to merge and compute headers for output messages.
 See xref:aggregator.adoc#aggregator-api[Aggregator Programming Model] for more information.
 
-All the `MessageHandlingException` s thrown in the framework, includes now a bean resource and source for back tracking a configuration part in case no end-user code involved.
+All the ``MessageHandlingException``s thrown in the framework, includes now a bean resource and source for back tracking a configuration part in case no end-user code involved.
 See xref:scatter-gather.adoc#scatter-gather-error-handling[Error Handling] for more information.
 
 For better end-user experience, Java DSL now provides a configurer variant for starting flow with a gateway interface.

src/reference/antora/modules/ROOT/pages/codec.adoc

@@ -117,7 +117,7 @@ NOTE: This class uses `ClassUtils.findClosestMatch` to select the appropriate co
 When multiple codecs match an object type, `ClassUtils.findClosestMatch` offers the `failOnTie` option.
 If `failOnTie` is `false`, it will return any one of the matching codecs.
 If `failOnTie` is `true` and multiple codecs match, it will throw an `IllegalStateException`.
-CompositeCodec` sets `failOnTie` to `true`, so if multiple codecs match, an `IllegalStateException` is thrown.
+`CompositeCodec` sets `failOnTie` to `true`, so if multiple codecs match, an `IllegalStateException` is thrown.
 
 [[customizing-kryo]]
 === Customizing Kryo

src/reference/antora/modules/ROOT/pages/configuration/annotations.adoc

@@ -174,7 +174,7 @@ public class AnnotationService {
 
 The `@Poller` annotation provides only simple `PollerMetadata` options.
 You can configure the `@Poller` annotation's attributes (`maxMessagesPerPoll`, `fixedDelay`, `fixedRate`, and `cron`) with property placeholders.
-Also, starting with version 5.1, the `receiveTimeout` option for `PollingConsumer` s is also provided.
+Also, starting with version 5.1, the `receiveTimeout` option for ``PollingConsumer``s is also provided.
 If it is necessary to provide more polling options (for example, `transaction`, `advice-chain`, `error-handler`, and others), you should configure the `PollerMetadata` as a generic bean and use its bean name as the `@Poller` 's `value` attribute.
 In this case, no other attributes are allowed (they must be specified on the `PollerMetadata` bean).
 Note, if `inputChannel` is a `PollableChannel` and no `@Poller` is configured, the default `PollerMetadata` is used (if it is present in the application context).

src/reference/antora/modules/ROOT/pages/dsl/java-flows.adoc

@@ -37,7 +37,7 @@ Starting with version 5.0.6, the generated bean names for the components in an `
 For example, the `ConsumerEndpointFactoryBean` for the `.transform("Hello "::concat)` in the preceding sample results in a bean name of `lambdaFlow.o.s.i.config.ConsumerEndpointFactoryBean#0`.
 (The `o.s.i` is a shortened from `org.springframework.integration` to fit on the page.)
 The `Transformer` implementation bean for that endpoint  has a bean name of `lambdaFlow.transformer#0` (starting with version 5.1), where instead of a fully qualified name of the `MethodInvokingTransformer` class, its component type is used.
-The same pattern is applied for all the `NamedComponent` s when the bean name has to be generated within the flow.
+The same pattern is applied for all the ``NamedComponent``s when the bean name has to be generated within the flow.
 These generated bean names are prepended with the flow ID for purposes such as parsing logs or grouping components together in some analysis tool, as well as to avoid a race condition when we concurrently register integration flows at runtime.
 See xref:dsl/java-runtime-flows.adoc[Dynamic and Runtime Integration Flows] for more information.
 

src/reference/antora/modules/ROOT/pages/filter.adoc

@@ -187,7 +187,7 @@ All of this is demonstrated in the following configuration example, where the ex
 </beans:bean>
 ----
 
-If the `ExpressionSource` bean is named `expressionSource`, you need not provide the` source` attribute on the `<expression>` element.
+If the `ExpressionSource` bean is named `expressionSource`, you need not provide the `source` attribute on the `<expression>` element.
 However, in the preceding example, we show it for completeness.
 
 The 'config/integration/expressions.properties' file (or any more-specific version with a locale extension to be resolved in the typical way that resource-bundles are loaded) can contain a key/value pair, as the following example shows:

src/reference/antora/modules/ROOT/pages/ftp/server-events.adoc

@@ -1,7 +1,7 @@
 [[ftp-server-events]]
 = Apache Mina FTP Server Events
 
-The `ApacheMinaFtplet`, added in version 5.2, listens for certain Apache Mina FTP server events and publishes them as `ApplicationEvent` s which can be received by any `ApplicationListener` bean, `@EventListener` bean method, or xref:event.adoc#appevent-inbound[Event Inbound Channel Adapter].
+The `ApacheMinaFtplet`, added in version 5.2, listens for certain Apache Mina FTP server events and publishes them as ``ApplicationEvent``s which can be received by any `ApplicationListener` bean, `@EventListener` bean method, or xref:event.adoc#appevent-inbound[Event Inbound Channel Adapter].
 
 Currently, supported events are:
 

src/reference/antora/modules/ROOT/pages/handler-advice/classes.adoc

@@ -327,7 +327,7 @@ The logic internally is based on the `CacheAspectSupport` extension, where proxy
 This advice can be configured with a SpEL expression or a `Function` to evaluate a cache key.
 The request `Message<?>` is available as the root object for the SpEL evaluation context, or as the `Function` input argument.
 By default, the `payload` of the request message is used for the cache key.
-The `CacheRequestHandlerAdvice` must be configured with `cacheNames`, when a default cache operation is a `CacheableOperation`, or with a set of any arbitrary `CacheOperation` s.
+The `CacheRequestHandlerAdvice` must be configured with `cacheNames`, when a default cache operation is a `CacheableOperation`, or with a set of any arbitrary ``CacheOperation``s.
 Every `CacheOperation` can be configured separately or have shared options, like a `CacheManager`, `CacheResolver` and `CacheErrorHandler`, can be reused from the `CacheRequestHandlerAdvice` configuration.
 This configuration functionality is similar to Spring Framework's `@CacheConfig` and `@Caching` annotation combination.
 If a `CacheManager` is not provided, a single bean is resolved by default from the `BeanFactory` in the `CacheAspectSupport`.

src/reference/antora/modules/ROOT/pages/ip/tcp-events.adoc

@@ -2,7 +2,7 @@
 = 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`, or an `@EventListener` method. 
+`TcpConnectionEvent` is a subclass of `ApplicationEvent` and can thus be received by any `ApplicationListener` defined in the `ApplicationContext`, or an `@EventListener` method.
 Also see xref:event.adoc#appevent-inbound[an event inbound channel adapter].
 
 `TcpConnectionEvents` have the following properties:
@@ -13,7 +13,7 @@ Also see xref:event.adoc#appevent-inbound[an event inbound channel adapter].
 * `source`: The `TcpConnection`.
 You can use this, for example, to determine the remote IP Address with `getHostAddress()` (cast required).
 
-Available `TcpConnectionEvent` s, related to a specific connection include: 
+Available ``TcpConnectionEvent``s, related to a specific connection include:
 
 * `TcpConnectionOpenEvent`
 * `TcpConnectionCloseEvent`

src/reference/antora/modules/ROOT/pages/ip/tcp-gateways.adoc

@@ -71,7 +71,7 @@ Consider using the `CachingClientConnectionFactory` if you wish to support concu
 
 Starting with version 5.4, the inbound can be configured with an `unsolicitedMessageChannel`.
 Unsolicited inbound messages will be sent to this channel, as well as late replies (where the client timed out).
-To support this on the server side, you can now register multiple `TcpSender` s with the connection factory.
+To support this on the server side, you can now register multiple ``TcpSender``s with the connection factory.
 Gateways and Channel Adapters automatically register themselves.
 When sending unsolicited messages from the server, you must add the appropriate `IpHeaders.CONNECTION_ID` to the messages sent.
 

src/reference/antora/modules/ROOT/pages/shutdown.adoc

@@ -12,7 +12,7 @@ Doing so lets such components prepare for shutdown.
 Examples of components that implement this interface and what they do with this call include JMS and AMQP message-driven adapters that stop their listener containers, TCP server connection factories that stop accepting new connections (while keeping existing connections open), TCP inbound endpoints that drop (log) any new messages received, and HTTP inbound endpoints that return `503 - Service Unavailable` for any new requests.
 . Stop any active channels, such as JMS- or AMQP-backed channels.
 . Stop all `MessageSource` instances.
-. Stop all inbound `MessageProducer` s (that are not `OrderlyShutdownCapable`).
+. Stop all inbound ``MessageProducer``s (that are not `OrderlyShutdownCapable`).
 . Wait for any remaining time left, as defined by the value of the `Long` parameter passed in to the operation.
 +
 Doing so lets any in-flight messages complete their journeys.

src/reference/antora/modules/ROOT/pages/zeromq.adoc

@@ -123,7 +123,7 @@ If the `unwrapTopic` option is set to `false`, the incoming message is considere
 Otherwise, by default, the `ZMsg` is considered to consist of three frames: the first one containing the topic, the last frame containing the message, with an empty frame in the middle.
 
 With `SocketType.SUB`, the `ZeroMqMessageProducer` uses the provided `topics` option for subscriptions; defaults to subscribe to all.
-Subscriptions can be adjusted at runtime using `subscribeToTopics()` and `unsubscribeFromTopics()` `@ManagedOperation` s.
+Subscriptions can be adjusted at runtime using `subscribeToTopics()` and `unsubscribeFromTopics()` ``@ManagedOperation``s.
 
 Here is a sample of `ZeroMqMessageProducer` configuration: