diff --git a/serverless/containers/reference-content/containers-limitations.mdx b/serverless/containers/reference-content/containers-limitations.mdx
index 7fc8c9a15d..257cb9e872 100644
--- a/serverless/containers/reference-content/containers-limitations.mdx
+++ b/serverless/containers/reference-content/containers-limitations.mdx
@@ -78,9 +78,11 @@ When container CPU and/or memory are not provided by the client, these default v
 
 ## Architecture
 
-Scaleway Containers only supports `amd64` [architecture](https://github.com/docker-library/official-images#architectures-other-than-amd64/) for
+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, 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 to build your image to target `amd64` architecture.
+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 an Instance with `amd64` architecture to run your builds.
diff --git a/serverless/containers/troubleshooting/common-errors.mdx b/serverless/containers/troubleshooting/common-errors.mdx
index aad17c9057..c004b7dc70 100644
--- a/serverless/containers/troubleshooting/common-errors.mdx
+++ b/serverless/containers/troubleshooting/common-errors.mdx
@@ -23,7 +23,7 @@ categories:
 
 - Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU.
 
-- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported.
+- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation.
 
 - Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/).
 
@@ -45,4 +45,4 @@ This issue can happen for the following reasons:
 
 ### Possible solutions
 
-Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces).
\ No newline at end of file
+Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces).
diff --git a/serverless/jobs/reference-content/jobs-limitations.mdx b/serverless/jobs/reference-content/jobs-limitations.mdx
index ab4b2d343e..a047c20403 100644
--- a/serverless/jobs/reference-content/jobs-limitations.mdx
+++ b/serverless/jobs/reference-content/jobs-limitations.mdx
@@ -38,11 +38,14 @@ When the job vCPU and/or memory are not provided by the client, these default va
 
 ## Architecture
 
-Scaleway Serverless Jobs only supports `amd64` architecture for images.
+Scaleway Serverless Jobs 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, 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.
+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 an Instance with `amd64` architecture to run your builds.
 
 ## Ports restrictions
 
diff --git a/serverless/jobs/troubleshooting/common-errors.mdx b/serverless/jobs/troubleshooting/common-errors.mdx
index 49425738d1..5db08971e1 100644
--- a/serverless/jobs/troubleshooting/common-errors.mdx
+++ b/serverless/jobs/troubleshooting/common-errors.mdx
@@ -17,6 +17,6 @@ categories:
 
 ### Possible solutions
 
-- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported.
+- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation.
 
-- Make sure your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/).
\ No newline at end of file
+- Make sure your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/).