Spell-check net bug triage docs.

net/docs/bug-triage.md

 # Chrome Network Bug Triage
 
 The Chrome network team uses a two day bug triage rotation.  The main goals are
 to identify and label new network bugs, and investigate network bugs when no
 label seems suitable.
 
 ## Responsibilities
 
 ### Required, in rough order of priority:
 * Identify new network bugs on the tracker.
@@ skipping 41 matching lines @@
       to this list.  When an alert fires, the triager should determine if the
       alert looks to be real and file a bug with the appropriate label if so.
       Note that if no label more specific than Internals>Network is appropriate,
       the responsibility remains with the triager to continue investigating the
       bug, as above.
       
     * The triager is responsible for looking at any notification previous
       triagers did not, so when an issue is investigated, the person who did
       so should respond to chrome-network-debugging@google.com with a short
       email, describing their conclusions.  Future triagers can then use the
-      fact an alert was responded to as an inidicator of which of them need
+      fact an alert was responded to as an indicator of which of them need
       to be followed up on.  Alerts fired before the beginning of the
       previous triager's rotation may be ignored. 
 
-* 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 [Unconfirmed / 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:
 
     * Mark it as *WontFix* (working as intended, obsolete issue) or a
       duplicate.
 
     * Mark it as a feature request.
 
     * Mark it as Needs-Feedback.
@@ skipping 54 matching lines @@
 * Close obsolete bugs.
 
 See [bug-triage-suggested-workflow.md](bug-triage-suggested-workflow.md) for
 suggested workflows.
 
 See [bug-triage-labels.md](bug-triage-labels.md) for labeling tips for network
 and non-network bugs.
 
 See [crash-course-in-net-internals.md](crash-course-in-net-internals.md) for
 some help on getting started with about:net-internals debugging.