json: resync with internal guide

jsoncstyleguide.html

@@ -1,7 +1,7 @@
 <HTML xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcq="http://purl.org/dc/qualifiers/1.0/" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:fn="http://www.w3.org/2005/xpath-functions">
 <HEAD>
 <TITLE>Google JSON Style Guide</TITLE>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
 <LINK HREF="/styleguide/favicon.ico" type="image/x-icon" rel="shortcut icon">
 <LINK HREF="styleguide.css" type="text/css" rel="stylesheet">
 <SCRIPT language="javascript" type="text/javascript">
@@ -453,7 +453,7 @@ Avoid naming conflicts by choosing a new property name or versioning the API.
   "data": {
     "recipeName": "pizza",
     "ingredients": "Some new property",
-    "recipeIngredients": ["tomatos", "cheese", "sausage"]
+    "recipeIngredients": ["tomatoes", "cheese", "sausage"]
   }
 }
 </PRE></DIV>
@@ -1508,7 +1508,7 @@ This example demonstrates how the Google search items could be represented as a
 </DIV>
 <DIV class=""><DIV class="stylepoint_body" name="Paging_Example__body" id="Paging_Example__body" style="display: none">
 <p>This sample is for illustrative purposes only.  The API below does not actually exist.</p>
-<p>Here's a sample Google search results page:<br><img src="jsoncstyleguide_example_01.png"><br><img src="jsoncstyleguide_example_02.png"></p>
+<p>Here's a sample Google search results page:<br><img src="jsoncstyleguide_example_01.png" style="max-width:100%"><br><img src="jsoncstyleguide_example_02.png" style="max-width:100%"></p>
 <p>Here's a sample JSON representation of this page:</p>
 <DIV class=""><PRE>{
   "apiVersion": "2.1",