In 4.8.11.2 "The 2D rendering context",
in the algorithm for "commit the scratch bitmap",
step 8 says:
    Queue a task from the canvas updating task source of the output bitmap's
    canvas element's event loop to perform the following substeps:

First, I think
    the <a ...>output bitmap</a>
should be
    <var>output bitmap</var>
i.e., a reference to the variable established in step 7.


Second, the 'access chain' in this step appears to be:
    the output bitmap
       v
    a canvas element
       v
    an event loop
       v
    canvas updating task source
and some of the links in this chain are questionable...

(a) "the output bitmap's canvas element"

    It isn't clear from the definition of 'output bitmap' that this is
    meaningful.  Section 4.8.11.2.1 does say:
        The output bitmap of a rendering context, when it has one,
        is always just an alias to a canvas element's bitmap.
    but that's non-normative, and appears later than the step in question.

    It would be helpful, where the spec says:
       A CanvasRenderingContext2D object ... can be bound to an output bitmap.
    to append something like:
       (the bitmap of a canvas element)


(b) "[a] canvas element's event loop"

    It's not clear what this means. It might mean:
        the event loop of the browsing context of the document
        that contains the canvas element
    but I couldn't find any prose to justify going directly from an element
    to an event loop.


(c) "the canvas updating task source of [an] event loop"

    It's not clear what this means either. I believe it's the only point
    in the spec that refers to a task source as being "of an event loop".
    (The only other place I could find of a task source being "of" anything
    is in 7.1.4.2's "spin the event loop", which refers to the task source
    of a task, which makes sense.)

    The step makes somewhat more sense if you replace the "of" with "to",
    leading to a slightly different parsing:
        Queue a task
            from 'the canvas updating task source'
            to the output bitmap's canvas element's event loop
            to perform the following substeps:
    i.e.:
        Queue a task to run the following substeps, where
        the task source of the task is the 'canvas updating task source',
        and the "relevant event loop" (referred to in the definition of
        "queue a task") is the output bitmap's canvas element's event loop.

    But that makes me wonder why this is (I think) the only "queue a task"
    that specifies the relevant event loop. Is there a general rule for
    determining the relevant event loop that works for all task-queuings
    other than this one? If so, it should probably be stated close to the
    definition for "queue a task".