Plugin Power Saver: Replace all "plug-in" with "plugin" for consistency.

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

 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "contentSettings" permission
 in your extension's manifest to use the API.
 For example:</p>
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
   <b>"permissions": [
     "contentSettings"
@@ skipping 97 matching lines @@
   <td><code>&lt;all_urls&gt;</code>, </td>
   <td><code>&lt;all_urls&gt;</code></td>
 </tr>
 </table>
 
 <h2 id="resource-identifiers">Resource identifiers</h2>
 <p>
 Resource identifiers allow you to specify content settings for specific
 subtypes of a content type. Currently, the only content type that supports
 resource identifiers is $(ref:contentSettings.plugins),
-where a resource identifier identifies a specific plug-in. When applying content
-settings, first the settings for the specific plug-in are checked. If there are
-no settings found for the specific plug-in, the general content settings for
-plug-ins are checked.
+where a resource identifier identifies a specific plugin. When applying content
+settings, first the settings for the specific plugin are checked. If there are
+no settings found for the specific plugin, the general content settings for
+plugins are checked.
 </p>
 <p>
 For example, if a content setting rule has the resource identifier
 <code>adobe-flash-player</code> and the pattern <code>&lt;all_urls&gt;</code>,
 it takes precedence over a rule without a resource identifier and the pattern
 <code>http://www.example.com/*</code>, even if that pattern is more specific.
 </p>
 <p>
 You can get a list of resource identifiers for a content type by calling the
 $(ref:contentSettings.ContentSetting.getResourceIdentifiers) method. The returned list
-can change with the set of installed plug-ins on the user's machine, but Chrome
-tries to keep the identifiers stable across plug-in updates.
+can change with the set of installed plugins on the user's machine, but Chrome
+tries to keep the identifiers stable across plugin updates.
 </p>
 
 <h2 id="examples">Examples</h2>
 
 <p>
 You can find samples of this API on the
 <a href="samples#contentSettings">sample page</a>.
 </p>