From 21ee5b13f0672990c807475ba094092d19dd6dc5 Mon Sep 17 00:00:00 2001
From: Philip Chimento <pchimento@igalia.com>
Date: Tue, 30 Aug 2022 18:13:06 -0700
Subject: [PATCH] Editorial: Remove note about normative intention

With the addition of DefaultTimeZone to ECMA-262, there should be nothing
left to define from this note.

Closes: #519
---
 spec/timezone.html | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/spec/timezone.html b/spec/timezone.html
index 4fd3b844bf..bf92c84151 100644
--- a/spec/timezone.html
+++ b/spec/timezone.html
@@ -8,13 +8,6 @@ <h1>Temporal.TimeZone Objects</h1>
   <emu-clause id="sec-time-zone-names">
     <h1>Time Zone Names</h1>
 
-    <emu-note type="editor">
-      <p>
-        The normative intention of this section is that an implementation must support UTC and a local time zone, which may also be UTC, or a named time zone like *"Europe/London"*, or an offset time zone like *"+01:00"*; and that the local time zone must in any case be consistent with the time zone offsets that can be determined using `Date.prototype.getTimezoneOffset()`, `Date.prototype.toString()`, and `Date.prototype.toTimeString()`.
-        The exact formal definition of "local time zone" is still to be determined.
-      </p>
-    </emu-note>
-
     <p>
       An ECMAScript implementation must support a number of built-in time zones.
       At a minimum, implementations must support a built-in time zone named *"UTC"*.