Update the explainer

Signed-off-by: Zoltan Kis <[email protected]>

Author: zolkis

EXPLAINER.md

@@ -92,17 +92,17 @@ when required, about granting access to Web NFC. It means sending and receiving
 info when users tap NFC devices can be done smoothly once permission is granted.
 
 ```js
-const reader = new NDEFReader();
+const ndef = new NDEFReader();
 
 async function startScanning() {
-  await reader.scan();
-  reader.onreading = event => {
+  await ndef.scan();
+  ndef.onreading = event => {
     /* handle NDEF messages */
   };
 }
 
 const nfcPermissionStatus = await navigator.permissions.query({ name: "nfc" });
-if (permissionStatus.state === "granted") {
+if (nfcPermissionStatus.state === "granted") {
   // NFC access was previously granted, so we can start NFC scanning now.
   startScanning();
 } else {
@@ -126,10 +126,10 @@ cases where the text might even be in UTF-16 do to existing real life
 implementations.
 
 ```js
-const reader = new NDEFReader();
+const ndef = new NDEFReader();
 
-await reader.scan({ recordType: "example.com:smart-poster" });
-reader.onreading = event => {
+await ndef.scan({ recordType: "example.com:smart-poster" });
+ndef.onreading = event => {
   const externalRecord = event.message.records.find(
     record => record.type == "example.com:smart-poster"
   );
@@ -166,7 +166,7 @@ abortController.signal.onabort = event => {
 const ndef = new NDEFReader();
 await ndef.scan({ signal: abortController.signal });
 
-await ndef.push("foo", { signal: abortController.signal });
+await ndef.write("foo", { signal: abortController.signal });
 
 document.querySelector("#abortButton").onclick = event => {
   abortController.abort();
@@ -227,12 +227,10 @@ same API, and have it loaded as a separate module. People working on Web
 Assembly are also advocating for this patterns as it might be able to turn such
 globals into modules in the future, at least when accessed from WASM.
 
-### Separate objects for reader/writer
+### Common vs separate objects for reader/writer
 
-The reader and writer objects could have been merged into one single object, but
-as we allow multiple scans with filters to be active at the same time (maybe in
-multiple places/view of the app/site) then it makes more sense to be able to use
-separate objects.
+The reader and writer objects existed separately when scan filters were supported,
+but after filters have been abandoned, they have been merged into one single object.
 
 ## Considered alternatives
 

index.html

@@ -1105,7 +1105,7 @@ <h4>
     </p>
     <pre class="example">
       const ndef = new NDEFReader();
-      ndef.onreading(event => console.log("We read a tag!"));
+      ndef.onreading = event => console.log("We read a tag!"));
 
       function write(data, { timeout } = {}) {
         return new Promise((resolve, reject) => {
@@ -2045,14 +2045,6 @@ <h2>The <dfn>record type</dfn> string</h2>
      </tr>
     </thead>
     <tbody data-link-for="NDEFReader">
-     <tr>
-      <tr>
-        <td><dfn>[[\ScanAbortSignal]]</dfn></td>
-        <td>`undefined`</td>
-        <td>
-          The {{NDEFScanOptions}}.signal to abort the operation.
-        </td>
-      </tr>
      <tr>
       <td><dfn>[[\WriteOptions]]</dfn></td>
       <td>`null`</td>
@@ -3443,30 +3435,33 @@ <h3><dfn>Writing content</dfn></h3>
             Let |options| be first argument.
           </li>
           <li>
-            [= list/For each =] |key| → |value| of |options|:
-            <ol>
-              <li>
-                If |key| equals "`signal`" and |value| is not `undefined`, set
-                |reader|.<a>[[\ScanAbortSignal]]</a> to |value|.
-              </li>
-            </ol>
+            Let |signal:AbortSignal| be the |options|’ dictionary member
+            of the same name if present, or `null` otherwise.
+          </li>
+          <li>
+            If |signal|’s [= AbortSignal/aborted flag =] is set, then reject |p|
+            with an {{"AbortError"}} {{DOMException}} and return |p|.
           </li>
           <li>
-            If |reader|.<a>[[\ScanAbortSignal]]</a>'s [= AbortSignal/aborted flag =] is
-            set, then reject |p| with a {{"AbortError"}} {{DOMException}}
-            and return |p|.
+            If |signal| is not `null`, then
+            <a data-cite="dom#abortsignal-abort-algorithms">
+            add the following abort steps</a> to |signal|:
+              <ol>
+                <li>
+                  Clear the <a>pending read tuple</a> .
+                </li>
+                <li>
+                  Make a request to stop listening to <a>NDEF message</a>s
+                  on all <a>NFC adapter</a>s.
+                </li>
+              </ol>
           </li>
           <li>
-            If |reader|.<a>[[\ScanAbortSignal]]</a> is not `null`, then
-            <a data-cite="dom#abortsignal-abort-algorithms">add the following
-            abort steps</a> to |reader|.<a>[[\ScanAbortSignal]]</a>:
+            [=promise/React=] to |p|:
             <ol>
               <li>
-                Clear the <a>pending read tuple</a>.
-              </li>
-              <li>
-                Make a request to stop listening to <a>NDEF message</a>s
-                on all <a>NFC adapter</a>s.
+                If |p| was settled (fulfilled or rejected), then clear the
+                <a>pending read tuple</a>.
               </li>
             </ol>
           </li>