diff --git a/docs/README.md b/docs/README.md
index b35ccce..4e042a7 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -3,8 +3,8 @@
 XOS provides a framework for defining a set of declarative models and
 then using those models to manage a collection of components that have
 been configured into an operational system. XOS is itself deployed as
-a set of micro-services, collectively forming a
-*ControlPlane-as-a-Service* that:
+a set of micro-services, collectively forming an
+*Extensible Service Control Plane* that:
 
 * Serves as a single unifying interface to a collection of backend
   services, avoiding the management silos that otherwise result from
@@ -33,7 +33,7 @@
 
 * **End-to-End Service Chains in a Multi-Cloud:** XOS is being used
   to manage end-to-end service chains that span customer premises,
-  edge sites, and commodity clouds.
+  edge sites, Internet exchange points, and commodity clouds.
 
 For additional white papers describing XOS, see the project
 [wiki page](https://wiki.opencord.org/display/CORD/XOS+and+the+CORD+Controller).
diff --git a/docs/dev/synchronizers.md b/docs/dev/synchronizers.md
index cfb8ce7..d73d862 100644
--- a/docs/dev/synchronizers.md
+++ b/docs/dev/synchronizers.md
@@ -1,17 +1,17 @@
 # XOS Synchronizer Framework
 
-Synchronizers are the components of CORD that map the abstract declarative
+Synchronizers are the components of XOS that map the abstract declarative
 state about how the system is suppose to behave (as defined by the XOS data
 model) into the concrete operational state of the backend components that
 implement the system (e.g., VNFs, micro-services, SDN control applications).
 
 Writing a Synchronizer is half of the work required to on-board a service into
-CORD. First a model for the service is written as an [xproto](xproto.md)
+XOS. First a model for the service is written as an [xproto](xproto.md)
 specification, and then you implement a synchronizer that translates that model
 onto some backend component.
 
-To implement a Synchronizer, it is important to first understand the role 
-they play in CORD and the assumptions made about their behavior. The
+To implement a Synchronizer, it is important to first understand the role
+they play and the assumptions made about their behavior. The
 following three subsections address these issues. The first presents
 a set of [design guidelines](sync_arch.md) for how to write synchronizers,
 the second describes some of the [implementation details](sync_impl.md)
diff --git a/docs/install.md b/docs/install.md
index f319aac..85b77c3 100644
--- a/docs/install.md
+++ b/docs/install.md
@@ -10,7 +10,7 @@
 Helm client-side tool. If you are new to Kubernetes, we recommend this [tutorial](https://kubernetes.io/docs/tutorials/) as a good place to start.
 
 Although you are free to set up Kubernetes and Helm in whatever way
-makes sense for your system, the following walks you through an
+makes sense to you, the following walks you through an
 example installation sequence on  MacOS. It was tested on version 10.12.6.
 
 ## Prerequisites
@@ -98,7 +98,7 @@
 While downloading the simple `helm-charts` repository is sufficient
 for bringing up XOS, you may also want to download the XOS source
 code, for example, so you can walk through the
-[XOS tutorial](tutorial/basic_synchronizer.md). The easiest way to do
+[XOS tutorial](tutorials/basic_synchronizer.md). The easiest way to do
 this uses the `repo` tool, as described [here](repo.md).
 
 ## Bring Up XOS
@@ -178,7 +178,7 @@
 
 ## Next Steps
 
-This completes the installation process. At this point, you can
+This completes the installation process. At this point, you can either
 drill down on the internals of
-[Simple Example Service](simpleexampleservice/simple-example-service.md).
-
+[Simple Example Service](simpleexampleservice/simple-example-service.md),
+or you can work through the [XOS tutorial](tutorials/basic_synchronizer.md).
diff --git a/docs/repo.md b/docs/repo.md
index 62c2fa3..deb94a5 100644
--- a/docs/repo.md
+++ b/docs/repo.md
@@ -1,9 +1,9 @@
 # Download Source Code
 
-The easiest way to download source code for XOS -- including the
+The easiest way to download source code for XOS—including the
 XOS core, the XOS-related interfaces (e.g., GUI, TOSCA), the helm
 charts used to deploy XOS, and the model/synchronizers
-for the services being managed by XOS -- is to use the `repo` tool.
+for the services being managed by XOS—is to use the `repo` tool.
 
 ## Install repo
 
diff --git a/docs/use.md b/docs/use.md
index c719bc6..ac6ea70 100644
--- a/docs/use.md
+++ b/docs/use.md
@@ -1,7 +1,7 @@
 # Using XOS
 
-XOS has three inter-related aspects, and this section is
-organized accordingly.
+There are three inter-related aspects to on-boarding a service into
+XOS. This section is organized accordingly.
 
 * **Modeling Framework:** XOS defines a
   [modeling framework](dev/xproto.md), which