chore: refine translations

Author: xiaost

content/en/docs/hertz/tutorials/basic-feature/http-adaptor.md

@@ -8,15 +8,15 @@ description: ""
 
 ## Background
 
-- We will deprecate the Hertz's native file system
-- Provide an fs implementation that is both compatible and performs well, using the official net/http ecosystem.
-- Reduce the implementation of a large number of extensions by expanding the hertz function through the official net/http ecosystem
+- Phasing out the poorly maintained hertz app.FS implementation
+- Providing a compatible and performant fs implementation through the official net/http ecosystem
+- Extending hertz functionality through the official net/http ecosystem to reduce custom implementations
 
 ## What is adaptor.HertzHandler
 
-- You are allowed to directly convert your existing http.HandlerFunc method into a HertzHandler.
-- You can directly use http.FileServer, embed.FS, and other official ecosystems
-- You can even use this directly at Hertz github.com/gorilla/websocket
+- Allows you to convert existing http.HandlerFunc methods directly to HertzHandler
+- Enables direct use of standard library methods like http.FileServer and embed.FS
+- Even allows direct use of github.com/gorilla/websocket in Hertz
 
 ## Example
 

content/en/docs/hertz/tutorials/basic-feature/sse.md

@@ -3,27 +3,20 @@ title: "SSE"
 date: 2025-05-21
 weight: 19
 keywords: ["SSE"]
-description: "SSE in Hertz"
+description: "SSE capabilities provided by Hertz"
 ---
-```Code：https://github.com/cloudwego/hertz/tree/develop/pkg/protocol/sse```
-
-**Changelog**
-
-- 2025/05/15 Has been released to the open-source version v0.10.0
-- 2025/05/13 [d3c68463] Added Get / SetLastEventID.
-- 2025/05/13 [3952e956] The Reader ForEach interface supports passing in ctx.
-- 2025/04/24 [cf38573ce] First version completed
+```code: https://github.com/cloudwego/hertz/tree/develop/pkg/protocol/sse```
 
 ## What is Server-Sent Events (SSE)
 
-- SSE is an HTML standard used to describe the implementation of the EventSource API in browsers. Strictly speaking, it is not an HTTP protocol.
-- Both the popular Model Context Protocol (MCP) and Agent2Agent (A2A) protocols are based to some extent on SSE
+- SSE is an HTML standard used to describe the implementation of browser EventSource API. Strictly speaking, it's not an HTTP protocol.
+- Popular protocols like Model Context Protocol (MCP) or Agent2Agent (A2A) are based on SSE to some extent
   - https://www.anthropic.com/news/model-context-protocol
   - https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/
 
-## Server Implementation
+## Server-side Implementation
 
-### Return data
+### Returning Data
 
 ```go
 import "github.com/cloudwego/hertz/pkg/protocol/sse"
@@ -35,78 +28,79 @@ func HandleSSE(ctx context.Context, c *app.RequestContext) {
         w.WriteEvent("id-x", "message", []byte("hello\n\nworld"))
         time.Sleep(10 * time.Millisecond)
     }
-    w.Close() // Send the last chunk of data to ensure graceful exit. Optional, Hertz will automatically call this after the Handler returns.
+    w.Close() // Send the last chunk of data to ensure graceful exit. Optional, Hertz will automatically call it after the Handler returns.
 
-    // Please make sure that the lifecycle of the writer is consistent with that of the handler. Do not use it in asynchronous background.
+    // Please ensure the writer's lifecycle is consistent with the handler. Don't use it asynchronously in the background.
 }
 ```
 
-### FAQ
+### Common Issues
 
 #### connection has been closed when flush
 
-Reason: The client connection has been disconnected, possibly due to a long time without response data. Please check the corresponding configuration.
+Reason:
+Client connection is disconnected, possibly due to no response data for too long. Please check the relevant configuration.
 
-## Client Implementation
+## Client-side Implementation
 
-### Initiate a request
+### Initiating a Request
 
-It's exactly the same as making a normal HTTP request to Hertz.
-Note: The new Hertz version will automatically recognize SSE streams, so you don't need to explicitly set `WithResponseBodyStream(true)`
+It's exactly the same as initiating a regular HTTP request with Hertz.
+Note: New Hertz versions will automatically identify SSE streams, so you don't need to explicitly set WithResponseBodyStream(true)
 
-**Some optional headers**
+**Some Optional Headers**
 
 ```go
 import "github.com/cloudwego/hertz/pkg/protocol/sse"
 
-sse.AddAcceptMIME(req) // Some SSE Servers may require explicit addition of Accept: text/event-stream
-sse.SetLastEventID(req, "id-123") // For stateful services, you need to tell the Server via SetLastEventID
+sse.AddAcceptMIME(req) // Some SSE Servers may require explicitly adding Accept: text/event-stream
+sse.SetLastEventID(req, "id-123") // For stateful services, you need to tell the Server through SetLastEventID
 ```
 
-### Handle response
+### Handling Responses
 
 ```go
 import "github.com/cloudwego/hertz/pkg/protocol/sse"
 
 func HandleSSE(ctx context.Context, resp *protocol.Response) error {
     r, err := sse.NewReader(resp)
     if err != nil {
-        return err
+    return err
     }
-    
-    // You can also call the r.Read method manually
+
+    // You can also manually call the r.Read method
     err = r.ForEach(ctx, func(e *Event) error {
         println("Event:", e.String())
         return nil
     })
-    if err != nil { // If the Server is disconnected normally, err == nil here, no error will be reported
-        // Other io errors or ctx cancelled
+    if err != nil { // If the Server disconnects normally, err == nil, no error will be reported
+        // Other IO errors or ctx cancelled
         return err
     }
     println("Client LastEventID", r.LastEventID()) // Can be used to save the last received Event ID
     return nil
 }
 ```
 
-### FAQ
+### Common Issues
 
-#### How to implement multi-level SSE/SSE Proxy?
+#### How to implement multi-level SSE / SSE Proxy?
 
-- You can refer to the implementations on both the Client and Server sides simultaneously
-- Enable `WithSenseClientDisconnection` in the server and pass the context to the next hop's Reader ForEach
-  - In this way, when the Client disconnects, it will be automatically recognized, and the entire stream will be interrupted
+- You can refer to both Client-side and Server-side implementations
+- Enable `WithSenseClientDisconnection` on the Server and pass the context to the next hop's Reader ForEach
+  - This way, when the Client disconnects, it will be automatically detected and the entire stream will be interrupted
 
-## Event Struct
+## Event Structure
 
 ```go
 // Event represents a Server-Sent Event (SSE).
 type Event struct {
-    ID string // Event ID, sse.Reader will automatically record the last Event ID, which can be obtained using LastEventID()
-    Type string // Event Type, such as "message"
-    Data []byte // []byte is used here for the convenience of Unmarshal/Marshal, but according to spec, this field must be utf8 string
+    ID   string // This is the Event ID, sse.Reader will automatically record the last Event ID, which can be obtained using LastEventID()
+    Type string // This is the Event Type, common ones like "message"
+    Data []byte // For convenience with Unmarshal/Marshal, []byte is used here, but according to the spec, this field must be a utf8 string
 
-    // Not recommended, mainly for the browser's SourceEvent to return this field to control its retry strategy.
-    // If you use Hertz as a client, you can refer to: https://www.cloudwego.io/docs/hertz/tutorials/basic-feature/retry/
+    // Not recommended to use, mainly for controlling the retry strategy of the browser's SourceEvent.
+    // If using Hertz as a Client, you can refer to: https://www.cloudwego.io/docs/hertz/tutorials/basic-feature/retry/
     Retry time.Duration
 }
 ```

content/zh/docs/hertz/tutorials/basic-feature/http-adaptor.md

@@ -8,14 +8,14 @@ description: ""
 
 ## 背景
 
-- 淘汰长期没有良好维护的 hertz 原生 fs 实现；
+- 淘汰长期没有良好维护的 hertz app.FS 实现
 - 通过官方 net/http 生态提供一个兼容性较好，性能也不差的 fs 实现。
 - 通过官方 net/http 生态扩展 hertz 功能，减少大量扩展实现
 
 ## 什么是 adaptor.HertzHandler
 
 - 允许你将现有的 http.HandlerFunc 方法直接转为 HertzHandler
-- 可以直接使用 http.FileServer embed.FS 等官方生态
+- 可以直接使用 http.FileServer embed.FS 等标准库方法
 - 甚至可以直接在 Hertz 使用 github.com/gorilla/websocket
 
 ## 具体例子

content/zh/docs/hertz/tutorials/basic-feature/sse.md

@@ -7,13 +7,6 @@ description: "Hertz 提供的 SSE 能力"
 ---
 ```代码：https://github.com/cloudwego/hertz/tree/develop/pkg/protocol/sse```
 
-**Changelog**
-
-- 2025/05/15 已发布到开源版本 v0.10.0
-- 2025/05/13 [d3c68463] 增加 Get / SetLastEventID
-- 2025/05/13 [3952e956] Reader ForEach 接口支持传入 ctx
-- 2025/04/24 [cf38573ce] 第一版本完成
-
 ## 什么是 Server-Sent Events (SSE)
 
 - SSE 是一个 HTML 标准，用于描述浏览器 EventSource API 的实现。严格说，不是 http 协议。