Editorial: Make auto-linking "read event" and "write event" specializ…

…ations

spec.html

@@ -49174,7 +49174,7 @@ <h1>Memory Model Fundamentals</h1>
     <emu-note>
       <p>No orderings weaker than sequentially consistent and stronger than unordered, such as release-acquire, are supported.</p>
     </emu-note>
-    <p>A <dfn variants="Shared Data Block events">Shared Data Block event</dfn> is either a <dfn>ReadSharedMemory</dfn>, <dfn>WriteSharedMemory</dfn>, or <dfn>ReadModifyWriteSharedMemory</dfn> Record.</p>
+    <p>A <dfn variants="Shared Data Block events">Shared Data Block event</dfn> is either a <dfn>ReadSharedMemory</dfn>, <dfn>WriteSharedMemory</dfn>, or <dfn>ReadModifyWriteSharedMemory</dfn> Record. A <dfn variants="read events">read event</dfn> is either a ReadSharedMemory or a ReadModifyWriteSharedMemory. A <dfn variants="write events">write event</dfn> is either a WriteSharedMemory or a ReadModifyWriteSharedMemory.</p>
 
     <emu-table id="table-readsharedmemory-fields" caption="ReadSharedMemory Event Fields">
       <table>
@@ -49683,7 +49683,7 @@ <h1>Sequentially Consistent Atomics</h1>
         <li>
           <p>For each WriteSharedMemory or ReadModifyWriteSharedMemory event _W_ in SharedDataBlockEventSet(_execution_), if _W_.[[Order]] is ~seq-cst~, then it is not the case that there is an infinite number of ReadSharedMemory or ReadModifyWriteSharedMemory events in SharedDataBlockEventSet(_execution_) with equal memory range that is memory-order before _W_.</p>
           <emu-note>
-            <p>This clause together with the forward progress guarantee on agents ensure the liveness condition that ~seq-cst~ writes become visible to ~seq-cst~ reads with equal memory range in finite time.</p>
+            <p>This clause together with the forward progress guarantee on agents ensure the liveness condition that ~seq-cst~ write events become visible to ~seq-cst~ read events with equal memory range in finite time.</p>
           </emu-note>
         </li>
       </ul>