Update messages about landing ZonedDateTime

The message is no longer accurate, since ZonedDateTime itself has landed already. Change it to say which methods are as yet unimplemented.
tc39 · Nov 3, 2020 · a368ad3 · a368ad3
1 parent 1a3b00d
commit a368ad3
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/docs/README.md b/docs/README.md
@@ -50,7 +50,7 @@ See [Temporal.Instant Documentation](./instant.md) for detailed documentation.
 
 ### **Temporal.ZonedDateTime**
 
-_NOTE: this type is not checked into the polyfill yet, but is planned to land in late October 2020._
+_NOTE: Not all methods of this type are available in the polyfill yet._
 
 A `Temporal.ZonedDateTime` is a timezone-aware, calendar-aware date/time type that represents a real event that has happened (or will happen) at a particular exact time from the perspective of a particular region on Earth.
 This type is optimized for use cases that require a time zone, including DST-safe arithmetic and interoperability with RFC 5545 (iCalendar).

diff --git a/docs/zoneddatetime.md b/docs/zoneddatetime.md
@@ -5,8 +5,7 @@
 <!-- toc -->
 </details>
 
-> **NOTE**: This type has been approved and will be merged soon (targeting late October 2020), but it's not in current builds yet.
-> If you have feedback about this new type, visit https://github.com/tc39/proposal-temporal/issues/700.
+> **NOTE**: The `with()`, `until()`, and `since()` methods of this type are not available in the polyfill yet.
 
 A `Temporal.ZonedDateTime` is a timezone-aware, calendar-aware date/time type that represents a real event that has happened (or will happen) at a particular instant from the perspective of a particular region on Earth.
 As the broadest `Temporal` type, `Temporal.ZonedDateTime` can be considered a combination of `Temporal.TimeZone`, `Temporal.Instant`, and `Temporal.DateTime` (which includes `Temporal.Calendar`).