fixes

Author: thomas-tacquet

pages/serverless-jobs/concepts.mdx

@@ -10,7 +10,7 @@ import ServerlessConcepts from '@macros/serverless/serverless-concepts.mdx'
 
 ## Commands and arguments
 
-Field `command` is deprecated prior `startup_command` in `v1alpha2`.
+Field `command` is deprecated in favor of `startup_command` in `v1alpha2`.
 
 For more details see [startup command and arguments](/serverless-jobs/concepts/#startup-commands-and-arguments) and [v1alpha2 migration guide](/serverless-jobs/reference-content/v1alpha1-to-v1alpha2/).
 
@@ -102,6 +102,7 @@ Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/task
 ## Status
 
 A Serverless Job run can have the following statuses:
+* **Running**: your Serverless Job run is currently executing.
 * **Succeeded**: your Serverless Job run finished in a successful state.
 * **Queued**: your Serverless Job run is waiting for resources to run.
 * **Error**: your Serverless Job run finished with an error or timeout. [Check our troubleshooting documentation](/serverless-jobs/troubleshooting/job-in-error-state/) to solve the issue.
@@ -117,7 +118,7 @@ To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway
 
 ## Terraform/OpenTofu
 
-Terraform/OpenTofu is an infrastructure-as-code tool, owned by Hashicorp. Serverless Jobs integrate easily with your infrastructure as code, via our [Terraform/OpenTofu provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/job_definition).
+Terraform is an infrastructure-as-code tool developed by HashiCorp, while OpenTofu is an open-source fork of Terraform. Serverless Jobs integrate easily with your infrastructure as code, via our [Terraform/OpenTofu provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/job_definition).
 
 Examples using Terraform/OpenTofu can be found in our [Serverless Examples repository](https://github.com/scaleway/serverless-examples), such as our [example using Terraform/OpenTofu with Serverless Jobs](https://github.com/scaleway/serverless-examples/blob/main/jobs/terraform-hello-world).
 

pages/serverless-jobs/how-to/migrate-command-to-startup-command.mdx

@@ -1,6 +1,6 @@
 ---
-title: How to migrate from startup command to command and arguments
-description: Learn how to migrate from the legacy startup command system to the modern commands and arguments for Scaleway Serverless Jobs.
+title: How to migrate from command to startup command and arguments
+description: Learn how to migrate from the legacy command system to the modern startup command and arguments for Scaleway Serverless Jobs.
 tags: containers
 dates:
   validation: 2025-12-23
@@ -9,23 +9,23 @@ dates:
 
 import Requirements from '@macros/iam/requirements.mdx'
 
-The Serverless Jobs `v1alpha2` API introduces a new startup execution mechanism based on [commands and arguments](/serverless-containers/concepts/#startup-command-and-arguments), replacing the legacy `command`.
+The Serverless Jobs `v1alpha2` API introduces a new startup execution mechanism based on [commands and arguments](/serverless-jobs/concepts/#startup-commands-and-arguments), replacing the legacy `command`.
 
 The Scaleway console allows you to quickly and easily migrate your existing jobs to the new system.
 
 Migration from `command` field to `startup_command` field is mostly transparent for customers using Scaleway Console but can require some attention of API, CLI and other devtools users.
 
 The change allows for:
-- More customisation for executing complex command, by separating `startup_command` and `args`.
-- To match our underlying [Kubernetes implementation](https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/).
-- It allows to compute environment variables used in command and argument strings.
+- More customization for executing complex commands, by separating `startup_command` and `args`.
+- Better alignment with our underlying [Kubernetes implementation](https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/).
+- The ability to compute environment variables used in command and argument strings.
 - `startup_command` is now an array of commands instead of a single string.
 
 <Requirements />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- An existing job that uses a startup command
+- An existing job that uses the legacy command field
 
 ## How to migrate from command to startup commands and arguments