fix: correct inaccurate claims in statuspage comparison doc (#59)

Author: debidong

en/on-call/statuspage/comparison.mdx

@@ -102,18 +102,18 @@ Before evaluating specific products, there's a more fundamental question to answ
   <Tab title="Notification Channels">
     | Method | Flashduty | Atlassian Statuspage |
     | --- | --- | --- |
-    | **Email** | ✅ Supported | ✅ Supported |
-    | **SMS** | Covered via IM channels | ✅ Supported, but with limited triggers -- intermediate updates do not send SMS |
-    | **Webhook** | ✅ Supported | ✅ Supported |
-    | **Feishu/Lark** | ✅ Supported | ❌ Not supported |
-    | **Dingtalk** | ✅ Supported | ❌ Not supported |
-    | **WeCom** | ✅ Supported | ❌ Not supported |
-    | **Slack** | ✅ Supported | ✅ Supported |
+    | **Email** | ✅ Supported (public status pages only) | ✅ Supported |
+    | **SMS** | ❌ Not supported | ✅ Supported, but with limited triggers -- intermediate updates do not send SMS |
+    | **Webhook** | ❌ Not supported | ✅ Supported |
+    | **Feishu/Lark** | ✅ Supported (internal status pages only) | ❌ Not supported |
+    | **Dingtalk** | ✅ Supported (internal status pages only) | ❌ Not supported |
+    | **WeCom** | ✅ Supported (internal status pages only) | ❌ Not supported |
+    | **Slack** | ✅ Supported (internal status pages only) | ✅ Supported |
     | **RSS/Atom** | ✅ Supported, compatible with Atlassian history.rss / history.atom link format | ✅ Supported |
     | **Multi-language Notifications** | ✅ Natively preserves language preferences | Relies on third-party integration (Localize) |
 
     <Tip>
-    Flashduty offers notification channels better suited for enterprise collaboration, with native support for Feishu/Lark, Dingtalk, WeCom, and Slack.
+    Flashduty offers notification channels better suited for enterprise collaboration. Internal status pages natively support Feishu/Lark, Dingtalk, WeCom, and Slack notifications, while public status pages support email notifications.
     </Tip>
   </Tab>
 </Tabs>
@@ -130,10 +130,9 @@ Atlassian Statuspage is billed as a standalone product, with pricing increasing
 | --- | --- | --- |
 | **Pricing Page** | [flashcat.cloud/flashduty/price](https://flashcat.cloud/flashduty/price/) | [atlassian.com/statuspage/pricing](https://www.atlassian.com/software/statuspage/pricing) |
 | **Billing Model** | **Included in the On-call module**, not sold separately | Standalone product, tiered across multiple dimensions |
-| **Traffic Limits** | ✅ **Unlimited** | Limited by plan |
-| **Public Page** | ✅ Included | Tiered by subscribers, components, team members, and metrics |
-| **Private Page** | ✅ Included | Tiered by authenticated subscribers |
-| **Audience-specific** | ✅ Included | **Separate product line, starting at $300/month** |
+| **Traffic Limits** | ✅ **Free** | Limited by plan |
+| **Public Page** | ✅ Free | Tiered by subscribers, components, team members, and metrics |
+| **Private Page** | ✅ Professional edition | Tiered by authenticated subscribers |
 | **Component Subscription** | ✅ All editions | Business and above only |
 | **Component Grouping** | ✅ All editions | Business and above only |
 
@@ -144,7 +143,7 @@ For a typical scenario requiring a public status page + internal status page, 1,
 | Cost Item | Flashduty | Atlassian Statuspage |
 | --- | --- | --- |
 | **Public Status Page** | Included in On-call | Startup plan from $99/month; 1,000 subscribers requires Business plan |
-| **Internal Status Page** | Included in On-call | Audience-specific is a separate product, starting at $300/month |
+| **Internal Status Page** | Included in On-call Professional | Audience-specific is a separate product, starting at $300/month |
 | **Annual Status Page Cost** | **$0 (additional)** | **~$4,800–$8,400+/year** (Public Business + Audience-specific) |
 
 <Note>

zh/on-call/statuspage/comparison.mdx

@@ -103,18 +103,18 @@ Flashduty 状态页和 Atlassian Statuspage 是市场上两款主流的状态页
   <Tab title="通知渠道">
     | 通知方式 | Flashduty | Atlassian Statuspage |
     | --- | --- | --- |
-    | **邮件** | ✅ 支持 | ✅ 支持 |
-    | **SMS** | 通过 IM 渠道覆盖 | ✅ 支持，但触发条件有限——中间 update 不发送 SMS |
-    | **Webhook** | ✅ 支持 | ✅ 支持 |
-    | **飞书** | ✅ 支持 | ❌ 不支持 |
-    | **钉钉** | ✅ 支持 | ❌ 不支持 |
-    | **企业微信** | ✅ 支持 | ❌ 不支持 |
-    | **Slack** | ✅ 支持 | ✅ 支持 |
+    | **邮件** | ✅ 支持（仅公开状态页） | ✅ 支持 |
+    | **SMS** | ❌ 不支持 | ✅ 支持，但触发条件有限——中间 update 不发送 SMS |
+    | **Webhook** | ❌ 不支持 | ✅ 支持 |
+    | **飞书** | ✅ 支持（仅内部状态页） | ❌ 不支持 |
+    | **钉钉** | ✅ 支持（仅内部状态页） | ❌ 不支持 |
+    | **企业微信** | ✅ 支持（仅内部状态页） | ❌ 不支持 |
+    | **Slack** | ✅ 支持（仅内部状态页） | ✅ 支持 |
     | **RSS/Atom** | ✅ 支持，兼容 Atlassian history.rss / history.atom 链接格式 | ✅ 支持 |
     | **多语言通知** | ✅ 原生保留语言偏好 | 依赖第三方集成（Localize） |
 
     <Tip>
-    Flashduty 在通知渠道上更贴合国内企业协同需求，原生支持飞书、钉钉、企业微信和 Slack。
+    Flashduty 在通知渠道上更贴合国内企业协同需求，内部状态页原生支持飞书、钉钉、企业微信和 Slack 通知，公开状态页支持邮件通知。
     </Tip>
   </Tab>
 </Tabs>
@@ -131,10 +131,9 @@ Atlassian Statuspage 作为独立产品收费，价格随订阅者、组件、
 | --- | --- | --- |
 | **价格页面** | [flashcat.cloud/flashduty/price](https://flashcat.cloud/flashduty/price/) | [atlassian.com/statuspage/pricing](https://www.atlassian.com/software/statuspage/pricing) |
 | **收费模式** | **包含在 On-call 模块中**，不单独售卖 | 独立产品，按多维度分档收费 |
-| **访问流量** | ✅ **无上限** | 按套餐限制 |
-| **Public 页面** | ✅ 包含 | 按订阅者、组件、团队成员、指标数量分档 |
-| **Private 页面** | ✅ 包含 | 按 authenticated subscribers 分档 |
-| **Audience-specific** | ✅ 包含 | **独立产品线，起步 $300/月** |
+| **访问流量** | ✅ **免费** | 按套餐限制 |
+| **Public 页面** | ✅ 免费 | 按订阅者、组件、团队成员、指标数量分档 |
+| **Private 页面** | ✅ 专业版 | 按 authenticated subscribers 分档 |
 | **组件级订阅** | ✅ 所有版本 | 仅 Business 及以上 |
 | **组件分组** | ✅ 所有版本 | 仅 Business 及以上 |
 
@@ -145,7 +144,7 @@ Atlassian Statuspage 作为独立产品收费，价格随订阅者、组件、
 | 费用项 | Flashduty | Atlassian Statuspage |
 | --- | --- | --- |
 | **公开状态页** | 包含在 On-call 中 | Startup 套餐 $99/月起，1,000 名订阅者需 Business 套餐 |
-| **内部状态页** | 包含在 On-call 中 | Audience-specific 独立产品，起步 $300/月 |
+| **内部状态页** | 包含在 On-call 专业版中 | Audience-specific 独立产品，起步 $300/月 |
 | **状态页年度总成本** | **¥0（额外）** | **约 $4,800–$8,400+/年**（Public Business + Audience-specific） |
 
 <Note>