Merge remote-tracking branch 'origin/main'

README.md

@@ -219,7 +219,7 @@ try {
 There are an endless amount of APIs with non-standard date/time exchange, and the goal of this project is to make it a
 no-brainer to do-the-right-thing(c).
 
-### Why the performance optimized version?
+### Why the performance docus?
 
 Some projects use epoch time-stamps for date-time exchange, and from a performance perspective this *may* make sense
 in *some* cases. With this project one can do-the-right-thing and maintain performance in date-time handling.
@@ -275,4 +275,4 @@ well.
 Since Java's `java.time` classes do not support storing leap seconds, ITU will throw a `LeapSecondException` if one is
 encountered to signal that this is a leap second. The exception can then be queried for the second-value. Storing such
 values is not possible in a `java.time.OffsetDateTime`, the `60` is therefore abandoned and the date-time will use `59`
-instead of `60`.
+instead of `60`.