guidelines/review-instructions: Add info about t: labels

guidelines/review-instructions.html

@@ -93,6 +93,7 @@ <h2>Summary</h2>
 
 <section id="creating-product">
 <h2>Create a label</h2>
+<p>If this is the first time a spec with this short-name has been reviewed, you'll need to create a label to identify the spec. You may need a W3C staff person to help do this.</p>
 <ol>
 <li>
 <p>Labels should start with &quot;<span style="font-weight: bold">s:</span>&quot;, followed by the exact short-name for the document, with the color <code>#6bc5c6</code>.</p>
@@ -160,8 +161,9 @@ <h2>Notify the relevant WG</h2>
 </ol>
 </li>
 <li>
-<p> <span class="highlight1">Add the equivalent labels to the tracker issue</span>, ie. a<span class="highlight1"></span> <span class="highlight1"><span style="background-color: #f9c9ff; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: bold; white-space: nowrap;">needs-resolution</span></span> label, and any appropriate <span class="highlight1"><span style="background-color: #d4c5f9; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: bold;">*lreq</span></span> label(s). (These are the same labels as used for the WG issue, just without the i18n- prefix.)</p>
-<p>If you added an *lreq label, add the label <span style="background-color: #006b75; padding:2px 4px; border-radius:5px; color:white;font-style:normal;font-weight: normal; white-space: nowrap;">spec-type-issue</span> and a label to indicate the relevant typographic feature(s), eg. <span style="background-color: #fef2c0; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: normal; white-space: nowrap;">i:line_breaking</span>. The latter represent categories related to the Language Enablement Index, and all start with i:.</p>
+<p> <span class="highlight1">Add  labels to the tracker issue</span>, ie. a<span class="highlight1"></span> <span class="highlight1"><span style="background-color: #f9c9ff; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: bold; white-space: nowrap;">needs-resolution</span></span> label, and any appropriate <span class="highlight1"><span style="background-color: #d4c5f9; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: bold;">*lreq</span></span> label(s). (These are the same labels as used for the WG issue, just without the i18n- prefix.)</p>
+<p>If you added an *lreq label, add the label <span style="background-color: #006b75; padding:2px 4px; border-radius:5px; color:white;font-style:normal;font-weight: normal; white-space: nowrap;">spec-type-issue</span> and a label to indicate the relevant typographic feature(s), eg. <span style="background-color: #fef2c0; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: normal; white-space: nowrap;">i:line_breaking</span>. The latter represent categories related to the <a href="https://www.w3.org/TR/typography/">Language Enablement Index</a>, and all start with i:.</p>
+<p>Always add a label starting with t: to indicate the topic, eg. <span style="background-color: #FBCA04; padding:2px 4px; border-radius:5px; color:black;font-style:normal;font-weight: normal; white-space: nowrap;">t:text_case</span>. After the t: the label contains an id for a relevant section in the document <a href="https://w3c.github.io/bp-i18n-specdev/">Internationalization Best Practices for Spec Developers</a> (called 'specdev'). You can attach multiple labels if multiple sections are relevant. These labels automatically establish links between the specdev document and related issues.</p>
 </li>
   <li>
     <p><span class="highlight1">Copy over</span> the information in the tracker issue description to the WG issue description, incorporating any changes that arise out of discussions with the i18n WG.</p>