Net triage docs: Fix links, mention crashes on other platforms.

net/docs/bug-triage.md

Index: net/docs/bug-triage.md
diff --git a/net/docs/bug-triage.md b/net/docs/bug-triage.md
index ac3240338f4498cdd58964ed08bca333d7a87f16..0eb41fea9f7eb3f673d0a619c3d92e1cc4f4f64e 100644
--- a/net/docs/bug-triage.md
+++ b/net/docs/bug-triage.md
@@ -61,8 +61,7 @@ uniform, predictable two day commitment for all triagers.
       fact an alert was responded to as an inidicator of which of them need
       to be followed up on.
 
-* Investigate [Uncomfirmed / Untriaged Internals>Network issues that don't
-  belong to a more specific network component](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DInternals%3ENetwork+status%3AUnconfirmed,Untriaged+-label:Needs-Feedback&sort=-modified),
+* Investigate [Uncomfirmed / Untriaged Internals>Network issues that don't belong to a more specific network component](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DInternals%3ENetwork+status%3AUnconfirmed,Untriaged+-label:Needs-Feedback&sort=-modified),
   prioritizing the most recent issues, ones with the most responsive reporters,
   and major crashers.  This will generally take up the majority of your time as
   triager. Continue digging until you can do one of the following:
@@ -90,8 +89,7 @@ uniform, predictable two day commitment for all triagers.
       its status should be set to Available.  Future triagers should ignore bugs
       with this status, unless investigating stale bugs.
 
-* Follow up on [Needs-Feedback issues for all components owned by the network
-  stack team](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AInternals%3ENetwork%2CUI>Browser>Downloads+-component%3AInternals%3ENetwork%3EDataProxy+-component%3AInternals%3ENetwork%3EDataUse+-component%3AInternals%3ENetwork%3EVPN+Needs%3DFeedback).

[mmenke, 2016/03/10 17:36:15]

Strangely, splitting the lines here didn't work on Googlesource's md enging, but
did work on Chrome...but the split on line 64 worked on both.

[Randy Smith (Not in Mondays), 2016/03/10 18:14:10]

Huh.  How did you check Googlesource's md engine before landing the CL?

[mmenke, 2016/03/10 19:18:35]

I didn't, I'm describing how it's behaving with the current code.

+* Follow up on [Needs-Feedback issues for all components owned by the network stack team](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AInternals%3ENetwork%2CUI>Browser>Downloads+-component%3AInternals%3ENetwork%3EDataProxy+-component%3AInternals%3ENetwork%3EDataUse+-component%3AInternals%3ENetwork%3EVPN+Needs%3DFeedback&sort=-modified).
 
     * Remove label once feedback is provided.  Continue to investigate, if
       the previous section applies.
@@ -116,6 +114,8 @@ uniform, predictable two day commitment for all triagers.
   crashes that are both in the top 100 for each release and occurred for more
   than two users.
 
+    * Make sure to check for new crashes on all platforms, not just Windows.
+
 ### Best Effort (As you have time):
 
 * Investigate old bugs, and bugs associated with Internals>Network