feat: update README files to improve clarity on R2 vs KV storage options

README.md

@@ -67,12 +67,14 @@ English：[`README_EN.md`](./README_EN.md)
 3. 部署完成后，同一页面打开workers设置，将**Git存储库**断开连接
 4. 同一位置，**Git存储库**链接至第一步Fork的仓库
 
-> [!NOTE] R2 vs KV
+> [!NOTE] 
+> R2 vs KV
 >- R2：需绑定银行卡；**单个附件/Send上限 100MB**（代码限制，可自行修改）；**总量 10GB 免费**
 >- KV：无需绑卡；**单个附件/Send 文件上限 25 MiB**（cloudflare限制，不可修改）；**总量 1GB 免费**
 
 
-> [!TIP] 同步上游（更新仓库）：
+> [!TIP] 
+> 同步上游（更新仓库）：
 >- 手动：Github打开你Fork的私人仓库，看到顶部同步提示时，点击 “Sync fork”。
 >- 自动：进入你的 Fork 仓库 → Actions，点击 “I understand my workflows, go ahead and enable them”，每天凌晨三点自动同步至上游
 

README_EN.md

@@ -67,11 +67,13 @@
 3. After deployment, open the Workers settings on the same page and disconnect the **Git repository**.
 4. From the same location, reconnect the **Git repository** to the fork you created in step 1.
 
-> [!NOTE] R2 vs KV
+> [!NOTE] 
+> R2 vs KV
 >- R2: typically requires a payment method; **single attachment/Send file limit is 100 MB** (**project-level limit, editable in code**); **10 GB free storage included**.
 >- KV: no card required; **single attachment/Send file limit is 25 MiB** (**Cloudflare platform limit, not editable**); **1 GB free storage included**.
 
-> [!TIP] Sync upstream (keep your fork updated):
+> [!TIP] 
+> Sync upstream (keep your fork updated):
 >- Manual: open your fork on GitHub and click **Sync fork** when prompted.
 >- Automatic: in your fork, go to **Actions**, click "I understand my workflows, go ahead and enable them". It will auto-sync from upstream daily at 3 AM.