| Index: chrome/common/extensions/docs/templates/intros/contentSettings.html
|
| diff --git a/chrome/common/extensions/docs/templates/intros/contentSettings.html b/chrome/common/extensions/docs/templates/intros/contentSettings.html
|
| index 152562a402f5e15ed1783c50ef3386fe373e8783..343b0a7dcfe83d150714344a3d7c972ecef20fd6 100644
|
| --- a/chrome/common/extensions/docs/templates/intros/contentSettings.html
|
| +++ b/chrome/common/extensions/docs/templates/intros/contentSettings.html
|
| @@ -19,7 +19,7 @@ For example:</p>
|
| You can use patterns to specify the websites that each content setting affects.
|
| For example, <code>http://*.youtube.com/*</code> specifies youtube.com and all
|
| of its subdomains. The syntax for content setting patterns is the same as for
|
| -<a href="match_patterns.html">match patterns</a>, with a few differences:
|
| +<a href="match_patterns">match patterns</a>, with a few differences:
|
| <ul><li>For <code>http</code>,
|
| <code>https</code>, and <code>ftp</code> URLs, the path must be a wildcard
|
| (<code>/*</code>). For <code>file</code> URLs, the path must be completely
|
| @@ -137,5 +137,5 @@ tries to keep the identifiers stable across plug-in updates.
|
|
|
| <p>
|
| You can find samples of this API on the
|
| -<a href="samples.html#contentSettings">sample page</a>.
|
| +<a href="samples#contentSettings">sample page</a>.
|
| </p>
|
|
|