chore(gen): update concepts with links MTA-6444

Author: SamyOubouaziz

pages/serverless-containers/concepts.mdx

@@ -44,7 +44,7 @@ The startup process steps are:
 * Starting the container. Optimize your container startup speed to minimize this step (e.g., avoid waiting for slow connections or downloading large objects at startup)
 * Waiting for the container to listen on the configured port.
 
-[How to reduce cold starts](/serverless-containers/faq/#how-can-i-reduce-the-cold-starts-of-serverless-containers)
+[How to reduce cold starts](/serverless-containers/faq/#how-can-i-reduce-the-cold-starts-of-serverless-containers).
 
 ## Commands and arguments
 
@@ -81,16 +81,18 @@ A container is a package of software that includes all dependencies: code, runti
 
 ## Container image
 
-A container image is a file that includes all the requirements and instructions of a complete and executable version of an application.
+A container image is a file that includes all the requirements and instructions of a complete and executable version of an application. Container images can be easily stored using [Scaleway Container Registry](/container-registry/quickstart/).
 
 ## Container Registry
 
-Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration and performances. See the [migration guide](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
+Container Registry is the place where your images are stored before being deployed. We recommend using [Scaleway Container Registry](/container-registry/quickstart/) for optimal integration and performances. See the [migration guide](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
 
 ## Deployment
 
 Some parameter changes require a new deployment of the container to take effect. The deployment happens without causing downtime, as traffic is switched to the newest version once it is ready.
 
+Refer to the [dedicated documentation](/serverless-containers/reference-content/deploy-container/) for information on the different deployment methods.
+
 ## Endpoint
 
 An endpoint is the URL generated to access your resource. It can be customized with [custom domains](#custom-domain).
@@ -145,9 +147,9 @@ Performance metrics for your Serverless resources are natively available. Refer
 
 ## Namespace
 
-A namespace is a folder with some settings that allows you to [group your containers](/serverless-containers/how-to/create-manage-delete-containers-namespace/).
+A namespace is a folder with some settings that allows you to group your containers. Containers in the same namespace can share environment variables, secrets, and access tokens, defined at the namespace level.
 
-Containers in the same namespace can share environment variables, secrets, and access tokens, defined at the namespace level.
+Refer to the [dedicated documentation](/serverless-containers/how-to/create-manage-delete-containers-namespace/) for information on how to create, manage, and delete namespaces.
 
 ## Port
 
@@ -181,7 +183,7 @@ While DHCP is built into all new Private Networks, it may not be automatically a
 
 ## Registry endpoint
 
-The registry endpoint parameter is the resource linked to the container image used in your Serverless Container.
+The registry endpoint parameter is the resource linked to the container image used in your Serverless Container. Endpoints for the [Scaleway Container Registry](/container-registry/) namespaces can be found in the Scaleway Console.
 
 ## Request timeout