`.
-3. Parse the JSON response, verify the license and store the result.
-
-```js
-var CWS_LICENSE_API_URL = 'https://www.googleapis.com/chromewebstore/v1.1/userlicenses/';
-var req = new XMLHttpRequest();
-req.open('GET', CWS_LICENSE_API_URL + chrome.runtime.id);
-req.setRequestHeader('Authorization', 'Bearer ' + token);
-req.onreadystatechange = function() {
- if (req.readyState == 4) {
- var license = JSON.parse(req.responseText);
- verifyAndSaveLicense(license);
- }
-}
-req.send();
-```
-
-Note: You cannot offer free trial experiences for Themes because themes do not execute any JavaScript and cannot verify a license.
-
-### Handling and parsing the response {: #parse-response }
-
-The response you get from the license server tells you three things: whether the user has access,
-the level of access the user should have, and how much longer the response is valid. If you just
-want to know whether the user has access, check the value of the `result` field. If you want to know
-whether the user should get a free trial version, check the value of the `accessLevel` field.
-
-Sample JSON license object
-
-```json
-{
- "kind": "chromewebstore#license",
- "itemId": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
- "createdTime": "1377660091254",
- "result": true,
- "accessLevel": "FULL",
- "maxAgeSecs": "2052"
-}
-```
-
-| Field Name | Description |
|---|
| kind | Identifies a Chrome Web Store license |
| itemId | Your app or extension ID |
| createdTime | The date that the license was created, returned as a Unix timestamp. You can use to limit functionality of a free trial to a specific period of time. |
| result | Whether the user has a license (full or trial), true or false |
| accessLevel | FREE_TRIAL, FULL or NONE |
| maxAgeSecs | The length of time the response is valid for, once that time has passed your app should query the license server again to check whether the user's access has changed. |
-
-### Caching the response {: #cache-response }
-
-To improve the performance and avoid running into rate limits, you should cache the license data
-locally using the [`chrome.storage.sync`][15] API and only refresh it on a periodic basis. By
-storing the license data in the sync data, it will be synced across all machines that the users is
-logged into.
-
-In addition, do not block the user interface or lock the user out of your Chrome App or Extension
-while waiting for the licensing server to respond, but instead, allow the user to continue for a
-limited grace period until a response is received. Providing a grace period of at least a day or two
-will ensure that your Chrome App or Extension continues to work properly in an offline situation
-where the user may not be connected to the network.
-
-## Handling the free trial experience {: #handling-trial }
-
-If you decide to offer a free trial to users, there are several ways that you can allow users to try
-before they make the purchase. The two most common ways are providing full access for a limited
-time, or offering a limited feature set. Of course, you can also combine these two, or provide your
-own incentives to encourage users to upgrade to the paid version.
-
-### Limited time access {: #trial-limited-time }
-
-The license API makes it easy to provide a limited time trial experience by including the date the
-license was first issued to the user. Comparing the `createdDate` to the current date will tell you
-how long the user has been using the free trial.
-
-```js
-var licenseStatus;
-if (license.result && license.accessLevel == "FULL") {
- console.log("Fully paid & properly licensed.");
- licenseStatus = "FULL";
-} else if (license.result && license.accessLevel == "FREE_TRIAL") {
- var daysAgoLicenseIssued = Date.now() - parseInt(license.createdTime, 10);
- daysAgoLicenseIssued = daysAgoLicenseIssued / 1000 / 60 / 60 / 24;
- if (daysAgoLicenseIssued <= TRIAL_PERIOD_DAYS) {
- console.log("Free trial, still within trial period");
- licenseStatus = "FREE_TRIAL";
- } else {
- console.log("Free trial, trial period expired.");
- licenseStatus = "FREE_TRIAL_EXPIRED";
- }
-} else {
- console.log("No license ever issued.");
- licenseStatus = "NONE";
-}
-```
-
-Note: After major updates or a significant period of time, you may want to allow the user to try your item again so they can try the new features and see how the item has changed.
-
-### Limited feature set {: #trial-limited-feature }
-
-Another way that you can provide a free trial to users is by offering them a limited feature set
-until they've upgraded to the paid version. For example, you might limit the number of files open at
-any given time, or the total number of files that the user can edit before being prompted for
-payment.
-
-## Migrating from a free to a paid experience {: #free2paid }
-
-If you decide to migrate from a free experience to a paid experience, you should consider what
-experience you want to provide for any user who installed your item prior to the change. We strongly
-recommend grandfathering these users into the full, paid experience though the decision is yours.
-
-Users who installed your item prior to the change will have a `FREE_TRIAL` license. To determine if
-a user installed your item prior to the price change, you can check the `createdTime` value in the
-license to determine when they first installed it.
-
-## Sample Chrome App {: #sample-app }
-
-For a simple Chrome App that demonstrates how to use the Chrome Web Store Licensing API, see:
-
-- [source code][16]
-- [published app][17]
-
-You can install and run the published app from the Chrome Web Store to try out free trial
-experience.
-
-[1]: /docs/webstore/payments-iap
-[2]: #before-starting
-[3]: #using-otps
-[4]: #verifying-payment
-[5]: #free2paid
-[6]: #sample-app
-[7]: https://payments.google.com/merchant/signup
-[8]: /docs/webstore/pricing#seller
-[9]: https://chrome.google.com/webstore/developer/dashboard
-[10]: https://cloud.google.com/console
-[11]: #update-manifest
-[12]: /docs/webstore/pricing#matrix
-[13]: /docs/extensions/reference/app_identity
-[14]: https://code.google.com/apis/console
-[15]: /docs/extensions/reference/storage
-[16]: https://github.com/GoogleChrome/chrome-app-samples/tree/master/one-time-payment
-[17]: https://chrome.google.com/webstore/detail/one-time-payment-sample/ebcgmmcbgnpoclkoibogeiokfdmjbbob
diff --git a/site/en/docs/webstore/payments-iap/index.md b/site/en/docs/webstore/payments-iap/index.md
deleted file mode 100644
index 2b71c97456ef..000000000000
--- a/site/en/docs/webstore/payments-iap/index.md
+++ /dev/null
@@ -1,373 +0,0 @@
----
-layout: "layouts/doc-post.njk"
-title: "In-App Payments with Payments Merchant Account and the Chrome Web Store API"
-date: 2014-02-28
-updated: 2018-06-15
-description: How to handle in-app purchases.
----
-
-Important: Chrome will be removing support for Chrome Apps on Windows, Mac, and Linux. Chrome OS will continue to support Chrome Apps. Additionally, Chrome and the Web Store will continue to support extensions on all platforms.
Read the announcement and learn more about
migrating your app.
-
-You can use a [Payments Merchant Account][3] and the Chrome Web Store API to sell virtual goods
-within your Chrome App or Chrome Extension.
-
-The [Chrome Web Store Developer Dashboard][4] makes it easy to easy to create and manage virtual
-goods. You can provide localized descriptions for each product and offer items in local currencies.
-It also can help you to verify and manage licenses for the virtual goods purchased by each user.
-
-In order to sell virtual goods, you'll need to:
-
-1. Create a [Google Payments Merchant account][5].
-2. Create the items you wish to sell via the Developer Dashboard in the Chrome Web Store.
-3. Include the appropriate [`buy.js`][buy-js] file in your package.
-4. Wire up the sales flow.
-
-The [`buy.js`][buy-js] file provides four functions:
-
-[`google.payments.inapp.getSkuDetails`][8]
-
-: Returns an array of active items provided by your product from the Chrome Web Store. Maps to the Web
- Store API [In-App Products List Method][9].
-
-[`google.payments.inapp.buy`][10]
-
-: Purchases an item.
-
-[`google.payments.inapp.getPurchases`][11]
-
-: Returns an array of items purchased by the user. Maps to the Web Store API [Payments List
-Method][12].
-
-[`google.payments.inapp.consumePurchase`][13]
-
-: Consumes an item.
-
-
-
-## Purchase flow {: #purchase-flow }
-
-You can use `google.payments.inapp.getSkuDetails` to get the list of available products, and then
-show those to the user.
-
-{% Img src="image/BrQidfK9jaQyIHwdw91aVpkPiib2/EZULNCIw4clveEnCqfvT.png",
- alt="A screenshot of an example purchase flow.", height="566", width="800" %}
-
-Best Practice: Before showing the user all of the items that are available, compare the list of items that they've already purchased (using google.payments.inapp.getPurchases) and provide some indication that the items have already been purchased.
-
-When a customer clicks a **Purchase** button within your Chrome App or Extension, Chrome uses the
-Google account of the user signed into Chrome to display the Google payment processing window.
-
-When the user clicks the **Accept and Buy** button in the payment processing window, the Google
-payment server processes the payment and displays a purchase confirmation dialog to the user. The
-`success` or `failure` callback is invoked appropriately.
-
-Items uploaded to the Web Store are unable to be purchased through the same developer account.
-Instead, use a trusted tester account to run a trial purchase flow.
-
-Note: if the user doesn't have a Google account, they are taken through the sign-up flow.
-
-## Using the Chrome Web Store API for In-App Purchases {: #how-to-use }
-
-The Chrome Web Store (CWS) API can be used to handle in-app purchases without the use of any
-server-side coding as was previously required by the deprecated Google Wallets for Digital Goods
-API.
-
-- The Chrome Web Store handles the list of virtual goods available for sale, eliminating the need to
- create, store, or manage JSON Web Tokens.
-- You can get the list of available virtual goods through the `getSkuDetails` function.
-- You must include the [`buy.js`][buy-js] library with your package, and load the library from its
- location in your package.
-- You must call the `buy()` method with an extra parameter called `parameters`.
-- The UI to process payments is displayed in a separate window, rather than in an iframe.
-- The Chrome Web Store manages the list of purchased virtual goods (licenses) for each user and
- exposes that list to you through the `getPurchases()` function.
-
-### Setting up your account {: #setup-account }
-
-In order to use the Chrome Web Store API to handle in-app purchases, you'll need to create a [Google
-Payments Merchant account][16].
-
-Once you've created the Merchant account, it will be automatically associated with your Chrome App
-or Extension listing in the Chrome Web Store.
-
-### Creating and Managing your virtual goods {: #create-digital-goods }
-
-Before you can sell any virtual goods, you need to create the list of in-app products that are
-available for purchase. The Chrome Web Store simplifies this process for us by providing an
-interface for creating in-app products and licenses. This interface can be found in the In-app
-Products tab in the Chrome app listing page of the Chrome Web Store Developer Dashboard. Once you
-have created your in-app products, you can continue to use this interface to manage them.
-
-{% Img src="image/BrQidfK9jaQyIHwdw91aVpkPiib2/BboETdjxoq0zsejDhhkL.png",
- alt="A screenshot of the in-app product dashboard", height="614", width="800" %}
-
-1. Open the [Chrome Web Store Developer Dashboard][17] and edit the listing for your app.
-2. Switch to the **In-app Products** tab at the top of the page.
-3. Click **Add new product**.
-4. Provide the necessary information:
-
- Product ID
-
- : An identifier (SKU) you'll use to identify that specific product. Product IDs must start with a
- lowercase letter or number and can only contain lowercase letters(a-z), numbers(0-9), dots(.)
- and underscores(\_).
-
- Title
-
- : A friendly name of your product that will be shown to users on the purchase confirmation page.
-
- Description
-
- : A short description of the item that will be shown to users on the purchase confirmation page.
-
-5. Choose the price tier or create a custom price within the tier range that you wish to sell the
- item for.
-6. Click **Save** to save the item.
-7. Activate by changing the state to **Active**.
-
-If you want to prepare digital goods for release on a specific day, you can leave the state set to
-`Inactive` until you're ready to make those available. This means you can launch new features or
-levels, but keep them hidden until you're ready.
-
-- You can have up to 100 items (active, inactive, or archived) at any given time.
-- You should move older items that are no longer for sale to archived.
-- Be careful when deleting items as users may already have purchased them and may lose their
- license.
-- Once a product ID has been used, it cannot be used again, even if it has been deleted.
-
-#### Querying available items {: #query-items }
-
-The `getSkuDetails` function returns a list of all active virtual goods available from the Chrome
-Web Store available for purchase by the user, including the product ID (SKU), title, description,
-and price. You can provide an optional SKU argument to the function, which will then return only the
-details for that specific item.
-
-```js
-google.payments.inapp.getSkuDetails({
- 'parameters': {'env': 'prod'},
- 'success': onSkuDetails,
- 'failure': onSkuDetailsFail
-});
-```
-
-Note: The parameters field is required and must be set to
{'env': 'prod'} to tell Chrome to use the production instance of the API. Review the
Testing your app section for details on how to test your app without incurring a charge. You can learn about adding trusted testers when you
publish your app here.
-
-The response will look like:
-
-```json
-{
- "response": {
- "details": {
- "kind": "chromewebstore#inAppProductList",
- "inAppProducts": [
- {
- "kind": "chromewebstore#inAppProduct",
- "sku": "70darkchocolate",
- "item_id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
- "type": "inapp",
- "state": "ACTIVE",
- "prices": [
- {
- "valueMicros": "990000",
- "currencyCode": "USD",
- "regionCode": "US"
- }
- ],
- "localeData": [
- {
- "title": "Dark Chocolate (70%)",
- "description": "The best chocolate available.",
- "languageCode": "all"
- }
- ]
- },
- {
- ...
- }
- ]
- }
- }
-}
-```
-
-
-
-For example, you might want to list the details of each object you get back from the function:
-
-```js
-function onSkuDetails(skus) {
- var products = response.response.details.inAppProducts;
- var count = products.length;
- for (var i = 0; i < count; i++) {
- addProductToUI(products[i]);
- }
-}
-```
-
-#### Responding to a purchase request {: #respond-to-purchase }
-
-The following code snippet shows how to initiate the purchase flow for an item managed through the
-Chrome Web Store:
-
-```js
-var sku = "giant_tv";
-google.payments.inapp.buy({
- 'parameters': {'env': 'prod'},
- 'sku': sku,
- 'success': onPurchase,
- 'failure': onPurchaseFail
-});
-```
-
-When the purchase completes, Chrome will call the defined callback with the a parameter that looks
-like:
-
-```json
-{
- "jwt": "eyJhb...0oFuU",
- "request": {
- "cartId": "00000000000000000000.0000000000000000000"
- },
- "response": {
- "orderId": "00000000000000000000.0000000000000000000"
- }
-}
-```
-
-#### Verifying what items the user has purchased {: #get-purchases }
-
-If you want to verify that the user has purchased an item and has a current license, you can call
-`google.payments.inapp.getPurchases`. The function will always return the most up to date
-information, and will reflect if the purchase was cancelled by the user, or refunded through the
-[Payments Merchant console][21].
-
-```js
-google.payments.inapp.getPurchases({
- 'parameters': {'env': 'prod'},
- 'success': onLicenseUpdate,
- 'failure': onLicenseUpdateFail
-});
-```
-
-The Chrome Web Store will return the list of SKUs that the user has purchased:
-
-```json
-{
- "response": {
- "details": [
- {
- "kind": "chromewebstore#payment",
- "itemId": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
- "sku": "giant_tv",
- "createdTime": "1387221267248",
- "state": "ACTIVE"
- }
- ]
- }
-}
-```
-
-
-
-```js
-function onLicenseUpdate(licenses) {
- var licenses = response.response.details;
- var count = licenses.length;
- for (var i = 0; i < count; i++) {
- var license = licenses[i];
- saveLicense(license);pay
- }
-}
-```
-
-#### Consume purchased item {: #consume-purchase }
-
-If you want to consume an item that a user has purchased, so that the user can purchase again, you
-can call `google.payments.inapp.consumePurchase`. The function will change the license status from
-"active" to "cancelled_by_developer".
-
-```js
-google.payments.inapp.consumePurchase({
- 'parameters': {'env': 'prod'},
- 'sku': sku,
- 'success': onConsume,
- 'failure': onConsumeFail
-});
-```
-
-After consuming a license, if you make a `getPurchase` call, you'll get:
-
-```json
-{
- "response": {
- "details": [
- {
- "kind":"chromewebstore#payment",
- "itemId":"bgjmpalnjpigmmelcdiakkfofbofhege",
- "sku":"bullet",
- "createdTime":"1424800615789",
- "state":"CANCELLED_BY_DEVELOPER"
- }
- ]
- }
-}
-```
-
-Note: The consumePurchase API won't work with in-app subscriptions.
-
-## Subscriptions {: #subscription }
-
-Developers can also offer in-app subscriptions.
-
-If a free trial is specified, users will go through the purchase flow for a 0 amount, and the first
-recurring order will occur automatically as soon as the free trial period expires. Note that once a
-subscription item is activated, developers can no longer inactivate it or change the price or
-period. However, the free trial period can be changed at any time. While non-subscription items will
-have the type "inapp", subscription items will have the type "subs". For example, getSkuDetails will
-return a result for a subscription item that resembles:
-
-```json
-{
-"kind":"chromewebstore#inAppProduct",
-"sku":"banana",
-"item_id":"bgjmpalnjpigmmelcdiakkfofbofhege",
-"type":"subs",
-"state":"ACTIVE",
-"prices":[{"valueMicros":"990000","currencyCode":"USD","regionCode":"US"}],"localeData":[{"title":"Bullet","description":"a bullet","languageCode":"en-US"}
-```
-
-## Testing purchases {: #testing }
-
-Prior to publishing your app to the world, you can test the In-App Payment experience by publishing
-it only to **trusted testers**. When your app is published to trusted testers, the purchase flow
-will proceed normally, except they will not be charged.
-
-## Sample Chrome App {: #sample-app }
-
-For a simple app that demonstrates how to use CWS API for in-app products, you can download the
-[source code][23] here.
-
-Note, this app is not published in the Chrome Web Store to prevent accidental purchases.
-
-[1]: http://blog.chromium.org/2016/08/from-chrome-apps-to-web.html
-[2]: /apps/migration
-[3]: https://payments.google.com/merchant/signup
-[4]: https://chrome.google.com/webstore/developer/dashboard
-[5]: #setup-account
-[8]: /docs/webstore/payments-iap#query-items
-[9]: /docs/webstore/webstore_api/inAppProducts/list
-[10]: /docs/webstore/payments-iap#respond-to-purchase
-[11]: /docs/webstore/payments-iap#get-purchases
-[12]: /docs/webstore/webstore_api/payments/list
-[13]: /docs/webstore/payments-iap#consume-purchase
-[14]: /docs/webstore/pricing
-[16]: https://payments.google.com/merchant/signup
-[17]: https://chrome.google.com/webstore/developer/dashboard
-[18]: /docs/webstore/payments-iap#testing
-[19]: /docs/webstore/publish#testaccounts
-[20]: /docs/webstore/webstore_api/inAppProducts#resource
-[21]: https://payments.google.com/merchant
-[22]: /docs/webstore/webstore/webstore_api/payments/list
-[23]: https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/managed-in-app-payments
-
-[buy-js]: https://github.com/GoogleChrome/chrome-extensions-samples/blob/main/apps/samples/managed-in-app-payments/scripts/buy.js
diff --git a/site/en/docs/webstore/rating/index.md b/site/en/docs/webstore/rating/index.md
index 1be4463d6b3b..e1a0e345b963 100644
--- a/site/en/docs/webstore/rating/index.md
+++ b/site/en/docs/webstore/rating/index.md
@@ -11,27 +11,31 @@ description: Guidelines about how the Chrome Web Store rates the maturity of con
[Branding Guidelines][3] | **Rating Guidelines** | [Program Policies][4] | [User Data FAQ][5] |
[Developer Agreement][6]
-Content ratings help users determine whether your application and its content are mature in nature.
-Ratings are not intended to reflect the quality or complexity of your app.
-
-As the developer, you are ultimately responsible for rating your application appropriately. Use the
-following rules as guidance in determining whether your app should be rated "Mature." When
-determining your app's rating, consider all the content in your app, including user generated
-content and ads, and content that your app links to. Note that regardless of the rating you give
-your app, all applications must still adhere to the terms of the Chrome Web Store Program Policy and
+Content ratings help users determine whether your extension and its content are mature in nature.
+Ratings are not intended to reflect the quality or complexity of your extension.
+
+As the developer, you are ultimately responsible for rating your extension appropriately. Use the
+following rules as guidance in determining whether your extension should be rated "Mature." When
+determining your extension's rating, consider all the content in your extension, including user generated
+content and ads, and content that your extension links to. Note that regardless of the rating you give
+your extension, all extensions must still adhere to the terms of the Chrome Web Store Program Policy and
the Chrome Web Store Developer Agreement.
## Sexual and suggestive content
Apps that focus on sexual content or sexually suggestive content should be rated "Mature." For
-example, an app that is a collection of images of men or women in lingerie posing suggestively
+example, an extension that is a collection of images of men or women in lingerie posing suggestively
should be rated "Mature." Note that pornography and sexually explicit content are not allowed in the
Chrome Web Store.
-As you consider how to rate your app, here is more guidance on apps that we would consider to be
+As you consider how to rate your extension, here is more guidance on extensions that we would consider to be
sexually explicit, mature, and not mature.
-| Not mature | Mature | Sexually explicit (not allowed) |
|---|
- Images of people kissing and hugging
- Dating app that is not focused on sexual relations
- App to help a woman choose the right bra size
| - Close-up images of people wearing thongs
- Apps with sexual themes like adult "Truth or Dare" apps
- Sex position app with no porn, but has detailed descriptions
| - Apps containing images or videos with nudity or sex acts
- Apps that contain prominent links to porn sites
|
+| Not mature | Mature | Sexually explicit (not
+allowed) |
|---|
- Images of people kissing and hugging
- Dating extension that
+is not focused on sexual relations
- App to help a woman choose the right bra
+size
| - Close-up images of people wearing thongs
- Apps with sexual
+themes like adult "Truth or Dare" extensions
- Sex position extension with no porn, but has detailed descriptions
| - Apps containing images or videos with nudity or sex acts
- Apps that contain prominent links to porn sites
|
## Strong language
diff --git a/site/en/docs/webstore/samples/index.md b/site/en/docs/webstore/samples/index.md
deleted file mode 100644
index ac4dad902045..000000000000
--- a/site/en/docs/webstore/samples/index.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: "layouts/doc-post.njk"
-title: "Samples"
-date: 2017-08-30
-description: Code samples demonstrating how to use the Chrome Web Store Licensing API.
----
-
-The following basic samples demonstrate how to use the Chrome Web Store Licensing API. Each sample
-app obtains the user's OpenID identifier (as described in [Identifying the User][1]) and makes an
-OAuth request with it to the Licensing API (as described in [Checking for Payment][2]) to determine
-whether the user has paid for the app.
-
-## Java {: #java }
-
-A sample Java app that runs on Google App Engine and takes advantage of App Engine's native OpenID
-support. To enable OAuth signing, this app uses the [OAuth Signpost][3] library.
-
-This sample is featured in the [Licensing API tutorial][4].
-
-You can browse the source, download all the files, or see the app in action:
-
-- [Browse code repository][5]
-- [Download ZIP file][6]
-- [Try live demo][7]
-
-## Python {: #python }
-
-A sample Python app that runs on Google App Engine and takes advantage of App Engine's native OpenID
-support. To enable OAuth signing, this app uses the [Python OAuth2][8] library.
-
-You can browse the source or download all the files:
-
-- [Browse code repository][9]
-- [Download ZIP file][10]
-
-## PHP {: #php }
-
-A sample PHP app that uses the [LightOpenId][11] and [OAuth for PHP][12] libraries.
-
-You can browse the source, download all the files, or see the app in action:
-
-- [Browse code repository][13]
-- [Download ZIP file][14]
-- [Try live demo][15]
-
-[1]: /docs/webstore/identify_user
-[2]: /docs/webstore/check_for_payment
-[3]: http://code.google.com/p/oauth-signpost/
-[4]: /docs/webstore/get_started
-[5]:
- http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/apps/hello-java/
-[6]:
- http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/apps/hello-java.zip
-[7]: http://hellolicense.appspot.com/
-[8]: http://github.com/simplegeo/python-oauth2
-[9]:
- http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/apps/hello-python/
-[10]:
- http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/apps/hello-python.zip
-[11]: http://gitorious.org/lightopenid
-[12]: http://oauth.googlecode.com/svn/code/php/
-[13]:
- http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/apps/hello-php/
-[14]:
- http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/apps/hello-php.zip
-[15]: http://googlecodesamples.com/chrome_webstore/hello-php/index.php
diff --git a/site/en/docs/webstore/troubleshooting/index.md b/site/en/docs/webstore/troubleshooting/index.md
index db0d009e0525..4bed957327b0 100644
--- a/site/en/docs/webstore/troubleshooting/index.md
+++ b/site/en/docs/webstore/troubleshooting/index.md
@@ -604,7 +604,7 @@ Keyword Spam: We don't allow extensions with misleading, improperly formatted, n
irrelevant, excessive, or inappropriate metadata, including but not limited to the extension's
description, developer name, title, icon, screenshots, and promotional images. Developers must
provide a clear and well-written description. We also don't allow unattributed or anonymous user
-testimonials in the app's description.
+testimonials in the extension's description.
```
This policy is to ensure quality of the products on the Chrome Web Store and prevent products from