docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx

@@ -3,11 +3,13 @@ title: How to migrate your workloads to Scaleway Serverless Containers
 description: This page gives recommendations and steps to migrate your workloads from Kubernetes or conventional virtual machines to Scaleway Serverless Containers
 tags: migration switch change adopt serverless containers go serverless try k8s vm
 dates:
-  validation: 2025-08-25
-  posted: 2025-08-25
+  validation: 2025-08-27
+  posted: 2025-08-27
 ---
 
-This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers). This guide covers the [core concepts](#why-migrating-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration.
+This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines, and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers).
+
+This guide covers the [core concepts](#why-migrating-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration.
 
 ## Why migrating to Serverless Containers
 
@@ -58,7 +60,7 @@ Deploying your first service to Serverless Containers is straightforward. Here
 
 1. **Containerize your Application**: If you haven't already, package your application into a container image using a Dockerfile.
 
-2. **Push your image to a Registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to push your container image to the Scaleway Container Registry.
+2. **Push your image to a Registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images.
 
 3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway Console.
 
@@ -80,35 +82,35 @@ Since Serverless Containers are stateless, you cannot rely on the local filesyst
 
 **Use external storage**
 
-For file storage, use an object storage service like Scaleway Object Storage (/object-storage/quickstart/)
+To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/).
 
 **Externalize state**
 
-For application state, use a managed database, cache like Redis(/managed-databases-for-redis/how-to/create-a-database-for-redis/) or a message queues(/queues/quickstart/)
+For application state, use a managed database, cache like [Redis](/managed-databases-for-redis/how-to/create-a-database-for-redis/) or [message queues](/queues/quickstart/).
 
 **Manage your infrastructure as code**
 
 While you can manage your services through the console, we highly recommend using developer tools for a repeatable and version-controlled setup.
 
 **CLI**
 
-Use the command-line interface provided by your cloud provider for scripting and automation. Read more(/scaleway-cli/quickstart/)
+Use the [Scaleway command-line interface](/scaleway-cli/quickstart/) for easy resources management, scripting, and automation.
 
 **Terraform/IaC**
 
-Define your Serverless Containers services using tools like Terraform for a fully automated and declarative infrastructure. Read more (/terraform/quickstart/)
+Define your Serverless Containers services using tools like Terraform or OpenTofu via the [Scaleway Provider](/terraform/quickstart/) for a fully automated and declarative infrastructure.
 
-## Migration Strategies
+### Migration Strategies
 
 **Progressive migration**
 
 You do not need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel of the platform. This approach minimizes risk and allows your teams to learn as they go.
 
 **API Migration**
 
-When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new /v2/ endpoint for your API that is served by Serverless Containers, while the existing /v1/ remains on your current infrastructure. This allows for a gradual rollout to your users.
+When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new `/v2/` endpoint for your API that is served by Serverless Containers, while the existing `/v1/` remains on your current infrastructure. This allows for a gradual rollout to your users.
 
-## Start small with Serverless Jobs
+### Start small with Serverless Jobs
 
 If you're looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion.