[net] Remove downloads bug triage from //net triage responsibilities.

net/docs/bug-triage-suggested-workflow.md

 # Chrome Network Bug Triage : Suggested Workflow
 
 [TOC]
 
 ## Identifying unlabeled network bugs on the tracker
 
 * Look at new unconfirmed bugs since noon PST on the last triager's rotation.
   [Use this issue tracker
-  query](https://code.google.com/p/chromium/issues/list?can=2&q=status%3Aunconfirmed&sort=-id&num=1000).
+  query](https://bugs.chromium.org/p/chromium/issues/list?q=status%3Aunconfirmed&sort=-id&num=1000).
 
 * Read the title of the bug.
 
-* If a bug looks like it might be network/download/safe-browsing related,
-  middle click (or command-click on OSX) to open it in a new tab.
+* If a bug looks like it might be network related, middle click (or
+  command-click on OSX) to open it in a new tab.
 
 * If a user provides a crash ID for a crasher for a bug that could be
   net-related, look at the crash stack at
   [go/crash](https://goto.google.com/crash), and see if it looks to be network
   related.  Be sure to check if other bug reports have that stack trace, and
   mark as a dupe if so.  Even if the bug isn't network related, paste the stack
   trace in the bug, so no one else has to look up the crash stack from the ID.
     * If there's just a blank form and a crash ID, just ignore the bug.
 
 * If network causes are possible, ask for a net-internals log (If it's not a
@@ skipping 152 matching lines @@
                bug.  Make sure to indicate if there is a defined point in the
                past before which the signature is not present.
 
 ## Investigating crashers
 
 * Only investigate crashers that are still occurring, as identified by above
   section.  If a search on go/crash indicates a crasher is no longer occurring,
   mark it as WontFix.
 
 * On Windows, you may want to look for weird dlls associated with the crashes.
-    This generally needs crashes from a fair number of different users to reach
-    any conclusions.
+  This generally needs crashes from a fair number of different users to reach
+  any conclusions.
     * To get a list of loaded modules in related crash dumps, select
       modules->3rd party in the left pane.  It can be difficult to distinguish
       between safe dlls and those likely to cause problems, but even if you're
       not that familiar with windows, some may stick out.  Anti-virus programs,
       download managers, and more gray hat badware often have meaningful dll
       names or dll paths (Generally product names or company names).  If you
       see one of these in a significant number of the crash dumps, it may well
       be the cause.
     * You can also try selecting the "has malware" option, though that's much
       less reliable than looking manually.
 
 * See if the same users are repeatedly running into the same issue.  This can
   be accomplished by search for (Or clicking on) the client ID associated with
   a crash report, and seeing if there are multiple reports for the same crash.
   If this is the case, it may be also be malware, or an issue with an unusual
   system/chrome/network config.
 
 * Dig through crash reports to figure out when the crash first appeared, and
   dig through revision history in related files to try and locate a suspect CL.
   TODO(mmenke):  Add more detail here.
 
 * Load crash dumps, try to figure out a cause.  See
   http://www.chromium.org/developers/crash-reports for more information