docs: make “implementer” wording consistent, replace exclamation point

source

@@ -4376,7 +4376,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
 
   <div w-nodev>
 
-  <p class="note">Implementors are strongly urged to carefully examine any third-party libraries
+  <p class="note">Implementers are strongly urged to carefully examine any third-party libraries
   they might consider using to implement the parsing of syntaxes described below. For example, date
   libraries are likely to implement error handling behavior that differs from what is required in
   this specification, since error-handling behavior is often not defined in specifications that
@@ -5048,7 +5048,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
 
   <p class="note">While the formats described here are intended to be subsets of the corresponding
   ISO8601 formats, this specification defines parsing rules in much more detail than ISO8601.
-  Implementors are therefore encouraged to carefully examine any date parsing libraries before using
+  Implementers are therefore encouraged to carefully examine any date parsing libraries before using
   them to implement the parsing rules described below; ISO8601 libraries might not parse dates and
   times in exactly the same manner. <ref spec=ISO8601></p>
 
@@ -33588,7 +33588,7 @@ interface <dfn interface>MediaError</dfn> {
   the user agent is confident that the type represents a <span>media resource</span> that it can
   render if used in with this <code>audio</code> or <code>video</code> element; and it must return
   "<dfn enum-value for="CanPlayTypeResult"><code
-  data-x="dom-CanPlayTypeResult-maybe">maybe</code></dfn>" otherwise. Implementors are encouraged to
+  data-x="dom-CanPlayTypeResult-maybe">maybe</code></dfn>" otherwise. Implementers are encouraged to
   return "<code data-x="dom-CanPlayTypeResult-maybe">maybe</code>" unless the type can be
   confidently established as being supported or not. Generally, a user agent should never return
   "<code data-x="dom-CanPlayTypeResult-probably">probably</code>" for a type that allows the <code
@@ -37496,7 +37496,7 @@ interface <dfn interface>VideoTrack</dfn> {
 
     <p class="critical">This specification does not currently say whether or how to check the MIME
     types of text tracks, or whether or how to perform file type sniffing using the actual file
-    data. Implementors differ in their intentions on this matter and it is therefore unclear what
+    data. Implementers differ in their intentions on this matter and it is therefore unclear what
     the right solution is. In the absence of any requirement here, the HTTP specifications' strict
     requirement to follow the Content-Type header prevails ("Content-Type specifies the media type
     of the underlying data." ... "If and only if the media type is not given by a Content-Type
@@ -40060,7 +40060,7 @@ interface <dfn interface>HTMLTableElement</dfn> : <span>HTMLElement</span> {
      <td>Not a good indicator (both layout and non-layout tables have historically been given this attribute)
   </table>
 
-  <p class="note">It is quite possible that the above suggestions are wrong. Implementors are urged
+  <p class="note">It is quite possible that the above suggestions are wrong. Implementers are urged
   to provide feedback elaborating on their experiences with trying to create a layout table
   detection heuristic.</p>
 
@@ -97171,7 +97171,7 @@ interface <dfn interface>Navigator</dfn> {
   handler using URL data considered private. They might do so with the expectation that the user's
   choice of handler points to a page inside the organization, ensuring that sensitive data will not
   be exposed to third parties. However, a user may have registered a handler pointing to an
-  external site, resulting in a data leak to that third party. Implementors might wish to consider
+  external site, resulting in a data leak to that third party. Implementers might wish to consider
   allowing administrators to disable custom handlers on certain subdomains, content types, or
   schemes.</p>
 
@@ -98788,7 +98788,7 @@ dictionary <dfn dictionary>EventSourceInit</dfn> {
   data-x="dom-EventSource-CLOSED">CLOSED</code> and <span data-x="concept-event-fire">fires an
   event</span> named <code data-x="event-error">error</code> at the <code>EventSource</code> object.
   <strong>Once the user agent has <span data-x="fail the connection">failed the connection</span>,
-  it does <em>not</em> attempt to reconnect!</strong></p>
+  it does <em>not</em> attempt to reconnect.</strong></p>
 
   <hr>
 
@@ -100162,7 +100162,7 @@ function receiver(e) {
   post arbitrary events (using <code data-x="">dispatchEvent()</code> or otherwise) to objects in
   other origins (those that are not the <span data-x="same origin">same</span>).</p>
 
-  <p class="note">Implementors are urged to take extra care in the implementation of this feature.
+  <p class="note">Implementers are urged to take extra care in the implementation of this feature.
   It allows authors to transmit information from one domain to another domain, which is normally
   disallowed for security reasons. It also requires that UAs be careful to allow access to certain
   properties but not others.</p>