docs: scope the tencent-css missing-field note to push/interruption callbacks

(cherry picked from commit 39c4a10)

Author: ysyneu

en/on-call/integration/alert-integration/alert-sources/tencent-css.mdx

@@ -78,7 +78,7 @@ Flashduty computes the Alert Key from the account APPID `appid`, the push domain
 
 Changes to the error code, error message, push node, pusher IP, push duration, or `sequence` do not change the Alert Key. `sequence` identifies one push session and changes when the stream is pushed again, so it is not part of the Alert Key.
 
-If a callback lacks `event_type`, `appid`, `app`, `appname`, or `stream_id`, Flashduty rejects the request with an error, and CSS retries it according to its callback retry rules.
+If a stream push or stream interruption callback lacks `appid`, `app`, `appname`, or `stream_id`, or a callback has no `event_type`, Flashduty rejects the request with an error, and CSS retries it according to its callback retry rules.
 
 ## Alert lifecycle
 ---

zh/on-call/integration/alert-integration/alert-sources/tencent-css.mdx

@@ -78,7 +78,7 @@ Flashduty 用账号 APPID `appid`、推流域名 `app`、推流路径 `appname`
 
 错误码、错误描述、推流节点、推流端 IP、推流时长和 `sequence` 的变化都不会改变 Alert Key。`sequence` 标识一次推流活动，重新推流时会变化，因此不用于计算 Alert Key。
 
-回调缺少 `event_type`、`appid`、`app`、`appname` 或 `stream_id` 时，Flashduty 会拒绝该请求并返回错误，云直播会按回调重试规则重试。
+推流回调或断流回调缺少 `appid`、`app`、`appname` 或 `stream_id`，或回调没有 `event_type` 时，Flashduty 会拒绝该请求并返回错误，云直播会按回调重试规则重试。
 
 ## 告警生命周期
 ---