fix: correct drop/silence/inhibit rule comparison and audit log query limits

1. Drop rules vs silence/inhibit rules: clarify that silence and inhibit
   rules still create alerts but prevent them from grouping into or
   triggering incidents, while drop rules discard events immediately
   with no alerts created at all.

2. Audit log query range: clarify the 30-day frontend query window limit
   vs per-plan data availability (Free 30d, Standard 180d, Pro 366d).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: ysyneu

en/on-call/channel/create-edit.mdx

@@ -96,10 +96,10 @@ Configure rules in **Configuration** → **Integrate Data** → **Drop Rules** t
 
 <Steps>
   <Step title="Create a Drop Rule">
-    Go to **Configuration** → **Integrate Data** → **Drop Rules**, click **Add Drop Rule**.
+    Click **Add Drop Rule**.
   </Step>
   <Step title="Fill in Rule Information">
-    Enter a **Rule Name** (required) and **Description** (optional) for identification and management.
+    Enter a **Rule Name** (required) and **Description** (optional).
   </Step>
   <Step title="Set Filter Conditions">
     Configure filter conditions — supports matching by **Integration Source** and **Severity**.
@@ -114,7 +114,9 @@ Multiple drop rules are executed sequentially in list order. If any rule matches
 </Note>
 
 <Warning>
-Dropped events will not appear anywhere. If you're not receiving alerts, check the drop rules first. Drop rules differ from [silence rules](/en/on-call/channel/noise-reduction) — silence rules only suppress notifications while the incident still exists; drop rules discard events entirely, producing no alert or incident records.
+Dropped events will not appear anywhere. If you are not receiving alerts, check drop rules first.
+
+Drop rules differ from [silence rules](/en/on-call/channel/noise-reduction) and [inhibit rules](/en/on-call/channel/noise-reduction): silence and inhibit rules still match and process at the alert event level (alerts are created), but matched alerts will not group into or trigger any incident; drop rules discard events immediately upon ingestion, producing no alert or incident records at all.
 </Warning>
 
 ### Configure Escalation Rules

en/platform/audit-log.mdx

@@ -32,7 +32,7 @@ Audit logs provide multiple filtering criteria to help you quickly locate target
 
 | Filter | Description |
 | --- | --- |
-| **Time Range** | Select the query time interval; defaults to showing the last 7 days of logs. The maximum searchable range depends on your subscription plan (see table below) |
+| **Time Range** | Select the query time interval; defaults to showing the last 7 days of logs. Each query can span up to 30 days; you can slide the window within your plan's data availability range |
 | **User** | Filter by operator, supports searching by member name or email |
 | **Event** | Filter by event type, supports multi-select and keyword search |
 | **Event ID** | Enter an event ID to precisely match a specific operation record |
@@ -41,22 +41,26 @@ Audit logs provide multiple filtering criteria to help you quickly locate target
 You can combine multiple filters. For example, you can specify both a time range and an operator to quickly find all operations by a specific member during a particular period.
 </Tip>
 
-**Maximum searchable range by plan:**
+**Data availability by plan:**
 
-| Subscription Plan | Maximum Searchable Range |
+| Subscription Plan | Data Availability |
 | --- | --- |
 | Free | 30 days |
 | Standard | 180 days |
 | Professional | 366 days |
 
+<Note>
+Each query window is limited to 30 days. To view older data, adjust the start and end dates of your time range.
+</Note>
+
 ## Pagination
 
 ---
 
 Audit logs display 10 records per page. Use the pagination buttons at the bottom of the page to browse more records. The current page number and total pages are shown at the bottom.
 
 <Note>
-Both the audit log retention period and searchable range depend on your subscription plan — higher tiers retain logs longer. Contact support to upgrade if you need a longer retention period.
+The audit log retention period depends on your subscription plan -- higher tiers retain logs longer. Contact support to upgrade if you need a longer retention period.
 </Note>
 
 ## FAQ

zh/on-call/channel/create-edit.mdx

@@ -97,10 +97,10 @@ keywords: ["协作空间", "创建管理", "业务隔离", "团队协作", "告
 
 <Steps>
   <Step title="创建排除规则">
-    进入 **配置** → **集成数据** → **排除规则**，点击 **添加排除规则**。
+    点击 **添加排除规则**。
   </Step>
   <Step title="填写规则信息">
-    输入 **规则名称**（必填）和 **描述**（可选），便于后续识别和管理。
+    输入 **规则名称**（必填）和 **描述**（可选）。
   </Step>
   <Step title="设置过滤条件">
     配置过滤条件，支持按 **集成来源** 和 **严重程度** 进行匹配。
@@ -115,7 +115,9 @@ keywords: ["协作空间", "创建管理", "业务隔离", "团队协作", "告
 </Note>
 
 <Warning>
-排除后的事件不会在任何地方显示。如遇收不到告警的情况，请先检查排除规则。排除规则与[静默策略](/zh/on-call/channel/noise-reduction)不同——静默策略只是抑制通知，故障仍然存在；排除规则会直接丢弃事件，不产生任何告警或故障记录。
+排除后的事件不会在任何地方显示。如遇收不到告警的情况，请先检查排除规则。
+
+排除规则与[静默策略](/zh/on-call/channel/noise-reduction)、[抑制策略](/zh/on-call/channel/noise-reduction)不同：静默策略和抑制策略仍然在告警事件层面进行匹配和处理（告警会被创建），但匹配的告警不会聚合到故障中，也不会触发新故障；排除规则会在事件进入时直接丢弃，不产生任何告警或故障记录。
 </Warning>
 
 ### 配置分派策略

zh/platform/audit-log.mdx

@@ -32,7 +32,7 @@ keywords: ["审计日志", "操作审计", "安全合规", "操作记录"]
 
 | 筛选条件 | 说明 |
 | --- | --- |
-| **时间范围** | 选择查询的时间区间，默认展示最近 7 天的日志。可检索的最大时间范围取决于订阅版本（见下表） |
+| **时间范围** | 选择查询的时间区间，默认展示最近 7 天的日志。单次查询最大跨度为 30 天，可在数据可查范围内滑动选择。数据可查范围取决于订阅版本 |
 | **用户** | 按操作人筛选，支持搜索成员名称或邮箱 |
 | **事件** | 按事件类型筛选，支持多选和关键词搜索 |
 | **事件 ID** | 输入事件 ID 精确匹配特定操作记录 |
@@ -41,22 +41,26 @@ keywords: ["审计日志", "操作审计", "安全合规", "操作记录"]
 多个筛选条件可以组合使用。例如，你可以同时指定时间范围和操作人，快速查找某位成员在特定时段内的所有操作。
 </Tip>
 
-**各版本可检索时间范围：**
+**各版本数据可查范围：**
 
-| 订阅版本 | 最大可检索范围 |
+| 订阅版本 | 数据可查范围 |
 | --- | --- |
 | 免费版 | 30 天 |
 | 标准版 | 180 天 |
 | 专业版 | 366 天 |
 
+<Note>
+单次查询的时间窗口最大为 30 天。如需查看更早的数据，请调整时间范围的起止日期。
+</Note>
+
 ## 日志翻页
 
 ---
 
 审计日志每页展示 10 条记录，通过页面底部的翻页按钮浏览更多记录。页面底部会显示当前页码和总页数。
 
 <Note>
-审计日志的保留时长和可检索范围均取决于你的订阅版本，版本越高保留越久。如需更长的日志保留期限，请联系客服升级。
+审计日志的保留时长取决于你的订阅版本，版本越高保留越久。如需更长的日志保留期限，请联系客服升级。
 </Note>
 
 ## 常见问题