diff --git a/docs/html/google/play/billing/billing_admin.jd b/docs/html/google/play/billing/billing_admin.jd index f1e4ec434d4cb..6277edafcf1b0 100644 --- a/docs/html/google/play/billing/billing_admin.jd +++ b/docs/html/google/play/billing/billing_admin.jd @@ -153,8 +153,7 @@ number of in-app items.

  • Description

    The description is a long descriptor for the item. For example, "Instantly puts creatures to - sleep. Does not work on angry elves." Every item must have a description. The description is - visible to users during checkout. Descriptions can be up to 80 characters in length.

    + sleep. Does not work on angry elves." Every item must have a description. Descriptions can be up to 80 characters in length.

  • Price

    You must provide a default price in your home currency. You can also provide prices in other diff --git a/docs/html/google/play/billing/billing_overview.jd b/docs/html/google/play/billing/billing_overview.jd index 581c648e5e589..301d9119a4591 100644 --- a/docs/html/google/play/billing/billing_overview.jd +++ b/docs/html/google/play/billing/billing_overview.jd @@ -130,13 +130,6 @@ Google Play sends your application the purchase details, such as the order number, the order date and time, and the price paid. At no point does your application have to handle any financial transactions; that role is provided by Google Play.

    - -

    - Figure 1. Applications initiate In-app Billing requests -through their own UI (first screen). Google Play responds to the request by -providing the checkout user interface (middle screen). When checkout is -complete, the application resumes. -

    Sample Application

    To help you integrate In-app Billing into your application, the Android SDK