docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/concepts.mdx

@@ -167,6 +167,8 @@ A NATS trigger is a mechanism that connects a container to a [NATS](/nats/concep
 For each message that is sent to a NATS subject, the NATS trigger reads the message and invokes the associated container with the message as the input parameter.
 The container can then process the message and perform any required actions, such as updating a database or sending a notification.
 
+Refer to the [dedicated documenation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to add triggers to a Serverless Container.
+
 ## Port
 
 The port of a containerized application refers to the network port that the application inside the container listens on for incoming requests.
@@ -200,6 +202,8 @@ A queue trigger is a mechanism that connects a container to a queue created with
 For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
 The container can then process the message, and perform any required actions, such as updating a database or sending a notification.
 
+Refer to the [dedicated documenation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to add triggers to a Serverless Container.
+
 ## Registry endpoint
 
 The registry endpoint parameter is the resource linked to the container image used in your Serverless Container.