Updating extension hosting docs

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>
 to allow extensions to manage important Chrome settings on Windows.
 Beginning with the July release of Chrome,

[not at google - send to devlin, 2015/05/13 18:23:27]

You may want to say "July 2014" here?

[mkearney1, 2015/05/13 18:36:36]

Done.

 the Settings Override API will be the only approved path
 for offering settings changes to Chrome users on Windows.
 In addition, starting with the May 20, 2014 release of Chrome,
 we <a href="http://blog.chromium.org/2014/02/make-sure-to-get-your-extension-in.html">have begun to require</a>
 that extensions in Chrome for Windows be hosted in the Chrome Web Store.
+Starting in Chrome M44 in July 2015,

[not at google - send to devlin, 2015/05/13 18:23:27]

I think publicly we don't put the "M" prefix, it's just "Chrome 44"?

[mkearney1, 2015/05/13 18:36:36]

Done.

+extensions in Mac are also required to be hosted in the Chrome Web Store.
 </p>
 
 <h2 id="two">2.) Why did Google launch a “single purpose” Chrome extensions policy?</h2>
 
 <p>For an overview of the policy announcement, please read this
 <a href="http://blog.chromium.org/2013/12/keeping-chrome-extensions-simple.html">Chromium blog post</a>.</p>
 
 <p>We launched this policy because
 multi-purpose extensions can crowd your browser UI
-and slow down your web browsing - sometimes significantly.
+and slow down your web browsing sometimes significantly.
 Speed and simplicity have always been part of Chrome's core principles,
 so this policy will help us get back to the design that was originally intended.
 Also, unexpected changes to browser functionality and
 settings have become the number one user complaint for Chrome users,
 and this policy helps minimize the problem by ensuring
 that users understand what extensions are doing.
 </p>
 
 <h2 id="three">3.) Where can I find the “single purpose” policy?</h2>
 
@@ skipping 30 matching lines @@
 If the extension is implemented in a single function,
 then it can offer content or features related to different areas or subjects.
 For example, an extension that replaces the new tab page could offer
 multiple unrelated features on the new tab page
 (for example, weather forecast, news headlines, search engine, and so on),
 but it can’t also provide a browser action button,
 change the browser’s homepage, or
 make any other changes to browser functionality.
 </p>
 
+<p>
+Be conscious of your extension’s permissions.
+We assume your extension utilizes each of the permissions it requests.
+Excessive permissions unrelated to your extension’s single purpose will be viewed
+as enabling unrelated functionalities, resulting in a policy violation.   
+</p>
+
 <h2 id="five">5.) Will this policy affect my extension?</h2>
 
 <p>
 It depends.
 Particularly if your extension offers multiple features,
 please make sure that it has a single purpose.
 Ask yourself these questions:
 </p>
 
 <ul>
   <li>Does my extension have a narrow focus area
   or a narrow function as described above?</li>
   <li>If my extension has a narrow focus area,
   are all of the features directly related to that single purpose?</li>
   <li>If my extension has multiple features,
   does it only affect a narrow function of the browser?</li>
   <li>Does my extension modify Chrome’s behavior in a predictable way,
   in line with the extension's narrow, stated purpose?</li>
+  <li>Does my extension request any unnecessary permissions?</li>
 </ul>
 
 <p>
 If you’re unsure, 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.
 If your extension does not have a single purpose,
 then you will need to remove functionality
 or split your extension into different extensions. 
@@ skipping 112 matching lines @@
 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>
+<h2 id="twelve">12.) Is this new policy only on some operating systems?</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
+initially applies only to Windows and Mac extensions.
+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="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.
@@ skipping 31 matching lines @@
 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="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.
+All extensions must 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.
 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="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,
+in the Chrome Web Store comes into effect for Windows in late May 2014,
 your extension must be hosted in the Chrome Web Store or
-it will be automatically disabled from the users’ browsers. 
+it will be automatically disabled from the users’ browsers.
+The same will occur for Mac extensions that are not hosted
+on the Chrome Web Store prior to the release of M44 in July 2015.
 </p>
 
 <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,
@@ skipping 52 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">