Rename managed service to Restate Cloud (#290)

* Rename managed service to Restate Cloud

* Fix urls for Restate cloud docs

docs/restate/managed_service.md → docs/restate/restate_cloud.md

@@ -3,15 +3,18 @@ sidebar_position: 7
 description: "Try out Restate without any servers."
 ---
 
-# Managed service
+# Restate Cloud
 
 If you're using Restate with a function as a service platform, it can be challenging to 
 continuously run the runtime in your infrastructure. To make Restate easier to test out,
-we offer a managed cluster to private beta users by request. If you'd like access,
-please email [[email protected]](mailto:[email protected]).
+we offer a managed cluster to users by request. 
+
+:::info Join the waitlist
+If you'd like to try out Restate Cloud, join the waitlist by filling out the [request form](https://restate.dev/get-restate-cloud/).
+:::
 
 ## SLA
-The managed service is intended to help people try out Restate, and **should never be used in
+Restate Cloud is intended to help people try out Restate, and **should never be used in
 production. We offer no promises of data durability or uptime.**
 
 ## Using your cluster
@@ -94,7 +97,7 @@ for more tips.
 ## Giving permission for your cluster to Invoke your Lambdas
 Managed service clusters by default assume a role in Restate's AWS account: `arn:aws:iam::663487780041:role/restate-dev`.
 However, allowing this role to invoke your Lambda via its resource policy is dangerous and not recommended, as this will
-allow *any* managed cluster to invoke your Lambda, not just yours!
+allow *any* Restate Cloud cluster to invoke your Lambda, not just yours!
 
 Instead, cross account Lambda access should be achieved with [Role Chaining](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html).
 First, set up a role on one your own AWS accounts that Restate will assume when calling your Lambda. This role needs

docs/services/deployment/lambda/lambda-java.mdx

@@ -48,7 +48,7 @@ Then upload the generated Jar to AWS Lambda, and configure `MyLambdaHandler` as
 ## Managed service
 If you'd prefer not to manage a runtime instance, we are trialing a managed service that lets you work
 with Lambda services without running any infrastructure or even an API gateway.
-See [the documentation](/restate/managed_service) for more details.
+See [the documentation](/restate/restate_cloud) for more details.
 
 ## Discovery of services
 

docs/services/deployment/lambda/lambda-typescript.mdx

@@ -31,7 +31,7 @@ By default, this is also the case for the Lambda functions developed with the Re
 ## Managed service
 If you'd prefer not to manage a runtime instance, we are trialing a managed service that lets you work
 with Lambda services without running any infrastructure.
-See [the documentation](/restate/managed_service) for more details.
+See [the documentation](/restate/restate_cloud) for more details.
 
 ## Discovery of services