diff --git a/docs/html/google/play/billing/gp-purchase-status-api.jd b/docs/html/google/play/billing/gp-purchase-status-api.jd index d6b251ea9d0af..c5b84616d0aa1 100644 --- a/docs/html/google/play/billing/gp-purchase-status-api.jd +++ b/docs/html/google/play/billing/gp-purchase-status-api.jd @@ -118,13 +118,13 @@ Purchase Status API. For security reasons, the app should not normally attempt t the purchase itself using the Purchase Status API.

If the backend server determines that the purchase is valid, it notifies the -app and grant access to the content. For improved performance, the backend servers -should store the purchase details and order status in a local database, updated a +app and grants access to the content. For improved performance, the backend servers +should store the purchase details and order status in a local database, updated at intervals or as-needed.

-

Keep in mind that users will want to be able to use your app at any time, including +

Keep in mind that users will want the ability to use your app at any time, including when there may be no network connection available. Make sure that your approach to -purchase verification takes account of the offline use-case.

+purchase verification accounts for the offline use-case.

Using the API Efficiently

@@ -154,7 +154,7 @@ minimize your access using the techniques below.

query each day to check the status of expiring subscriptions, then update the database. Note that: @@ -162,5 +162,6 @@ minimize your access using the techniques below.

By following those general guidelines, your implementation will offer the -best possible performance for users and minimize use of the Google Play Android -Developer API.

+best possible performance for users and minimize use of the Google Play Android +Developer API.