diff --git a/specification/appendix-d-observability.md b/specification/appendix-d-observability.md
index 0a35385d..0c2376a4 100644
--- a/specification/appendix-d-observability.md
+++ b/specification/appendix-d-observability.md
@@ -61,9 +61,9 @@ Telemetry hooks can emit OpenTelemetry signals in three distinct ways:
 
 | Pattern                                                                            | Advantages                                                                                                                                                                                | Disadvantages                                                                                                                                                                                          |
 | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **Span Events**</br>![recommended](https://img.shields.io/badge/recommended-green) | - Leverages existing trace configuration and tooling</br> - Minimal overhead, no additional spans created</br> - Maintains trace context relationships</br> - Simpler than creating spans | - Requires an active span to function</br> - Must gracefully handle absence of active span</br> - Limited to span lifetime and context.                                                                |
-| **Event Logging**                                                                  | - Works independently without active spans</br> - Aligns with OpenTelemetry's emerging direction</br> - Suitable for environments without tracing</br> - Simpler implementation model     | - Requires an event exporter to be configured</br> - Processed and stored separately from spans</br> - Event logging standards still evolving                                                         |
-| **Standalone Spans**                                                               | - Distributed traces contain every evaluation</br> - Detailed timing information</br> - Full span lifecycle control                                                                       | - Creates one span per evaluation</br> - May clutter trace visualizations</br> - Increased overhead and resource usage</br> - Potential performance impact at scale</br> - More complex implementation |
+| **Span Events**<br />![recommended](https://img.shields.io/badge/recommended-green) | <ul><li>Leverages existing trace configuration and tooling</li><li>Minimal overhead, no additional spans created</li><li>Maintains trace context relationships</li><li>Simpler than creating spans</li></ul> | <ul><li>Requires an active span to function</li><li>Must gracefully handle absence of active span</li><li>Limited to span lifetime and context.</li></ul> |
+| **Event Logging**                                                                  | <ul><li>Works independently without active spans</li><li>Aligns with OpenTelemetry's emerging direction</li><li>Suitable for environments without tracing</li><li>Simpler implementation model</li></ul>     | <ul><li>Requires an event exporter to be configured</li><li>Processed and stored separately from spans</li><li>Event logging standards still evolving</li></ul>                                                         |
+| **Standalone Spans**                                                               | <ul><li>Distributed traces contain every evaluation</li><li>Detailed timing information</li><li>Full span lifecycle control</li></ul>                                                                       | <ul><li>Creates one span per evaluation</li><li>May clutter trace visualizations</li><li>Increased overhead and resource usage</li><li>Potential performance impact at scale</li><li>More complex implementation</li></ul> |
 
 > [!NOTE]
 > While span events are recommended for their low overhead and ease of use, OpenTelemetry is trending toward using log-based events instead of span events. Please refer to the [OpenTelemetry Span Event Deprecation Plan][otel-span-event-deprecation-plan] for more details.