Addresses the Ricardo's comment about a missing anchor for 'secret'

Signed-off-by: Charles d'Avernas <charles.davernas@neuroglia.io>

Author: cdavernas

dsl-reference.md

@@ -38,6 +38,7 @@
     - [OAUTH2](#oauth2-authentication)
   + [Extension](#extension)
   + [Error](#error)
+    - [Standard Error Types](#standard-error-types)
   + [Event Consumption Strategy](#event-consumption-strategy)
   + [Retry](#retry)
   + [Input](#input)

dsl.md

@@ -92,7 +92,7 @@ Serverless Workflow DSL allows for defining reusable components that can be refe
 - [Extensions](dsl-reference.md#extension)
 - [Functions](dsl-reference.md#task)
 - [Retries](dsl-reference.md#retry)
-- [Secrets](#)
+- [Secrets](#secret)
 
 ##### Task
 
@@ -114,6 +114,12 @@ The Serverless Workflow DSL defines several default [task](dsl-reference.md#task
 
 To ensure they conform to the DSL, runtimes **should** pass all the feature conformance test scenarii defined in the [ctk](ctk/README.md).
 
+##### Secret
+
+Secrets are sensitive information required by a workflow to securely access protected resources or services. They provide a way to securely store and manage credentials, tokens, or other sensitive data used during workflow execution.
+
+Runtime **must** implement a mechanism capable of providing the workflow with the data contained within the defined secrets. If a workflow attempts to access a secret to which it does not have access rights or which does not exist, runtimes **must** raise an error with type `https://serverlessworkflow.io/spec/1.0.0/errors/authorization` and status `403`.
+
 #### Scheduling
 
 Workflow scheduling in ServerlessWorkflow allows developers to specify when and how their workflows should be executed, ensuring timely response to events and efficient resource utilization. It offers four key properties: `every`, `cron`, `after`, and `on`.