Update onc_spec.html to match implementation.

components/onc/docs/onc_spec.html

Index: components/onc/docs/onc_spec.html
diff --git a/components/onc/docs/onc_spec.html b/components/onc/docs/onc_spec.html
index 8f0c03867c754f83984d59928e7e5b33480cf314..0db48abd5b34dd8858313ca74225d95aca170051 100644
--- a/components/onc/docs/onc_spec.html
+++ b/components/onc/docs/onc_spec.html
@@ -189,7 +189,8 @@
     <dt class="field">Type</dt>
     <dd>
       <span class="field_meta">
-        (required)
+        (optional, defaults to <span class="value">UnencryptedConfiguration
+         </span>)
         <span class="type">string</span>
       </span>
       Must be <span class="value">UnencryptedConfiguration</span>.
@@ -214,9 +215,10 @@
     </dd>
   </dl>
 
-  Besides the field <span class="field">Type</span>, at least one other field
+  At least one actual configuration field
   (<span class="field">NetworkConfigurations</span> or
-   <span class="field">Certificates</span>) should be present.
+   <span class="field">Certificates</span>) should be present. It should not be

[David Roche, 2014/07/07 17:22:43]

These 2 sentences seem a little at odds when separate, I wonder if we can soften
this by combining them with this edit?

s/. It/, however it/ ?

+  considered an error if no such field is present.
 
 <section>
   <h1>Network Configuration</h1>