doc: clarify story in the deploy a service guide pass 2

Focus on the migration team and platform team.

doc/md/guides/deploy-a-service.mdx

@@ -12,17 +12,18 @@ import Admonition from '@theme/Admonition';
 
 Welcome to the Holos Deploy a Service guide.  In this guide we'll explore how
 Holos helps the platform team work efficiently with a migration team at the
-fictional [Bank of Holos] to migrate a service from an acquired company onto the
-bank's platform.
+fictional [Bank of Holos].  The migration team is responsible for migrating a
+service from an acquired company onto the bank's platform.  The platform team
+supports the migration team by providing safe and consistent methods to add the
+service to the bank's platform.
 
 We'll build on the concepts we learned in the [Quickstart] guide and explore how
 the migration team safely integrates a Helm chart from the acquired company into
-the bank's platform consistent with the policies defined by the platform team.
-
-We'll also see how the platform team uses Holos and CUE to define consistent and
-safe structures for Namespaces, AppProjects, and HTTPRoutes for other teams. The
-migration team uses these structures to integrate the Helm chart into the bank's
-platform in a self-service way, without filing tickets or interrupting the
+the bank's platform.  We'll also explore how the platform team uses Holos and
+CUE to define consistent and safe structures for Namespaces, AppProjects, and
+HTTPRoutes for the benefit of other teams. The migration team uses these
+structures to integrate the Helm chart into the bank's platform safely and
+consistently in a self-service way, without filing tickets or interrupting the
 platform team.
 
 ## What you'll need {#requirements}