From 6390fa6bdf50a3bf10cd6c54328397fe709f7c37 Mon Sep 17 00:00:00 2001 From: Scott Main Date: Tue, 14 Dec 2010 10:39:35 -0800 Subject: [PATCH] cherrypick Change-Id: I653e91a47979b24e7ecfcbce013c4ffaaa3c55ee docs: fix bug 3273882 Change-Id: Ie53ba246c39bf448bfe199ae3754e50749ceb340 --- docs/html/guide/practices/screens_support.jd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/html/guide/practices/screens_support.jd b/docs/html/guide/practices/screens_support.jd index f503749d2ff14..5738bd64ec699 100644 --- a/docs/html/guide/practices/screens_support.jd +++ b/docs/html/guide/practices/screens_support.jd @@ -195,10 +195,10 @@ its characteristics.

Illustration of how the Android platform maps actual screen densities and sizes to generalized density and size configurations.

-

Although the platform lets your application provide layouts and resources for -generalized size-density configurations, you do not necessarily need to do write -custom code or provide custom resources for each of the nine supported -configurations. The platform provides robust compatibility features, described +

Although the platform lets your application provide customized resources for +the various size and density configurations, you do not need to do write +custom code or provide custom resources for every combination of screen size and density. +The platform provides robust compatibility features, described in the sections below, that can handle most of the work of rendering your application on any device screen, provided that you've implemented your application UI properly. For more information about how to implement a UI that