From 866de207f550a4531638da40c0a00122cb9ad2e9 Mon Sep 17 00:00:00 2001
From: Sam Brannen <104798+sbrannen@users.noreply.github.com>
Date: Mon, 18 Nov 2024 16:12:31 +0100
Subject: [PATCH] Link to JEP 400

---
 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 dc63c1f..9dd68a8 100644
--- a/Date-and-Time-Formatting-with-JDK-20-and-higher.md
+++ b/Date-and-Time-Formatting-with-JDK-20-and-higher.md
@@ -4,7 +4,7 @@ This Wiki page discusses locale-sensitive formatting and parsing issues that dev
 
 Specifically, this document provides background information on changes in the JDK as well as guidance on how to address formatting and parsing issues encountered in Spring applications.
 
-Before you read any further, we highly recommend that you first read [JEP 252: Use CLDR Locale Data by Default](https://openjdk.org/jeps/252).
+Before you read any further, we highly recommend that you first read [JEP 252: Use CLDR Locale Data by Default](https://openjdk.org/jeps/252) and [JEP 400: UTF-8 by Default](https://openjdk.org/jeps/400).
 
 Although this document primarily focuses on issues related to time formats for the US English locale (for example, `3:30 PM`), numerous other use cases may potentially be affected by locale-sensitive formats for dates, times, currencies, time zones, etc. provided by the [Unicode Common Locale Data Repository (CLDR) project](https://cldr.unicode.org/).