Another round of updates to single-purpose doc.

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

 <h1>Extensions Quality Guidelines FAQ</h1>
 
 <h2 id="one">1.) What is the new policy?</h2>
 
 <p>
 To maintain the quality of the Chrome user experience,
 we recently launched a new policy requiring Chrome extensions
 to have a single purpose.
 We are also introducing the new
 <a href="http://blog.chromium.org/2014/03/protecting-user-settings-on-windows.html">Settings Override API</a>
@@ skipping 185 matching lines @@
 From these notifications,
 users will have the option to reverse the settings changes
 by disabling the extension.
 </p>
 
 <h2 id="10">10.) What happens to settings when an extension is disabled?</h2>
 
 <p>
 All Chrome settings changed by an extension will be reverted
 when that extension is disabled.
-All other settings will remain unchanged.
+All other settings
+(for example, those changed directly by a Windows binary)
+will remain unchanged.
 </p>
 
-<h2 id="eleven">11.) Is this new policy Windows-only?</h2>
+<h2 id="eleven">11.) Will users’ existing homepage, search provider or
+startup pages be affected by the introduction of the Settings Override API?</h2>
+
+<p>
+No.
+A user’s existing homepage, search provider or startup settings will
+remain unchanged by the introduction of Settings Override API.
+Following the launch of the Settings Override API,
+only extensions can programmatically change these settings and
+only through the Settings Override API.
+But all changes to a user’s homepage, search provider or
+startup pages made prior to the launch of the Settings Override API,
+including any that may have been made by Windows binaries,
+will remain unchanged until the user manually updates those settings or
+installs an extension that uses the Settings Override API to change them. 
+</p>
+
+<h2 id="twelve">12.) Is this new policy Windows-only?</h2>
 
 <p>
 The <a href="https://developer.chrome.com/extensions/hosting_changes">requirement</a>
 that Chrome extensions be hosted in the Chrome Web Store
 initially applies only to Windows extensions.
 Likewise, the new Settings Override API will initially be made available
 only on Chrome for Windows.
 However, the single-purpose policy will apply to all Chrome extensions.
 </p>
 
-<h2 id="twelve">12.) Does this policy apply to Chrome apps too?</h2>
+<h2 id="thirteen">13.) Does this policy apply to Chrome apps too?</h2>
 
 <p>
 At this time, Chrome apps (as distinguished from extensions)
 are not required to be distributed through the Chrome Web Store,
 or to have a single purpose.
 Chrome apps are currently not capable of changing Chrome settings.
 </p>
 
-<h2 id="thirteen">13.) Can I bundle ad injection with some other type of functionality?</h2>
+<h2 id="fourteen">14.) Can I bundle ad injection with some other type of functionality?</h2>
 
 <p>
 No.
 This violates the single purpose policy.
 However, if injecting ads is the single purpose of the extension and
 the extension is otherwise compliant with Chrome policies,
 then it would be acceptable.
 For example, a “related articles” extension that adds sponsored links
 to articles related to a page the user is visiting would be compliant
 with the single purpose policy because it has a single purpose limited
 to a narrow function of the browser.
 You also might want to explore the other monetization options described
 <a href="https://developer.chrome.com/webstore/money">here</a>.
 </p>
 
-<h2 id="fourteen">14.) Are toolbars permitted under this policy?</h2>
+<h2 id="fifteen">15.) Are toolbars permitted under this policy?</h2>
 
 <p>
 It depends on what the toolbar does.
 As described in
 <a href="#four">answer #4</a>,
 it must adhere to the narrow single purpose of the extension.
 Broad, multi-purpose toolbars are not allowed and
 toolbars that are implemented using content scripts
 to inject UI into every page are not recommended because
 they slow down every page load, clutter the UI,
 and can lead to security problems for users.
 Instead, consider using a
 <a href="https://developer.chrome.com/extensions/browserAction">browser action popup</a>,
 which was designed to solve this very problem.
 It's a better user experience, with no performance or security downsides.
 </p>
 
-<h2 id="fifteen">15.) What will happen to non-compliant extensions
+<h2 id="sixteen">16.) What will happen to non-compliant extensions
 that were already installed by users?</h2>
 
 <p>
 All extensions will need to comply with the Extension Quality Guidelines.
 If a user installed a non-compliant extension,
 then you will need to update them to a compliant extension
 that is hosted in the Chrome Web Store.
 If the user is not updated to a compliant extension
 that is hosted in the Chrome Web Store,
 then the extension will be automatically disabled.
-When Chrome disables a non-compliant extension,
-it will not revert browser settings made at the same time as installing
-that extension prior to the launch of the Settings Override API.
-Only settings changed by an extension using the Settings Override API
+As noted above,
+any settings or behaviours controlled by the extension,
+including any settings controlled by the Settings Override API,
 will be reverted when the extension is disabled. 
 You can find more information
 <a href="http://blog.chromium.org/2014/02/make-sure-to-get-your-extension-in.html">here</a>.
 </p>
 
-<h2 id="sixteen">16.) If my extension is rejected from the Chrome Web Store
+<h2 id="seventeen">17.) If my extension is rejected from the Chrome Web Store
 because it doesn’t comply with the single purpose policy,
 what will happen after the requirement to host extensions
 in the Chrome Web Store comes into effect?</h2>
 
 <p>
 If your extension is rejected from the Chrome Web Store,
 you will need to make changes or appeal the decision.
 After the requirement to host extensions
 in the Chrome Web Store comes into effect in late May 2014,
 your extension must be hosted in the Chrome Web Store or
 it will be automatically disabled from the users’ browsers. 
 </p>
 
-<h2 id="seventeen">17.) If my extension gets flagged for review under the single purpose policy,
+<h2 id="eighteen">18.) If my extension gets flagged for review under the single purpose policy,
 what will happen?</h2>
 
 <p>
 Our team will review it,
 and it may be removed from the Chrome Web Store.
 You’ll have a chance to make changes and appeal the decision.
 As noted above,
 if you created your extension before we announced the policy on December 19, 2013,
 you have until July 22, 2014 to make changes.
 If your extension was created after the policy was announced,
 it needs to be compliant now.
 You can temporarily unpublish it and contact us at
 <a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@google.com</a>
 with your extension ID if you’d like feedback.
 We’ll try to respond within a week.
 </p>
 
-<h2 id="eighteen">18.) I need help. Who should I contact?</h2>
+<h2 id="nineteen">19.) I need help. Who should I contact?</h2>
 
 <p>
 You can email
 <a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@google.com</a>
 with your extension ID,
 and we’ll take a look and try to provide feedback within a week.
 This is a lightweight review intended to give you an indication
 of whether your extension will comply with the new policy.
 </p>
 
@@ skipping 31 matching lines @@
 A search extension.
 It has multiple features, including this dropdown,
 but all of them are related to the narrow subject matter of search.
 </p>
 
 <img src="{{static}}/images/extension2.png"
      width="680"
      height="425"
      alt="Image of search extension">