Tweak network doc wording, fix link, and make order in workflow match

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

 # Chrome Network Bug Triage : Suggested Workflow
 
 [TOC]
 
 ## Identifying unlabeled network bugs on the tracker
 
 * Look at new uncomfirmed 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).
 
@@ skipping 11 matching lines @@
     * 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
   browser crash) and attach the most specific internals-network label that's
   applicable.  If there isn't an applicable narrower component, a clear owner
   for the issue, or there are multiple possibilities, attach the
   Internals>Network component and proceed with further investigation.
 
 * If non-network causes also seem possible, attach those components as well.
 
+## Investigate UMA notifications
+
+For each alert that fires, determine if it's a real alert and file a bug if so.
+
+* Don't file if the alert is coincident with a major volume change.  The volume
+  at a particular date can be determined by hovering the mouse over the
+  appropriate location on the alert line.
+
+* Don't file if the alert is on a graph with very low volume (< ~200 data
+  points); it's probably noise, and we probably don't care even if it isn't.
+
+* Don't file if the graph is really noisy (but eyeball it to decide if there is
+  an underlying important shift under the noise).
+
+* Don't file if the alert is in the "Known Ignorable" list:
+    * SimpleCache on Windows
+    * DiskCache on Android.
+
 ## Investigating component=Internals>Network bugs
 
 * It's recommended that while on triage duty, you subscribe to the
   Internals>Network component (but not its subcomponents). To do this, go
   to the issue tracker and then click "Saved Queries".
   Add a query with these settings:
     * Saved query name: Network Bug Triage
     * Project: chromium
     * Query: component=Internals>Network
     * Subscription options: Notify Immediately
@@ skipping 58 matching lines @@
 * If you are having trouble with an issue, particularly for help understanding
   net-internals logs, email the public net-dev@chromium.org list for help
   debugging.  If it's a crasher, or for some other reason discussion needs to
   be done in private, use chrome-network-debugging@google.com.  TODO(mmenke):
   Write up a net-internals tips and tricks docs.
 
 * If it appears to be a bug in the unowned core of the network stack (i.e. no
   subcomponent applies, or only the Internals>Network>HTTP subcomponent
   applies, and there's no clear owner), try to figure out the exact cause.
 
-## Investigate UMA notifications
-
-For each alert that fires, determine if it's a real alert and file a bug if so.
-
-* Don't file if the alert is coincident with a major volume change.  The volume
-  at a particular date can be determined by hovering the mouse over the
-  appropriate location on the alert line.
-
-* Don't file if the alert is on a graph with very low volume (< ~200 data
-  points); it's probably noise, and we probably don't care even if it isn't.
-
-* Don't file if the graph is really noisy (but eyeball it to decide if there is
-  an underlying important shift under the noise).
-
-* Don't file if the alert is in the "Known Ignorable" list:
-    * SimpleCache on Windows
-    * DiskCache on Android.
-
 ## Looking for new crashers
 
 1. Go to [go/chromecrash](https://goto.google.com/chromecrash).
 
 2. For each platform, look through the releases for which releases to
    investigate.  As per bug-triage.txt, this should be the most recent canary,
    the previous canary (if the most recent is less than a day old), and any of
    dev/beta/stable that were released in the last couple of days.
 
 3. For each release, in the "Process Type" frame, click on "browser".
@@ skipping 63 matching lines @@
   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