Resolve more @ptomato review comments

Author: justingrant

spec/intl.html

@@ -86,7 +86,7 @@ <h1>Time Zone Identifiers</h1>
           It is recommended that implementations maintain a fully consistent copy of the IANA Time Zone Database for the lifetime of each agent.
           If implementations do revise time zone information during the lifetime of an agent, then it is recommended that changes to time zone data, including which identifiers are supported, the primary time zone identifier associated with any identifier, and the UTC offsets and transitions associated with any Zone, can be incorporated into an agent only if they are consistent with results already observed by all ECMAScript code that can reach that agent.
           For example, it is recommended that a new identifier can be incorporated only if no ECMAScript code has already tried to use it, and it is recommended that replacement of a primary identifier with a Link to a different identifier can only be incorporated only if no ECMAScript code has already resulted in resolving it as primary.
-          The complexity of maintaining such invariants is why it is recommended that implementations maintain a fully consistent copy of the IANA Time Zone Database for the lifetime of each agent.
+          Due to the complexity of supporting these recommendations, it is recommended that implementations maintain a fully consistent copy of the IANA Time Zone Database for the lifetime of each agent.
         </p>
 
         <emu-note>
@@ -183,7 +183,7 @@ <h1>AvailableTimeZoneIdentifiers ( ): a List of Time Zone Identifier Records</h1
         <emu-note>
           Time zone identifiers in the IANA Time Zone Database can change over time.
           At a minimum, it is recommended that implementations limit changes to the result of AvailableTimeZoneIdentifiers to the changes allowed by GetAvailableTimeZoneIdentifier, for the lifetime of the surrounding agent.
-          Due to the complexity of supporting these requirements, it is recommended that the result of AvailableTimeZoneIdentifiers remains the same for the lifetime of the surrounding agent.
+          Due to the complexity of supporting these recommendations, it is recommended that the result of AvailableTimeZoneIdentifiers remains the same for the lifetime of the surrounding agent.
         </emu-note>
 
         <p>This definition supersedes the definition provided in <emu-xref href="#sec-availabletimezoneidentifiers"></emu-xref>.</p>

spec/timezone.html

@@ -124,7 +124,7 @@ <h1>
       <emu-note>
         Given the same value of _timeZoneIdentifier_ or any value that is an ASCII-case-insensitive match for it, it is recommended that the resulting Time Zone Identifier Record contain the same property values for the lifetime of the surrounding agent.
         Furthermore, it is recommended that time zone identifiers do not dynamically change from primary to non-primary, meaning that if _timeZoneIdentifier_ is a case-insensitive match for the [[PrimaryIdentifier]] property of the result of a previous call to GetAvailableTimeZoneIdentifier, then GetAvailableTimeZoneIdentifier(_timeZoneIdentifier_) will return a record where [[Identifier]] is [[PrimaryIdentifier]].
-        Due to the complexity of supporting these requirements, it is recommended that the result of AvailableTimeZoneIdentifiers (and therefore GetAvailableTimeZoneIdentifier) remains the same for the lifetime of the surrounding agent.
+        Due to the complexity of supporting these recommendations, it is recommended that the result of AvailableTimeZoneIdentifiers (and therefore GetAvailableTimeZoneIdentifier) remains the same for the lifetime of the surrounding agent.
       </emu-note>
     </emu-clause>