Updated Triage Instructions (markdown)

Triage-Instructions.md

@@ -6,6 +6,14 @@ The highest priority is getting unlabeled bugs to zero.
 
 # How to Label a Bug
 
+### Change the Title
+
+Most issues have pretty bad titles, hindering future searches. If needed, edit the issue title to align better with the [[Preferred Issue Titles]] format.
+
+If you can't figure out from the issue report what the title *should* be, then you'll definitely need clarification from the user (see "Needs More Info" below).
+
+### Add a Label
+
 Classify the bug accordingly:
  * Duplicate: Many issues are duplicates, so try to find an original
    * If you do, add the `Duplicate` label and add a comment e.g. "See #1234567"
@@ -26,9 +34,14 @@ Classify the bug accordingly:
  * Not a bug
    * Add `Working as Intended` if the behavior is truly done on purpose, or `Design Limitation` if it's something we *would* fix in a perfect world but are unable to do so
    * Post a comment explaining why. Try to reference things from [the FAQ](https://github.com/Microsoft/TypeScript/wiki/FAQ) if applicable; consider updating the FAQ if you think it's a common question
+ * It's not clear what the issue is describing
+   * Add the `Needs More Info` label
+   * Add a comment explaining why the issue isn't actionable yet
  * Issue is in external component (e.g. tslint, awesome-typescript-loader, etc)
    * Add the `External` label
    * Explain why
+ * Completely useless
+   * If the issue is completely unsalvageable (e.g. it's just "Why can TypeScript not for C# now?" with no other info), add the `Unactionable` label and Close.
  * Fallback: Not sure
    * Add "Needs Investigation" label
    * Optional: Post comment with your thoughts (e.g. "Might be a type inference bug, need to investigate")