Merge 32931 - Update pages that reference the gallery to link to the gallery.

Also a few wording changes.

TEST=none
BUG=none
TBR=aa
Review URL: http://codereview.chromium.org/437027

TBR=kathyw@google.com
Review URL: http://codereview.chromium.org/500052

git-svn-id: svn://svn.chromium.org/chrome/branches/249/src@34674 0039d316-1c4b-4281-b951-d872f2087c98

10 files changed, 38 insertions, 14 deletions

diff --git a/chrome/common/extensions/docs/autoupdate.html b/chrome/common/extensions/docs/autoupdate.html
index 7fa3c60..f01ad18 100644
--- a/chrome/common/extensions/docs/autoupdate.html
+++ b/chrome/common/extensions/docs/autoupdate.html
@@ -285,7 +285,7 @@
 
 <p>We want extensions to be autoupdated for some of the same reasons as Google Chrome itself: to incorporate bug and security fixes, add new features or performance enhancements, and improve user interfaces.</p>
 
-<p>For extensions packaged and distributed via the gallery, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themselves with the rest of this document.</p>
+<p>For extensions packaged and distributed via the <a href="https://chrome.google.com/extensions">gallery</a>, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themselves with the rest of this document.</p>
 
 <p>Those who choose to host extensions themselves instead of using the gallery will probably want to use autoupdate for their extensions as described below. You might want to make sure you are familiar with <a href="packaging.html">Packaging</a> first.</p>
 
diff --git a/chrome/common/extensions/docs/hosting.html b/chrome/common/extensions/docs/hosting.html
index f16e4b5..af4fa90 100644
--- a/chrome/common/extensions/docs/hosting.html
+++ b/chrome/common/extensions/docs/hosting.html
@@ -248,7 +248,8 @@
         <div id="static"><div id="pageData-title" class="pageData">Hosting</div>
 
 <p>
-If your extension is hosted in Google's gallery,
+If your extension is hosted in Google's
+<a href="https://chrome.google.com/extensions">gallery</a>,
 <em>ignore this page</em>.
 You don't need to worry about HTTP headers
 because the gallery handles them for you.
diff --git a/chrome/common/extensions/docs/manifest.html b/chrome/common/extensions/docs/manifest.html
index a318180..f9c3506 100644
--- a/chrome/common/extensions/docs/manifest.html
+++ b/chrome/common/extensions/docs/manifest.html
@@ -322,7 +322,7 @@ A plain text string
 that describes the extension.
 The description should be suitable for both
 the browser's extension management UI
-and the extension gallery.
+and the <a href="https://chrome.google.com/extensions">extension gallery</a>.
 </p>
 
 
@@ -351,7 +351,7 @@ A short, plain text string
 that identifies the extension.
 The name is used in the install dialog,
 extension management UI,
-and the extension gallery.
+and the <a href="https://chrome.google.com/extensions">extension gallery</a>.
 </p>
 
 <h3 id="permissions">permissions</h3>
diff --git a/chrome/common/extensions/docs/npapi.html b/chrome/common/extensions/docs/npapi.html
index 232b06d..8a861fa 100644
--- a/chrome/common/extensions/docs/npapi.html
+++ b/chrome/common/extensions/docs/npapi.html
@@ -262,7 +262,8 @@ allowing you to call into native binary code from JavaScript.
 
 </p><p>Code running in an NPAPI plugin has the full permissions of the current user and is not sandboxed or shielded from malicious input by Google Chrome in any way. You should be especially cautious when processing input from untrusted sources, such as when working with <a href="content_scripts.html#security-considerations">content scripts</a> or XMLHttpRequest.
 
-</p><p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the extension gallery.
+</p><p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the
+<a href="https://chrome.google.com/extensions">extension gallery</a>.
 
 </p><h2>Details</h2>
 
diff --git a/chrome/common/extensions/docs/packaging.html b/chrome/common/extensions/docs/packaging.html
index d26d789..0d631b2 100644
--- a/chrome/common/extensions/docs/packaging.html
+++ b/chrome/common/extensions/docs/packaging.html
@@ -278,6 +278,16 @@ for example, <code>myextension.crx</code>.
 </p>
 
 <p>
+<b>Note:</b>
+You might not need to package your extension.
+If you publish your extension using the
+<a href="https://chrome.google.com/extensions">gallery</a>,
+then the only reason to create your own <code>.crx</code> file
+would be to distribute a non-public version —
+for example, to alpha testers.
+</p>
+
+<p>
 When you package an extension,
 the extension is assigned a unique key pair.
 The public key is used as the identifier for the extension.
@@ -336,8 +346,8 @@ You'll need it later if you want to do any of the following:
 </p>
 <ul>
 <li><a href="#update">Update</a> the extension</li>
-<li>Import the extension into the extensions gallery,
-once the gallery becomes available</li>
+<li>Upload the extension to the
+<a href="https://chrome.google.com/extensions">extensions gallery</a> </li>
 </ul>
 
 <p>
diff --git a/chrome/common/extensions/docs/static/autoupdate.html b/chrome/common/extensions/docs/static/autoupdate.html
index 99fbd97..f865c1a 100644
--- a/chrome/common/extensions/docs/static/autoupdate.html
+++ b/chrome/common/extensions/docs/static/autoupdate.html
@@ -3,7 +3,7 @@
 
 <p>We want extensions to be autoupdated for some of the same reasons as Google Chrome itself: to incorporate bug and security fixes, add new features or performance enhancements, and improve user interfaces.</p>
 
-<p>For extensions packaged and distributed via the gallery, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themselves with the rest of this document.</p>
+<p>For extensions packaged and distributed via the <a href="https://chrome.google.com/extensions">gallery</a>, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themselves with the rest of this document.</p>
 
 <p>Those who choose to host extensions themselves instead of using the gallery will probably want to use autoupdate for their extensions as described below. You might want to make sure you are familiar with <a href="packaging.html">Packaging</a> first.</p>
 
diff --git a/chrome/common/extensions/docs/static/hosting.html b/chrome/common/extensions/docs/static/hosting.html
index 6e366a7..ff0b53f 100644
--- a/chrome/common/extensions/docs/static/hosting.html
+++ b/chrome/common/extensions/docs/static/hosting.html
@@ -1,7 +1,8 @@
 <div id="pageData-title" class="pageData">Hosting</div>
 
 <p>
-If your extension is hosted in Google's gallery,
+If your extension is hosted in Google's
+<a href="https://chrome.google.com/extensions">gallery</a>,
 <em>ignore this page</em>.
 You don't need to worry about HTTP headers
 because the gallery handles them for you.
diff --git a/chrome/common/extensions/docs/static/manifest.html b/chrome/common/extensions/docs/static/manifest.html
index a36626a..953d8df 100644
--- a/chrome/common/extensions/docs/static/manifest.html
+++ b/chrome/common/extensions/docs/static/manifest.html
@@ -61,7 +61,7 @@ A plain text string
 that describes the extension.
 The description should be suitable for both
 the browser's extension management UI
-and the extension gallery.
+and the <a href="https://chrome.google.com/extensions">extension gallery</a>.
 </p>
 
 
@@ -91,7 +91,7 @@ A short, plain text string
 that identifies the extension.
 The name is used in the install dialog,
 extension management UI,
-and the extension gallery.
+and the <a href="https://chrome.google.com/extensions">extension gallery</a>.
 </p>
 
 <h3 id="permissions">permissions</h3>
diff --git a/chrome/common/extensions/docs/static/npapi.html b/chrome/common/extensions/docs/static/npapi.html
index ecf3787..8d349ab 100644
--- a/chrome/common/extensions/docs/static/npapi.html
+++ b/chrome/common/extensions/docs/static/npapi.html
@@ -15,7 +15,8 @@ allowing you to call into native binary code from JavaScript.
 
 <p>Code running in an NPAPI plugin has the full permissions of the current user and is not sandboxed or shielded from malicious input by Google Chrome in any way. You should be especially cautious when processing input from untrusted sources, such as when working with <a href="content_scripts.html#security-considerations">content scripts</a> or XMLHttpRequest.
 
-<p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the extension gallery.
+<p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the
+<a href="https://chrome.google.com/extensions">extension gallery</a>.
 
 <h2>Details</h2>
 
diff --git a/chrome/common/extensions/docs/static/packaging.html b/chrome/common/extensions/docs/static/packaging.html
index 8b218fd..5115173 100644
--- a/chrome/common/extensions/docs/static/packaging.html
+++ b/chrome/common/extensions/docs/static/packaging.html
@@ -10,6 +10,16 @@ for example, <code>myextension.crx</code>.
 </p>
 
 <p>
+<b>Note:</b>
+You might not need to package your extension.
+If you publish your extension using the
+<a href="https://chrome.google.com/extensions">gallery</a>,
+then the only reason to create your own <code>.crx</code> file
+would be to distribute a non-public version &mdash;
+for example, to alpha testers.
+</p>
+
+<p>
 When you package an extension,
 the extension is assigned a unique key pair.
 The public key is used as the identifier for the extension.
@@ -68,8 +78,8 @@ You'll need it later if you want to do any of the following:
 </p>
 <ul>
 <li><a href="#update">Update</a> the extension</li>
-<li>Import the extension into the extensions gallery,
-once the gallery becomes available</li>
+<li>Upload the extension to the
+<a href="https://chrome.google.com/extensions">extensions gallery</a> </li>
 </ul>
 
 <p>