fix links

Author: Iwaniukooo11

docs/specification.md

@@ -323,7 +323,7 @@ Creates a push notification configuration for a task to receive asynchronous upd
 
 **Outputs:**
 
-- [`TaskPushNotificationConfig`](#431-taskpushnotificationconfig): Created configuration with assigned ID
+- [`TaskPushNotificationConfig`](#TaskPushNotificationConfig): Created configuration with assigned ID
 
 **Errors:**
 
@@ -348,7 +348,7 @@ Retrieves an existing push notification configuration for a task.
 
 **Outputs:**
 
-- [`TaskPushNotificationConfig`](#431-taskpushnotificationconfig): The requested configuration
+- [`TaskPushNotificationConfig`](#TaskPushNotificationConfig): The requested configuration
 
 **Errors:**
 
@@ -2622,7 +2622,7 @@ Creates a push notification configuration for a task.
 
 {{ proto_to_table("TaskPushNotificationConfig") }}
 
-**Response:** See [`TaskPushNotificationConfig`](#431-taskpushnotificationconfig) object definition.
+**Response:** See [`TaskPushNotificationConfig`](#TaskPushNotificationConfig) object definition.
 
 #### 10.4.8. GetTaskPushNotificationConfig
 
@@ -2632,7 +2632,7 @@ Retrieves an existing push notification configuration for a task.
 
 {{ proto_to_table("GetTaskPushNotificationConfigRequest") }}
 
-**Response:** See [`TaskPushNotificationConfig`](#431-taskpushnotificationconfig) object definition.
+**Response:** See [`TaskPushNotificationConfig`](#TaskPushNotificationConfig) object definition.
 
 #### 10.4.9. ListTaskPushNotificationConfigs
 
@@ -3127,7 +3127,7 @@ When implementing push notifications, both agents (as webhook callers) and clien
 **Configuration Security:**
 
 - Webhook URLs **SHOULD** use HTTPS to protect payload confidentiality in transit
-- Authentication tokens in [`TaskPushNotificationConfig`](#431-taskpushnotificationconfig) **SHOULD** be treated as secrets and rotated periodically
+- Authentication tokens in [`TaskPushNotificationConfig`](#TaskPushNotificationConfig) **SHOULD** be treated as secrets and rotated periodically
 - Agents **SHOULD** securely store push notification configurations and credentials
 - Clients **SHOULD** use unique, single-purpose tokens for each push notification configuration
 

docs/topics/streaming-and-async.md

@@ -47,7 +47,7 @@ For very long-running tasks (for example, lasting minutes, hours, or even days)
 The following key features detail how push notifications are implemented and managed within the A2A protocol:
 
 - **Server Capability:** The A2A Server must indicate its support for this feature by setting `capabilities.pushNotifications: true` in its Agent Card.
-- **Configuration:** The client provides a [`TaskPushNotificationConfig`](../specification.md#431-taskpushnotificationconfig) to the server. This configuration is supplied:
+- **Configuration:** The client provides a [`TaskPushNotificationConfig`](../specification.md#TaskPushNotificationConfig) to the server. This configuration is supplied:
     - Within the initial `SendMessage` or `SendStreamingMessage` request, or
     - Separately, using the `CreateTaskPushNotificationConfig` RPC method for an existing task.
     The `TaskPushNotificationConfig` includes a `url` (the HTTPS webhook URL), an optional `token` (for client-side validation), and optional `authentication` details (for the A2A Server to authenticate to the webhook).