Spell-check net bug triage docs.

net/docs/bug-triage-labels.md

 # Chrome Network Bug Triage : Components and labels
 
 ## Some network component caveats
 
 * **UI>Browser>Downloads**
 
     Despite the name, this covers all issues related to downloading a file
     except saving entire pages (which is **Blink>SavePage**), not just UI
     issues.  Most downloads bugs will have the word "download" or "save as" in
     the description.  Issues with the HTTP server for the Chrome binaries are
@@ skipping 10 matching lines @@
 
     This includes issues that should be also tagged as **Security>UX**
     (certificate error pages or other security interstitials, omnibox indicators
     that a page is secure), and more general SSL issues.  If you see requests
     that die in the SSL negotiation phase, in particular, this is often the
     correct component.
 
 * **Internals>Network>DataProxy**
 
     Flywheel / the Data Reduction Proxy.  Issues require "Reduce Data Usage" be
-    turned on.  Proxy url is [https://proxy.googlezip.net:443](#), with
+    turned on.  Proxy URL is [https://proxy.googlezip.net:443](#), with
     [http://compress.googlezip.net:80](#) as a fallback.  Currently Android and
     iOS only.
 
 * **Internals>Network>Cache**
 
     The cache is the layer that handles most range request logic (Though range
     requests may also be issued by the PDF plugin, XHRs, or other components).
 
 * **Internals>Network>SPDY**
 
@@ skipping 76 matching lines @@
 
     Issues with network related extension APIs should have this component.
     chrome.webRequest is the big one, I believe, but there are others.
 
 * **Internals>Plugins>Pepper[>SDK]**
 
 * **UI>Browser>Omnibox**
 
     Basically any issue with the omnibox.  URLs being treated as search queries
     rather than navigations, dropdown results being weird, not handling certain
-    unicode characters, etc.  If the issue is new TLDs not being recognized by
+    Unicode characters, etc.  If the issue is new TLDs not being recognized by
     the omnibox, that's due to Chrome's TLD list being out of date, and not an
     omnibox issue.  Such TLD issues should be duped against
     http://crbug.com/37436.
 
 * **Internals>Media>Network**
 
     Issues related to media.  These often run into the 6 requests per hostname
     issue, and also have fun interactions with the cache, particularly in the
     range request case.
 
 * **Internals>Plugins>PDF**
 
-    Issues loading pdf files.  These are often related to range requests, which
+    Issues loading PDF files.  These are often related to range requests, which
     also have some logic at the Internals>Network>Cache layer.
 
 * **UI>Browser>Navigation**
 
 * **UI>Browser>History**
 
     Issues which only appear with forward/back navigation.
 
 * **OS>Systems>Network** / **OS>Systems>Mobile** / **OS>Systems>Bluetooth**
 
@@ skipping 12 matching lines @@
     beyond the lifetime of incognito tabs, etc).  Generally used in conjunction
     with other components.
 
 ## Common labels
 
 * **Type-Bug-Security**
 
     Security related bug (Allows for code execution from remote site, allows
     crossing security boundaries, unchecked array bounds, etc) should be tagged
     with this label.