Fix typos and update reference links

framework-docs/modules/ROOT/pages/core/appendix/xml-custom.adoc

@@ -303,7 +303,7 @@ http\://www.mycompany.example/schema/myns=org.springframework.samples.xml.MyName
 `:` character in the URI needs to be escaped with a backslash.)
 
 The first part (the key) of the key-value pair is the URI associated with your custom
-namespace extension and needs to exactly match exactly the value of the `targetNamespace`
+namespace extension and needs to exactly match the value of the `targetNamespace`
 attribute, as specified in your custom XSD schema.
 
 [[xsd-custom-registration-spring-schemas]]

framework-docs/modules/ROOT/pages/core/appendix/xsd-schemas.adoc

@@ -584,7 +584,7 @@ for those annotations.
 
 NOTE: This element does not activate processing of Spring's
 xref:data-access/transaction/declarative/annotations.adoc[`@Transactional`] annotation;
-you can use the <<data-access.adoc#tx-decl-explained, `<tx:annotation-driven/>`>>
+you can use the xref:data-access/transaction/declarative/tx-decl-explained.adoc[`<tx:annotation-driven/>`]
 element for that purpose. Similarly, Spring's
 xref:integration/cache/annotations.adoc[caching annotations] need to be explicitly
 xref:integration/cache/annotations.adoc#cache-annotation-enable[enabled] as well.

framework-docs/modules/ROOT/pages/core/beans/definition.adoc

@@ -240,7 +240,7 @@ class should suffice. However, depending on what type of IoC you use for that sp
 bean, you may need a default (empty) constructor.
 
 The Spring IoC container can manage virtually any class you want it to manage. It is
-not limited to managing true JavaBeans. Most Spring users prefer actual JavaBeans with
+not limited to manage true JavaBeans. Most Spring users prefer actual JavaBeans with
 only a default (no-argument) constructor and appropriate setters and getters modeled
 after the properties in the container. You can also have more exotic non-bean-style
 classes in your container. If, for example, you need to use a legacy connection pool

framework-docs/modules/ROOT/pages/integration/rest-clients.adoc

@@ -110,7 +110,7 @@ Java::
 		.uri("https://example.com") <2>
 		.retrieve() <3>
 		.body(String.class); <4>
-	
+
 	System.out.println(result); <5>
 ----
 <1> Set up a GET request
@@ -127,7 +127,7 @@ Kotlin::
 		.uri("https://example.com") <2>
 		.retrieve() <3>
 		.body<String>() <4>
-	
+
 	println(result) <5>
 ----
 <1> Set up a GET request
@@ -149,7 +149,7 @@ Java::
 		.uri("https://example.com") <1>
 		.retrieve()
 		.toEntity(String.class); <2>
-	
+
 	System.out.println("Response status: " + result.getStatusCode()); <3>
 	System.out.println("Response headers: " + result.getHeaders()); <3>
 	System.out.println("Contents: " + result.getBody()); <3>
@@ -166,7 +166,7 @@ Kotlin::
 		.uri("https://example.com") <1>
 		.retrieve()
 		.toEntity<String>() <2>
-	
+
 	println("Response status: " + result.statusCode) <3>
 	println("Response headers: " + result.headers) <3>
 	println("Contents: " + result.body) <3>
@@ -495,7 +495,7 @@ By default, it uses the `SimpleClientHttpRequestFactory`, but this can be change
 See <<rest-request-factories>>.
 
 NOTE: `RestTemplate` can be instrumented for observability, in order to produce metrics and traces.
-See the xref:integration/observability.adoc#http-client.resttemplate[RestTemplate Observability support] section.
+See the xref:integration/observability.adoc#observability.http-client.resttemplate[RestTemplate Observability support] section.
 
 [[rest-template-body]]
 === Body

framework-docs/modules/ROOT/pages/languages/kotlin/spring-projects-in.adoc

@@ -181,7 +181,7 @@ such bean by name, or add `@JvmName("sampleBean")` to disable name mangling.
 [[injecting-configuration-properties]]
 == Injecting Configuration Properties
 
-In Java, you can inject configuration properties by using annotations (such as pass:q[`@Value("${property}")`)].
+In Java, you can inject configuration properties by using annotations (such as pass:q[`@Value("${property}")`]).
 However, in Kotlin, `$` is a reserved character that is used for
 {kotlin-docs}/idioms.html#string-interpolation[string interpolation].
 
@@ -357,7 +357,7 @@ file with a `spring.test.constructor.autowire.mode = all` property.
 	class OrderServiceIntegrationTests(
 					val orderService: OrderService,
 					val customerService: CustomerService) {
-	
+
 		// tests that use the injected OrderService and CustomerService
 	}
 ----
@@ -414,19 +414,19 @@ class support. The following example shows how to do so:
 [source,kotlin,indent=0]
 ----
 	class SpecificationLikeTests {
-	
+
 		@Nested
 		@DisplayName("a calculator")
 		inner class Calculator {
 
 			val calculator = SampleCalculator()
-	
+
 			@Test
 			fun `should return the result of adding the first number to the second number`() {
 				val sum = calculator.sum(2, 4)
 				assertEquals(6, sum)
 			}
-	
+
 			@Test
 			fun `should return the result of subtracting the second number from the first number`() {
 				val subtract = calculator.subtract(4, 2)

framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/context-pausing.adoc

@@ -32,14 +32,16 @@ For example, if you want inactive application contexts to always be paused, you
 switch from the default `ON_CONTEXT_SWITCH` mode to `ALWAYS` by setting the
 `spring.test.context.cache.pause` system property to `always`.
 
-```shell
+[source,shell]
+----
 -Dspring.test.context.cache.pause=always
-```
+----
 Similarly, if you encounter issues with `Lifecycle` components that cannot or should not
 opt out of pausing, or if you discover that your test suite runs more slowly due to the
 pausing and restarting of application contexts, you can disable the pausing feature by
 setting the `spring.test.context.cache.pause` system property to `never`.
 
-```shell
+[source,shell]
+----
 -Dspring.test.context.cache.pause=never
-```
+----