Clarify components/README about when to create a component.

components/README

Index: components/README
diff --git a/components/README b/components/README
index 8112f6e25d7d1e750c27bd7c4b97482184259af8..199924adbca1a8fb4dae17e542b21022594abaad 100644
--- a/components/README
+++ b/components/README
@@ -1,8 +1,17 @@
-This directory is for features that are intended for reuse across multiple
-embedders (e.g., Android WebView and Chrome).
-
+This directory is for features that are intended for reuse. Example use cases:
+-code that is shared by Chrome on iOS and other Chrome platforms (since the iOS
+  port doesn't use src/chrome)
+-code that is shared between multiple embedders of content (e.g., Android
+  WebView and Chrome)
+-code that is shared between Blink and the browser process (since code in the
+  browser doesn't use Blink, while Blink doesn't include content or chrome to
+  avoid circular dependencies)
+
+In general, if some code is used by a directory "foo" and things above "foo" in
+the dependency tree, the code should probably live in "foo".
+
 By default, components can depend only on the lower layers of the Chromium
-codebase(e.g. base/, net/, etc.). Individual components may additionally allow
+codebase (e.g. base/, net/, etc.). Individual components may additionally allow
 dependencies on the content API and IPC; however, if such a component is used
 by Chrome for iOS (which does not use the content API or IPC), the component
 will have to be in the form of a layered component