Be more specific regarding what Vespa Cloud manage of resources within a Enclave account

Author: ean

en/cloud/enclave/aws-getting-started.md

@@ -12,25 +12,22 @@ Setting up Vespa Cloud Enclave requires:
    Go through the [AWS tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started) as needed.
 4. Deployment of a Vespa application.
 
-
 ### 1. Vespa Cloud Tenant setup
 
 Register at [Vespa Cloud](https://console.vespa-cloud.com) or use an existing tenant.
 Note that the tenant must be on a [paid plan](https://vespa.ai/pricing/).
 
-
 ### 2. Onboarding
 
 Contact [[email protected]](mailto:[email protected]) stating which tenant should be on-boarded to use Vespa Cloud Enclave.
 Also include the [AWS account ID](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html#FindAccountId)
 to associate with the tenant.
 
 {% include note.html content='We recommend using a _dedicated_ account for your Vespa Cloud Enclave.
-Resources in this account will be fully managed by Vespa Cloud.' %}
+Vespa Cloud will manage resources in the Enclave VPCs created in the AWS resource provisioning step. Primarily EC2 instances, load balancers and service endpoints.' %}
 
 One account can host all your Vespa applications, there is no need for multiple tenants or accounts.
 
-
 ### 3. Configure AWS Account
 
 The same AWS account used in step two must be prepared for deploying Vespa applications.
@@ -56,7 +53,6 @@ features you must re-apply your terraform templates with the latest release.
 The [notification system](/en/cloud/notifications.html)
 will let you know when a new release is available.
 
-
 ### 4. Deploy a Vespa application
 
 By default, all applications are deployed on resources in Vespa Cloud accounts.
@@ -73,7 +69,6 @@ Useful resources are [getting started](/en/cloud/getting-started)
 and [migrating to Vespa Cloud](/en/cloud/migrating-to-cloud.html) -
 put _deployment.xml_ next to _services.xml_.
 
-
 ## Next steps
 
 After a successful deployment to the [dev](https://cloud.vespa.ai/en/reference/environments.html#dev) environment,
@@ -83,7 +78,6 @@ The _dev_ environment is ideal for this, with rapid deployment cycles.
 For production serving, deploy to the [prod](https://cloud.vespa.ai/en/reference/environments.html#prod) environment -
 follow the steps in [production deployment](/en/cloud/production-deployment.html).
 
-
 ## Enclave teardown
 
 To tear down a Vespa Cloud Enclave system, do the steps above in reverse order: