diff --git a/goals/ocata/remove-incubated-oslo-code.rst b/goals/ocata/remove-incubated-oslo-code.rst
index 5c422f0b2..e163e0f99 100644
--- a/goals/ocata/remove-incubated-oslo-code.rst
+++ b/goals/ocata/remove-incubated-oslo-code.rst
@@ -7,7 +7,7 @@
 The Oslo team has moved all previously incubated code from the
 ``openstack/oslo-incubator`` repository into separate library
 repositories and released those libraries to the Python Package
-Index. Many of our big tent project teams are still using the old,
+Index. Many of our official project teams are still using the old,
 unsupported, incubated versions of the code. The Oslo team has been
 working to remove that incubated code from projects, and the time has
 come to finish that work.
@@ -51,7 +51,7 @@ http://specs.openstack.org/openstack/oslo-specs/
 Current State / Anticipated Impact
 ==================================
 
-On 5 Aug 2016 a review of git repositories owned by big tent project
+On 5 Aug 2016 a review of git repositories owned by official projects
 showed:
 
 ::
diff --git a/goals/pike/deploy-api-in-wsgi.rst b/goals/pike/deploy-api-in-wsgi.rst
index f4053e9e2..a509f06aa 100644
--- a/goals/pike/deploy-api-in-wsgi.rst
+++ b/goals/pike/deploy-api-in-wsgi.rst
@@ -64,7 +64,7 @@ Reference documentation for the existing WSGI deployments:
 Current State / Anticipated Impact
 ==================================
 
-On 12 Jan 2017 a review of git repositories owned by big tent project
+On 12 Jan 2017 a review of git repositories owned by official projects
 showed the projects that don't support their control-plane API services deployed
 via WSGI:
 
diff --git a/reference/tags/stable_follows-policy.rst b/reference/tags/stable_follows-policy.rst
index 4dab82ed0..ce8962210 100644
--- a/reference/tags/stable_follows-policy.rst
+++ b/reference/tags/stable_follows-policy.rst
@@ -24,7 +24,7 @@ Application to current deliverables
 Rationale
 =========
 
-In the big tent, all project teams can create stable branches, with the
+All OpenStack project teams can create stable branches, with the
 name of their choice. However, some of those branches do not follow the
 `Stable branch policy`_: some approve backports that modify the behavior
 of the software, some backport new features, some do not actively backport
diff --git a/reference/tags/starter-kit_compute.rst b/reference/tags/starter-kit_compute.rst
index f13f094b5..f3e4f10ac 100644
--- a/reference/tags/starter-kit_compute.rst
+++ b/reference/tags/starter-kit_compute.rst
@@ -71,10 +71,10 @@ Starter Kit implies this is not the end point, but just a beginning.
 Why is this needed?
 -------------------
 
-The big tent has been great for expanding the scope and features that
-are part of OpenStack. However that has scared and confused many
-members of our community who used the integrated release as their
-starting point, and see that now going away. Smaller Operators,
+The 'big tent' project structure reform of 2014 has been great for expanding
+the scope and features that are part of OpenStack. However that has scared and
+confused many members of our community who used the integrated release as
+their starting point, and see that now going away. Smaller Operators,
 Trainers, Hobbyists all have been asking the question, "where do I
 start?".