Clarify the interpretation of string literal tokens

Fixes #141.

Author: Ms2ger

index.bs

@@ -2274,7 +2274,8 @@ it is interpreted in the same way as for a [=constant=].
 <div id="string-literal" algorithm="value of string literal tokens">
     Optional argument default values can also be specified using a
     <emu-t class="regex"><a href="#prod-string">string</a></emu-t>
-    token, whose value is a [=string type=] determined as follows:
+    token, whose <dfn lt="value of string literal tokens">value</dfn> is a
+    [=string type=] determined as follows:
 
     1.  Let |S| be the sequence of [=Unicode scalar values=] matched by
         the <emu-t class="regex"><a href="#prod-string">string</a></emu-t> token
@@ -5786,9 +5787,10 @@ of specifications using Web IDL might want to obtain a sequence of
 </div>
 
 There is no way to represent a constant {{DOMString}}
-value in IDL, although {{DOMString}} [=dictionary member=]
-and [=optional argument|operation optional argument=] default values
-can be specified using a <emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
+value in IDL, although {{DOMString}} [=dictionary member=] [=dictionary member/default values=]
+and [=optional argument|operation optional argument=] [=optional argument/default values=]
+can be set to [=value of string literal tokens|the value=] of a
+<emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
 
 The [=type name=] of the
 {{DOMString}} type is "<code>String</code>".
@@ -5802,9 +5804,10 @@ Such sequences might be interpreted as UTF-8 encoded strings [[!RFC3629]]
 or strings in some other 8-bit-per-code-unit encoding, although this is not required.
 
 There is no way to represent a constant {{ByteString}}
-value in IDL, although {{ByteString}} [=dictionary member=]
-and [=optional argument|operation optional argument=] default values
-can be specified using a <emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
+value in IDL, although {{ByteString}} [=dictionary member=] [=dictionary member/default values=]
+and [=optional argument|operation optional argument=] [=optional argument/default values=]
+can be set to [=value of string literal tokens|the value=] of a
+<emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
 
 The [=type name=] of the
 {{ByteString}} type is "<code>ByteString</code>".
@@ -5832,9 +5835,10 @@ which are all of the Unicode code points apart from the
 surrogate code points.
 
 There is no way to represent a constant {{USVString}}
-value in IDL, although {{USVString}} [=dictionary member=]
-and [=optional argument|operation optional argument=] default values
-can be specified using a <emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
+value in IDL, although {{USVString}} [=dictionary member=] [=dictionary member/default values=]
+and [=optional argument|operation optional argument=] [=optional argument/default values=]
+can be set to [=value of string literal tokens|the value=] of a
+<emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
 
 The [=type name=] of the
 {{USVString}} type is "<code>USVString</code>".
@@ -5929,8 +5933,9 @@ refer to a type whose values are the set of strings (sequences of
 [=enumeration values|enumeration’s values=].
 
 Like {{DOMString}}, there is no way to represent a constant [=enumeration=]
-value in IDL, although enumeration-typed [=dictionary member=]
-[=dictionary member/default values=] can be specified using a
+value in IDL, although enumeration-typed [=dictionary member=] [=dictionary member/default values=]
+and [=optional argument|operation optional argument=] [=optional argument/default values=]
+can be set to [=value of string literal tokens|the value=] of a
 <emu-t class="regex"><a href="#prod-string">string</a></emu-t> literal.
 
 The [=type name=] of an enumeration type