From f35d29438ac875d31f528e553989dc93ec1556fb Mon Sep 17 00:00:00 2001
From: Bart Koelman <104792814+bart-vmware@users.noreply.github.com>
Date: Tue, 3 Mar 2026 12:09:58 +0100
Subject: [PATCH] Fix broken documentation in Steeltoe 4.x

---
 .../Configuration/ConfigurationServiceCollectionExtensions.cs | 4 ++--
 .../Endpoint/Actuators/Health/Availability/LivenessState.cs   | 3 ++-
 .../Endpoint/Actuators/Health/Availability/ReadinessState.cs  | 3 ++-
 3 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/Discovery/src/Configuration/ConfigurationServiceCollectionExtensions.cs b/src/Discovery/src/Configuration/ConfigurationServiceCollectionExtensions.cs
index 03ad09ee9d..4d5bd83405 100644
--- a/src/Discovery/src/Configuration/ConfigurationServiceCollectionExtensions.cs
+++ b/src/Discovery/src/Configuration/ConfigurationServiceCollectionExtensions.cs
@@ -19,7 +19,7 @@ public static class ConfigurationServiceCollectionExtensions
     /// Build your list of service instances under the configuration prefix discovery:services.
     /// <example>
     /// Example configuration in appsettings.json:
-    /// <![CDATA[
+    /// <code><![CDATA[
     /// {
     ///   "discovery": {
     ///     "services": [
@@ -37,7 +37,7 @@ public static class ConfigurationServiceCollectionExtensions
     ///     ]
     ///   }
     /// }
-    /// ]]>
+    /// ]]></code>
     /// </example>
     /// </remarks>
     /// <param name="services">
diff --git a/src/Management/src/Endpoint/Actuators/Health/Availability/LivenessState.cs b/src/Management/src/Endpoint/Actuators/Health/Availability/LivenessState.cs
index e19bbbb7eb..e0e609983d 100644
--- a/src/Management/src/Endpoint/Actuators/Health/Availability/LivenessState.cs
+++ b/src/Management/src/Endpoint/Actuators/Health/Availability/LivenessState.cs
@@ -6,9 +6,10 @@ namespace Steeltoe.Management.Endpoint.Actuators.Health.Availability;
 
 /// <summary>
 /// "Liveness" state of the application.
-/// <para />
+/// <para>
 /// An application is considered live when it's running with a correct internal state. "Liveness" failure means that the internal state of the
 /// application is broken, and we cannot recover from it. As a result, the platform should restart the application.
+/// </para>
 /// </summary>
 public sealed class LivenessState : AvailabilityState
 {
diff --git a/src/Management/src/Endpoint/Actuators/Health/Availability/ReadinessState.cs b/src/Management/src/Endpoint/Actuators/Health/Availability/ReadinessState.cs
index b4371f9898..4169a69ae7 100644
--- a/src/Management/src/Endpoint/Actuators/Health/Availability/ReadinessState.cs
+++ b/src/Management/src/Endpoint/Actuators/Health/Availability/ReadinessState.cs
@@ -6,9 +6,10 @@ namespace Steeltoe.Management.Endpoint.Actuators.Health.Availability;
 
 /// <summary>
 /// The Readiness state of the application.
-/// <para />
+/// <para>
 /// An application is considered ready when it's <see cref="LivenessState.Correct" /> and willing to accept traffic. "Readiness" failure means that the
 /// application is not able to accept traffic and that the infrastructure should not route requests to it.
+/// </para>
 /// </summary>
 public sealed class ReadinessState : AvailabilityState
 {