Replace remaining shell references with service manager

services/README.md

 Chrome Foundation Services
 ====
 
 ### Overview
 
 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:
 
   * is a client of `//services/service_manager` with its own unique Identity.
   * could logically run a standalone process for security/performance isolation
     benefits depending on the constraints of the host OS.
 
 ### Service Directory Structure
 
 Individual services are structured like so:
 
     //services/foo/                   <-- Implementation code, may have subdirs.
-                  /public/    
+                  /public/
                          /cpp/        <-- C++ client libraries (optional)
                          /interfaces/ <-- Mojom interfaces
 
 ### Dependencies
 
 Code within `//services` may only depend on each other via each other's
 `/public/` directories, i.e. implementation code cannot be shared directly.
 
 Service code should also take care to tightly limit the dependencies on static
 libraries from outside of `//services`. Dependencies to large platform
@@ skipping 11 matching lines @@
 ### 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.
+identities with the Service Manager.