@@ -1451,13 +1451,15 @@ <h2>
14511451 messages=]. Many [=MIDI devices=] use [=System
14521452 Exclusive=] messages to perform firmware updates.
14531453 This is a common use of [=System Exclusive=]
1454- messages. A small number of devices use
1455- non-[=System Exclusive=] messages to perform
1456- firmware updates. Others may use out-of-band USB
1457- communication or require the user to connect a
1458- storage device directly to the [=MIDI device=] to
1459- perform firmware updates, which cannot be done using
1460- the Web MIDI API, and are not vulnerable.
1454+ messages. It is technically possible to make a
1455+ device that uses non-[=System Exclusive=] messages
1456+ to perform firmware updates, but this is not an
1457+ intended use of non-[=System Exclusive=] messages.
1458+ Other devices may use out-of-band USB communication
1459+ or require the user to connect a storage device
1460+ directly to the [=MIDI device=] to perform firmware
1461+ updates, which cannot be done using the Web MIDI
1462+ API, and are not vulnerable.
14611463 </ li >
14621464 < li >
14631465 Allow firmware updates without explicit user
@@ -1546,8 +1548,8 @@ <h2>
15461548 </ p >
15471549 < p >
15481550 Before discussing security concerns, it's useful to
1549- examine what scenarios are enabled by MIDI mapped against
1550- these features:
1551+ examine what scenarios are enabled by MIDI using these
1552+ features:
15511553 </ p >
15521554 < ul >
15531555 < li >
0 commit comments