Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(4954)

Unified Diff: chrome/common/extensions/docs/server2/templates/intros/permissions.html

Issue 10832042: Extensions Docs Server: Doc conversion script (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: script/build.py fixes Created 8 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/common/extensions/docs/server2/templates/intros/permissions.html
diff --git a/chrome/common/extensions/docs/server2/templates/intros/permissions.html b/chrome/common/extensions/docs/server2/templates/intros/permissions.html
index 37ba76efc97d6ac62cc5dda454377c1243721bc0..84a7e727012c4018d6a84ce78a5e51aace0191aa 100644
--- a/chrome/common/extensions/docs/server2/templates/intros/permissions.html
+++ b/chrome/common/extensions/docs/server2/templates/intros/permissions.html
@@ -1,4 +1,3 @@
-<!-- BEGIN AUTHORED CONTENT -->
<p id="classSummary">
Use the <code>chrome.permissions</code> module to implement
optional permissions. You can request optional permissions during your
@@ -12,8 +11,9 @@
manifest documentation.
</p>
<h2 id="howto"> Implementing optional permissions </h2>
-
-<h3 id="types"> Step 1: Decide which permissions are optional and required </h3>
+<h3 id="types">
+ Step 1: Decide which permissions are optional and required
+</h3>
<p>
Extensions should generally require permissions when they are needed for the
extension's basic functionality and employ optional permissions for optional
@@ -158,5 +158,4 @@ chrome.permissions.remove({
// required permissions).
}
});
-</pre>
-<!-- END AUTHORED CONTENT -->
+</pre>

Powered by Google App Engine
This is Rietveld 408576698