From 3ddf7da545c3c038a101c00838cd8741aa6fc067 Mon Sep 17 00:00:00 2001
From: Sam Brannen <104798+sbrannen@users.noreply.github.com>
Date: Mon, 21 Oct 2024 15:56:37 +0200
Subject: [PATCH] Highlight key recommendations.

---
 Date-and-Time-Formatting-with-JDK-20-and-higher.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Date-and-Time-Formatting-with-JDK-20-and-higher.md b/Date-and-Time-Formatting-with-JDK-20-and-higher.md
index d961510..5f44456 100644
--- a/Date-and-Time-Formatting-with-JDK-20-and-higher.md
+++ b/Date-and-Time-Formatting-with-JDK-20-and-higher.md
@@ -26,7 +26,7 @@ The Spring team recommends the use of ISO standardized formats for both parsing
 
 Another option is to always use date/time formatting patterns that you control. In other words, instead of relying on predefined locale-sensitive patterns such as `@DateTimeFormat(style = "-M")`  or `java.time.format.FormatStyle.MEDIUM` to parse or format a time, define your own date/time pattern that parses and formats times the way you expect – for example, `"HH:mm a"` to handle US English times such as `3:30 PM`.
 
-Using an ISO standardized format or a concrete pattern that you control allows for reliable system-independent and locale-independent parsing and formatting of date/time values. However, if that is not an option for your use case, consider one of the _lenient_ approaches outlined below.
+**Using an ISO standardized format or a concrete pattern that you control allows for reliable system-independent and locale-independent parsing and formatting of date/time values.** However, if that is not an option for your use case, consider one of the _lenient_ approaches outlined below.
 
 The Spring team also recommends the use of UTF encoding whenever possible – for example, `UTF-8`.