Tiny spelling fix to the extension optionsV2 docs.

chrome/common/extensions/docs/templates/articles/optionsV2.html

 <h1>Options</h1>
 
 <p class="warning">
 This new way of writing options is only supported from Chrome 40 onwards.
 <a href="options">See the old documentation</a>.
 </p>
 
 <p>
 To allow users to customize the behavior of your extension, you may wish to
 provide an options page.
@@ skipping 167 matching lines @@
 ensure that the dialogue will find an appropriate size.
 </p>
 
 <h2 id="migration">Migrating from old options pages</h2>
 <p class="warning">
 At least until Chrome 40 is stable, you should specify <strong>both</strong>
 the <code>options_ui</code> <strong>and</strong> the <code>options_page</code>
 fields.
 <br><br>
 Older versions of Chrome will only recognize <code>options_page</code>, and
-only open in tabs. Chrome 40 and onwards prefers to use the
+only open in tabs. Chrome 40 and onwards prefer to use the
 <code>options_ui</code> field if it's specified.
 </p>
 
 The <code>options_ui</code> manifest field and embedded extension options
 were introduced in Chrome 40. Prior to these changes, options pages were always
 displayed in new tabs and were declared using the <code>options_page</code>
 field:
 </p>
 
 <pre data-filename="manifest.json">
@@ skipping 17 matching lines @@
 <p>
 If you specify both, Chrome 40 and onwards will ignore the value of
 <code>options_page</code>.
 </p>
 <p>
 In a future version of Chrome, any extension which specifies
 <code>options_page</code> will change to match the <code>options_ui</code>
 behavior - most importantly, they will always be embedded in
 <em>chrome://extensions</em> - so migrate as soon as possible.
 </p>