chore: update formatting on trace update docs

Author: Steffen911

pages/faq/all/tracing-data-updates.mdx

@@ -22,8 +22,8 @@ UI-based updates ([tags](/docs/observability/features/tags), bookmarks, [publish
 **Via SDK or Ingestion API**
 
 - You can upsert traces, observations, and scores based on their `id` (and, optionally, `timestamp` for traces, `startTime` for observations, and `timestamp` for scores, respectively).
-- Within 60 days of creation, updates will be merged into the existing trace, observation, or score.
-- After 60 days, updates may create duplicate entries containing only the changed fields. This can lead to inconsistencies in dashboards and historical filtering.
+- **Within 60 days of creation**, updates will be merged into the existing trace, observation, or score.
+- **After 60 days**, updates may create duplicate entries containing only the changed fields. This can lead to inconsistencies in dashboards and historical filtering.
 - Sending a full event with `id`, same `timestamp/startTime`, and all desired properties will always replace the existing record instead of producing a duplicate and is recommended for long-term updates.
 
 **Example behaviour**