From f6383f239e83d55fec3f0db456ac0210c1eac9f7 Mon Sep 17 00:00:00 2001
From: Spring Builds <builds@springframework.org>
Date: Thu, 8 Feb 2024 17:28:10 -0500
Subject: [PATCH] Fix typos and broken links in docs

---
 src/reference/antora/modules/ROOT/pages/codec.adoc     |  3 +--
 .../antora/modules/ROOT/pages/content-enrichment.adoc  | 10 +++++-----
 .../antora/modules/ROOT/pages/endpoint-summary.adoc    |  4 ++--
 3 files changed, 8 insertions(+), 9 deletions(-)

diff --git a/src/reference/antora/modules/ROOT/pages/codec.adoc b/src/reference/antora/modules/ROOT/pages/codec.adoc
index 2871876298..1e8c4531d5 100644
--- a/src/reference/antora/modules/ROOT/pages/codec.adoc
+++ b/src/reference/antora/modules/ROOT/pages/codec.adoc
@@ -94,7 +94,7 @@ You can override these framework defaults by configuring the registrars mentione
 ==== Using a Custom Kryo Serializer
 
 If you need custom serialization, see the https://github.com/EsotericSoftware/kryo[Kryo] documentation, because you need to use the native API to do the customization.
-For an example, see the https://github.com/spring-projects/spring-integration/blob/main/spring-integration-core/src/main/java/org/springframework/integration/codec/kryo/MessageCodec.java[`MessageCodec`] implementation.
+For an example, see the `org.springframework.integration.codec.kryo.MessageCodec` implementation.
 
 [[implementing-kryoserializable]]
 ==== Implementing KryoSerializable
@@ -107,7 +107,6 @@ The following example shows a custom Kryo serializer:
 [source,java]
 ----
 public class Address implements KryoSerializable {
-    ...
 
     @Override
     public void write(Kryo kryo, Output output) {
diff --git a/src/reference/antora/modules/ROOT/pages/content-enrichment.adoc b/src/reference/antora/modules/ROOT/pages/content-enrichment.adoc
index e6e31159e2..9c49bf2e62 100644
--- a/src/reference/antora/modules/ROOT/pages/content-enrichment.adoc
+++ b/src/reference/antora/modules/ROOT/pages/content-enrichment.adoc
@@ -106,7 +106,7 @@ You can similarly point to a Groovy script, as the following example shows:
 [[spel-support]]
 === SpEL Support
 
-In Spring Integration 2.0, we introduced the convenience of the https://docs.spring.io/spring/docs/current/spring-framework-reference/core.html#expressions[Spring Expression Language (SpEL)] to help configure many different components.
+In Spring Integration 2.0, we introduced the convenience of the https://docs.spring.io/spring-framework/reference/core/expressions.html[Spring Expression Language (SpEL)] to help configure many different components.
 The header enricher is one of them.
 Look again at the POJO example shown earlier.
 You can see that the computation logic to determine the header value is pretty simple.
@@ -182,7 +182,7 @@ Starting with Spring Integration 3.0, a new sub-element `<int:header-channels-to
 It has no attributes.
 This new sub-element converts existing `replyChannel` and `errorChannel` headers (when they are a `MessageChannel`) to a `String` and stores the channels in a registry for later resolution, when it is time to send a reply or handle an error.
 This is useful for cases where the headers might be lost -- for example, when serializing a message into a message store or when transporting the message over JMS.
-If the header does not already exist or it is not a `MessageChannel`, no changes are made.
+If the header does not already exist, or it is not a `MessageChannel`, no changes are made.
 
 Using this functionality requires the presence of a `HeaderChannelRegistry` bean.
 By default, the framework creates a `DefaultHeaderChannelRegistry` with the default expiry (60 seconds).
@@ -365,7 +365,7 @@ The enricher's `request-channel` attribute is configured to pass the `User` to t
 
 Through the implicitly set `reply-channel`, a `User` object is returned and, by using the `property` sub-element, properties from the reply are extracted and used to enrich the original payload.
 
-[[how-do-i-pass-only-a-subset-of-data-to-the-request-channel?]]
+[[how-do-i-pass-only-a-subset-of-data-to-the-request-channel]]
 === How Do I Pass Only a Subset of Data to the Request Channel?
 
 When using a `request-payload-expression` attribute, a single property of the payload instead of the full message can be passed on to the request channel.
@@ -384,7 +384,7 @@ In the following example, the username property is passed on to the request chan
 
 Keep in mind that, although only the username is passed, the resulting message to the request channel contains the full set of `MessageHeaders`.
 
-[[how-can-i-enrich-payloads-that-consist-of-collection-data?]]
+[[how-can-i-enrich-payloads-that-consist-of-collection-data]]
 ==== How Can I Enrich Payloads that Consist of Collection Data?
 
 In the following example, instead of a `User` object, a `Map` is passed in:
@@ -403,7 +403,7 @@ The `Map` contains the username under the `username` map key.
 Only the `username` is passed on to the request channel.
 The reply contains a full `User` object, which is ultimately added to the `Map` under the `user` key.
 
-[[how-can-i-enrich-payloads-with-static-information-without-using-a-request-channel?]]
+[[how-can-i-enrich-payloads-with-static-information-without-using-a-request-channel]]
 === How Can I Enrich Payloads with Static Information without Using a Request Channel?
 
 The following example does not use a request channel at all but solely enriches the message's payload with static values:
diff --git a/src/reference/antora/modules/ROOT/pages/endpoint-summary.adoc b/src/reference/antora/modules/ROOT/pages/endpoint-summary.adoc
index 6c2b9adf01..fd67924425 100644
--- a/src/reference/antora/modules/ROOT/pages/endpoint-summary.adoc
+++ b/src/reference/antora/modules/ROOT/pages/endpoint-summary.adoc
@@ -119,8 +119,8 @@ The following table summarizes the various endpoints with quick links to the app
 | xref:jdbc/outbound-gateway.adoc[Outbound Gateway] and xref:jdbc/stored-procedures.adoc#stored-procedure-outbound-gateway[Stored Procedure Outbound Gateway]
 
 | *JMS*
-| xref:changes-3.0-4.0.adoc#x4.0-jms-ib[Inbound Channel Adapter] and xref:changes-2.2-3.0.adoc#x3.0-jms-mdca-te[Message-driven Channel Adapter]
-| xref:changes-3.0-4.0.adoc#x4.0-jms-ob[Outbound Channel Adapter]
+| xref:jms.adoc#jms-inbound-channel-adapter[Inbound Channel Adapter] and xref:jms.adoc#jms-message-driven-channel-adapter[Message-driven Channel Adapter]
+| xref:jms.adoc#jms-outbound-channel-adapter[Outbound Channel Adapter]
 | xref:jms.adoc#jms-inbound-gateway[Inbound Gateway]
 | xref:jms.adoc#jms-outbound-gateway[Outbound Gateway]