diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx
index 2527484692..e0a4d23db1 100644
--- a/pages/serverless-containers/reference-content/containers-limitations.mdx
+++ b/pages/serverless-containers/reference-content/containers-limitations.mdx
@@ -95,10 +95,10 @@ When container CPU and/or memory are not provided by the client, these default v
 Scaleway Containers only supports `amd64` [architecture](https://github.com/docker-library/official-images?tab=readme-ov-file#architectures-other-than-amd64) for
 images.
 
-For example, if you build an image using an ARM CPU, such as Apple Silicon M series, your image will be in the `arm64` architecture, and you will have an error message during deployment.
+For example, if you build an image using an ARM CPU, such as Apple silicon M series, your image will be in the `arm64` architecture, and you will have an error message during deployment.
 
 You must ensure that you build your image to target `amd64` architecture, to acheive this there are multiple solutions:
-* You can use the following Docker command: `docker buildx build --platform linux/amd64 .`, or
+* You can use the following Docker command: `docker build --platform linux/amd64 .`, or
 * You can use an Instance with `amd64` architecture to run your builds.
 
 ## Versioning and rollback
diff --git a/pages/serverless-jobs/reference-content/jobs-limitations.mdx b/pages/serverless-jobs/reference-content/jobs-limitations.mdx
index ccd93caf4b..f92a08606f 100644
--- a/pages/serverless-jobs/reference-content/jobs-limitations.mdx
+++ b/pages/serverless-jobs/reference-content/jobs-limitations.mdx
@@ -44,7 +44,7 @@ images.
 For example, if you build an image using an ARM CPU, such as Apple Silicon M series, your image will be in the `arm64` architecture, and you will have an error message during deployment.
 
 You must ensure that you build your image to target `amd64` architecture, to achieve this there are multiple solutions:
-* You can use the following docker command: `docker buildx build --platform linux/amd64 .`, or
+* You can use the following docker command: `docker build --platform linux/amd64 .`, or
 * You can use an Instance with `amd64` architecture to run your builds.
 
 ## Ports restrictions
diff --git a/tutorials/snapshot-instances-jobs/index.mdx b/tutorials/snapshot-instances-jobs/index.mdx
index 5ba45ef1f7..2dcb067c9a 100644
--- a/tutorials/snapshot-instances-jobs/index.mdx
+++ b/tutorials/snapshot-instances-jobs/index.mdx
@@ -181,7 +181,7 @@ Serverless Jobs rely on containers to run in the cloud, and therefore require a
     docker build -t rg.fr-par.scw.cloud/your-namespace-name/jobs-snapshot:v1 .
 
     ## TIP: for Apple Silicon or other ARM processors, please use the following command as Serverless Jobs supports amd64 architecture
-    # docker buildx build --platform linux/amd64 -t rg.fr-par.scw.cloud/jobs-snapshot/jobs-snapshot:v1 .
+    # docker build --platform linux/amd64 -t rg.fr-par.scw.cloud/jobs-snapshot/jobs-snapshot:v1 .
     ```
 
 4. Run the following command to push the container image to the registry:
@@ -235,4 +235,4 @@ This tutorial is a lightweight example of how to create recurring snapshots of a
 - [Serverless Jobs Documentation](/serverless-jobs/how-to/create-job/)
 - [Other methods to deploy Jobs](/serverless-jobs/reference-content/deploy-job/)
 - [API keys documentation](/iam/how-to/create-api-keys/)
-- [CRON schedule reference](/serverless-jobs/reference-content/cron-schedules/)
\ No newline at end of file
+- [CRON schedule reference](/serverless-jobs/reference-content/cron-schedules/)