fix s/CH-Accept/Accept-CH/ in client hints article

google · Sep 2, 2015 · b3c800b · b3c800b
1 parent 7a696e3
commit b3c800b
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/.../en/updates/2015-09-01-automating-resource-selection-with-client-hints.markdown b/.../en/updates/2015-09-01-automating-resource-selection-with-client-hints.markdown
@@ -180,7 +180,7 @@ Take a deep breath, suspend your disbelief, and now consider the following
 example:
 
 {% highlight html %}
-<meta http-equiv="CH-Accept" value="DPR, Viewport-Width, Width">
+<meta http-equiv="Accept-CH" value="DPR, Viewport-Width, Width">
 ...
 <picture>
   <source media="(min-width: 50em)" sizes="50vw" srcset="/image/thing">
@@ -208,7 +208,7 @@ expand the above markup because the actual resource selection is negotiated by
 the client and server.
 
 **Chrome 46 provides native support for the `DPR`, `Width`, and `Viewport-Width` 
-hints.** The hints are disabled by default and the `<meta http-equiv="CH-Accept" ...>` 
+hints.** The hints are disabled by default and the `<meta http-equiv="Accept-CH" ...>` 
 above serves as an opt-in signal that tells Chrome to append the specified headers to
 outgoing requests. With that in place, let's examine the request and response headers 
 for a sample image request: