review feedback

Author: yihuiliao

packages/dev/docs/pages/blog/rtl-date-time.mdx

@@ -20,7 +20,7 @@ import keyboardVideoURL from 'url:../assets/rtl-keyboard.mp4';
 keywords: [date picker, date, time, calendar, components, accessibility, react spectrum, react, spectrum]
 description: Internationalization is a core feature of our Date and Time components. We support 13 different calendar systems as well as locale-specific formatting, number systems, and 12 and 24 hour time. However, we identified an issue with our right-to-left support where in some right-to-left (RTL) languages, the format of the date and time fields was incorrect. While investigating this bug, we faced several challenges in ensuring proper date and time representation in RTL languages and implemented various strategies that we’d like to share.
 
-date: 2025-03-30
+date: 2025-05-30
 author: '[Yihui Liao](https://github.com/yihuiliao)'
 ---
 
@@ -57,7 +57,7 @@ Below is an example of how the dates were being formatted based on user-entered
 
 We first addressed time fields since they were easier to fix. As mentioned earlier, the segments in time fields for RTL languages were flipped. We learned that regardless of locale, all time fields should follow the `HH:MM` format. Knowing this, we could apply a direction of left-to-right (LTR) on the numeric values across all segments in a time field. We could do this by wrapping the time field in a `<bdo>` tag and setting the `dir` attribute to `ltr` which would override the current text direction from `rtl` to `ltr`. 
 
-However, instead of changing the DOM structure and introducing potential side effects, we chose to use the [LRI (left-to-right isolate) Unicode character](https://www.w3.org/International/questions/qa-bidi-unicode-controls) to encapsulate the time segments and force an LTR direction. This sets the text direction to `ltr` and isolates the time field from the surrounding text. Adding this Unicode character is the equivalent of wrapping the time segments in a `<bdo>` tag but offers several advantages. Since the character is invisible, there are no visual changes, and by adding it as a siblings to the segments, we avoided major structural changes to the DOM. Additionally, by enforcing a LTR direction, we no longer had to worry about whether the time field consisted of placeholders or numeric values. Lastly, it ensured that when a date field included a time, that the time field appeared in the correct order with respect to the date field (e.g. `8:45 1/31/2025` instead of `1/31/2025 8:45`).
+However, instead of changing the DOM structure and introducing potential side effects, we chose to use the [LRI (left-to-right isolate) Unicode character](https://www.w3.org/International/questions/qa-bidi-unicode-controls) to encapsulate the time segments and force an LTR direction. This sets the text direction to `ltr` and isolates the time field from the surrounding text. Adding this Unicode character is the equivalent of wrapping the time segments in a `<bdo>` tag but offers several advantages. Since the character is invisible, there are no visual changes, and by adding it as a sibling to the segments, we avoided major structural changes to the DOM. Additionally, by enforcing a LTR direction, we no longer had to worry about whether the time field consisted of placeholders or numeric values. Lastly, it ensured that when a date field included a time, that the time field appeared in the correct order with respect to the date field (e.g. `8:45 1/31/2025` instead of `1/31/2025 8:45`).
 
 Below is a simplified code example of how we utilize Unicode characters to enforce an left-to-right direction on the segments:
 
@@ -100,9 +100,13 @@ However, this assumption proved too broad. In some locales, such as Arabic (`ar-
 // An example of a date field in he-IL
 <div>
   <span aria-label="day">3</span>
+  {/*- begin highlight -*/}
   <span>.</span>
+  {/*- end highlight -*/}
   <span aria-label="month">11</span>
-  <span>.</span>  
+  {/*- begin highlight -*/}
+  <span>.</span>
+  {/*- end highlight -*/}
   <span aria-label="year">2020</span>
 </div>
 ```