[NaCl SDK]: Docs -- fix typo in nacl manifest specification (missing "portable")

native_client_sdk/doc_generated/reference/nacl-manifest-format.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="native-client-manifest-nmf-format">
 <h1 id="native-client-manifest-nmf-format">Native Client Manifest (nmf) Format</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id1">Overview</a></li>
 <li><a class="reference internal" href="#field-summary" id="id2">Field summary</a></li>
 <li><p class="first"><a class="reference internal" href="#field-details" id="id3">Field details</a></p>
 <ul class="small-gap">
@@ skipping 43 matching lines @@
 of URLs, one URL for each supported architecture (currently the choices
 are &#8220;arm&#8221;, &#8220;x86-32&#8221;, and &#8220;x86-64&#8221;). For a dynamically linked executable,
 <code>program</code> is the dynamic loader used to load the dynamic executable
 and its dynamic libraries.  See the <a class="reference internal" href="#nmf-url-resolution"><em>semantics</em></a>
 section for the rules on URL resolution.</p>
 <section id="example-of-a-program-for-portable-native-client">
 <h4 id="example-of-a-program-for-portable-native-client">Example of a <code>program</code> for Portable Native Client:</h4>
 <pre class="prettyprint">
 {
   &quot;program&quot;: {
-    &quot;pnacl-translate&quot;: {
-      // url is required
-      &quot;url&quot;: &quot;url_to_my_pexe&quot;,
+    &quot;portable&quot;: {
+      // Required
+      &quot;pnacl-translate&quot;: {
+        // url is required
+        &quot;url&quot;: &quot;url_to_my_pexe&quot;,
 
-      // optlevel is optional
-      &quot;optlevel&quot;: 2
-    },
-    // pnacl-debug is optional
-    &quot;pnacl-debug&quot;: {
-      // url is required
-      &quot;url&quot;: &quot;url_to_my_bitcode_bc&quot;,
+        // optlevel is optional
+        &quot;optlevel&quot;: 2
+      },
+      // pnacl-debug is optional
+      &quot;pnacl-debug&quot;: {
+        // url is required
+        &quot;url&quot;: &quot;url_to_my_bitcode_bc&quot;,
 
-      // optlevel is optional
-      &quot;optlevel&quot;: 0
+        // optlevel is optional
+        &quot;optlevel&quot;: 0
+      }
     }
   }
 }
 </pre>
 <p>Portable Native Client applications can also specify an <code>optlevel</code> field.
 The <code>optlevel</code> field is an optimization level <em>hint</em>, which is a number
 (zero and higher). Higher numbers indicate more optimization effort.
 Setting a higher optimization level will improve the application&#8217;s
 performance, but it will also slow down the first load experience.
 The default is <code>optlevel</code> is currently <code>2</code>, and values higher
@@ skipping 150 matching lines @@
 inline with a data URI can help reduce the amount of network traffic
 required to load the Native Client application.</p>
 </section><section id="url-resolution">
 <span id="nmf-url-resolution"></span><h3 id="url-resolution"><span id="nmf-url-resolution"></span>URL resolution</h3>
 <p>All URLs contained in a manifest are resolved relative to the URL of
 the manifest. If the manifest was specified as a data URI, the URLs must
 all be absolute.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}