Minor correction on example code for privavy extension documentation

chrome/common/extensions/docs/templates/intros/privacy.html

 <p class="note">
   The <a href="http://www.google.com/intl/en/landing/chrome/google-chrome-privacy-whitepaper.pdf">Chrome Privacy Whitepaper</a>
   gives background detail regarding the features which this API can control.
 </p>
 
 <h2 id="manifest">Manifest</h2>
 <p>
   You must declare the "privacy" permission in your extension's
   <a href="manifest.html">manifest</a> to use the API. For example:
 </p>
@@ skipping 54 matching lines @@
   reduce user confusion):
 </p>
 
 <pre>chrome.privacy.services.autofillEnabled.get({}, function(details) {
   if (details.levelOfControl === 'controllable_by_this_extension') {
     chrome.privacy.services.autofillEnabled.set({ value: true }, function() {
       if (chrome.runtime.lastError === undefined)
         console.log("Hooray, it worked!");
       else
         console.log("Sadness!", chrome.runtime.lastError);
-    }
+    });
   }
 });</pre>
 
 <p>
   If you're interested in changes to a setting's value, add a listener to its
   <code>onChange</code> event. Among other uses, this will allow you to warn the
   user if a more recently installed extension grabs control of a setting, or if
   enterprise policy overrides your control. To listen for changes to Autofill's
   status, for example, the following code would suffice:
 </p>
 
 <pre>chrome.privacy.services.autofillEnabled.onChange.addListener(
     function (details) {
       // The new value is stored in `details.value`, the new level of control
       // in `details.levelOfControl`, and `details.incognitoSpecific` will be
       // `true` if the value is specific to Incognito mode.
     });</pre>
 
 <h2 id="examples">Examples</h2>
 <p>
   For example code, see the
   <a href="samples.html#privacy">Privacy API samples</a>.
 </p>