Adds support for new-tab targeted loads initiated from the renderer.

services/README.md

Index: services/README.md
diff --git a/services/README.md b/services/README.md
index 24b7014ac24c7b2377d67b51c83f3d2c3912d328..2b52b2d1300bdfee69b33ffc93a6e6e558edc9ca 100644
--- a/services/README.md
+++ b/services/README.md
@@ -1,11 +1,11 @@
-Chrome Platform Services
+Chrome Foundation Services
 ====
 
 ### Overview
 
-This directory contains Chrome Platform Services. If you think of Chrome as a
-"portable OS," Chrome Platform Services can be thought of as that OS' "system
-services".
+This directory contains Chrome Foundation Services. If you think of Chrome as a
+"portable OS," Chrome Foundation Services can be thought of as that OS'
+foundational "system services" layer.
 
 Roughly each subdirectory here corresponds to a service that:
 
@@ -38,4 +38,16 @@ for each service, products consuming these services may package them
 differently, e.g. by combining them into a single package.
 
 ### High-level Design Doc
-https://docs.google.com/document/d/15I7sQyQo6zsqXVNAlVd520tdGaS8FCicZHrN0yRu-oU/edit#heading=h.p37l9e7o0io5
+https://docs.google.com/document/d/15I7sQyQo6zsqXVNAlVd520tdGaS8FCicZHrN0yRu-oU/edit#heading=h.p37l9e7o0io5
+
+### Relationship to other top-level directories in //
+
+Services can be thought of as integrators of library code from across the
+Chromium repository, most commonly //base and //mojo (obviously) but for each
+service also //components, //ui, etc in accordance with the functionality they
+provide.
+
+Not everything in //components is automatically a service in its own right.
+Think of //components as sort of like a //lib. Individual //components can
+define, implement and use mojom interfaces, but only //services have unique
+identities with the Mojo Shell.