diff --git a/en-US/dita/RTC-NG/release/release_notes.dita b/en-US/dita/RTC-NG/release/release_notes.dita
index d153d32b367..04ab00d52e6 100644
--- a/en-US/dita/RTC-NG/release/release_notes.dita
+++ b/en-US/dita/RTC-NG/release/release_notes.dita
@@ -21,16 +21,14 @@
                                 </ul>                                <ph>此外，该版本还新增了 <codeph><apiname keyref="enableContentInspectEx"/></codeph> 方法，支持同时对多条视频流截图并上传。</ph>
                             </p>
                         </li>
-                        <li props="cpp"><ph><b>ID3D11Texture2D Rendering </b></ph><p>自该版本起，SDK 支持 ID3D11Texture2D 类型的视频格式，提升了游戏场景中视频帧的渲染效果。 你可以在调用 <codeph><apiname keyref="pushVideoFrame"/></codeph> 方法将外部原始视频帧推送到 SDK 时，设置 <parmname>format</parmname> 为 <codeph>VIDEO_TEXTURE_ID3D11TEXTURE2D</codeph>；并通过设置 <parmname>*d3d11_texture_2d</parmname> 和 <parmname>texture_slice_index</parmname> 属性，来确定要使用的 ID3D11Texture2D 纹理对象。</p>
+                        <li props="cpp"><ph><b>ID3D11Texture2D Rendering </b></ph><p>As of this release, the SDK supports video formats of type ID3D11Texture2D, improving the rendering effect of video frames in game scenarios. You can set <parmname>format</parmname> to <codeph>VIDEO_TEXTURE_ID3D11TEXTURE2D</codeph> when pushing external raw video frames to the SDK by calling . By setting the *<parmname>d3d11_texture_2d</parmname> and texture_slice_index properties, you can determine the ID3D11Texture2D<parmname> texture</parmname> object to use.<codeph><apiname keyref="pushVideoFrame"/></codeph></p>
                         </li>
-                        <li props="cpp"><ph><b>本地视频状态错误码更新</b></ph>
-                            <p>为了帮助用户在屏幕共享场景下了解本地视频出错的准确原因，<codeph><apiname keyref="onLocalVideoStateChanged"/></codeph> 回调中新增了如下几组枚举：
-                            <ul>
-                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_PAUSED"/></codeph>(23)：屏幕采集已暂停。 Common scenarios for reporting this error code: The current screen may have been switched to a secure desktop, such as a UAC dialog box or Winlogon desktop.</li>
-                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_RESUMED"/></codeph>(24)：屏幕采集已从暂停状态中恢复。</li>
-                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_WINDOW_HIDDEN"/></codeph>(25)：当前屏幕采集的窗口处于隐藏状态，并且在当前屏幕上不可见。</li>
-                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_WINDOW_RECOVER_FROM_HIDDEN"/></codeph>(26)：进行屏幕采集的窗口已经从隐藏状态中恢复。</li>
-                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_WINDOW_RECOVER_FROM_MINIMIZED"/></codeph>(27)：进行屏幕采集的窗口已经从最小化状态中恢复。</li>
+                        <li props="cpp"><ph><b>Local video status error code update</b></ph><p>In order to help users understand the exact reasons for local video errors in screen sharing scenarios, the following sets of enumerations have been added to the <codeph><apiname keyref="onLocalVideoStateChanged"/></codeph> callback:<ul>
+                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_PAUSED"/></codeph>(23): Screen capture has been paused. Common scenarios for reporting this error code: The current screen may have been switched to a secure desktop, such as a UAC dialog box or Winlogon desktop.</li>
+                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_RESUMED"/></codeph>(24): Screen capture has resumed from the paused state.</li>
+                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_WINDOW_HIDDEN"/></codeph>(25): The window being captured on the current screen is in a hidden state and is not visible on the current screen.</li>
+                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_WINDOW_RECOVER_FROM_HIDDEN"/></codeph>(26): The window for screen capture has been restored from the hidden state.</li>
+                            <li><codeph><apiname keyref="LOCAL_VIDEO_STREAM_ERROR_SCREEN_CAPTURE_WINDOW_RECOVER_FROM_MINIMIZED"/></codeph>(27): The window for screen capture has been restored from the minimized state.</li>
                             </ul></p>
                         </li>
                     </ol>
@@ -43,14 +41,13 @@
                         <li><ph><b>优化虚拟背景内存占用</b></ph>
                             <p>该版本升级了虚拟背景算法，降低了虚拟背景功能的内存占用。 相比之前的版本，在低端机上使用虚拟背景功能时 App 运行占用的内存降低了约 4%~10%（具体数值取决于设备型号和平台）。</p>
                         </li>
-                        <li props="cpp android"><ph><b>屏幕共享场景优化</b></ph>
-                            <p props="cpp">该版本优化了在超高清（4K，60 fps）游戏共享场景下的性能和编码效率，有效降低了屏幕共享时系统资源占用率。</p>
-                            <p props="android">该版本优化了屏幕共享场景下的视频编码配置。 当用户自定义视频的 <codeph>width</codeph> 和 <codeph>height</codeph> 属性时，SDK 会在保持视频与屏幕的宽高比一致的前提下，对实际的编码分辨率进行向下取整，确保最终编码分辨率不超过用户自定义的编码分辨率，从而提升了对屏幕共享流的计费准确性。</p>
+                        <li props="cpp android"><ph><b>Screen sharing scenario optimization</b></ph><p props="cpp">This release optimizes the performance and encoding efficiency in ultra-high-definition (4K, 60 fps) game sharing scenarios, effectively reducing the system resource usage during screen sharing.</p>
+                            <p props="android">This version optimizes the video encoding configuration in screen sharing scenarios. When users customize the <codeph>width</codeph> and <codeph>height</codeph> properties of the video, the SDK rounds down the actual encoding resolution while maintaining the aspect ratio of the video and the screen, ensuring that the final encoding resolution does not exceed the user-defined encoding resolution, thereby improving the accuracy of billing for screen sharing streams.</p>
                         </li>
                     </ol>
-                    <p><b>其他改进</b></p>
+                    <p><b>Other Improvements</b></p>
                     <p>This release includes the following additional improvements:<ul>
-                        <li props="android">优化了 SDK 采集和自定义视频采集场景下 Texture Buffer 的管理方式，有效消除丢帧和崩溃隐患。</li>
+                        <li props="android">Optimizes the management method of Texture Buffer for SDK capture and custom video capture scenarios, effectively eliminating frame dropping and crash risks.</li>
                          <li>当调用 <codeph><apiname keyref="setPlaybackSpeed"/></codeph> 设置音频文件的播放进度时，传入非法参数后会返回错误码 -2，表示方法中设置了无效的参数，需要重新设置参数。</li>
                          <li>优化了 Token 解析时的逻辑，避免传入非法 Token 后 App 发生崩溃。</li>
                         </ul></p>
@@ -61,8 +58,8 @@
                 <body>
                     <p>This release fixed the following issues:</p>
                     <ul>
-                        <li props="cpp">在屏幕共享场景下偶现崩溃、掉帧。</li>
-                        <li props="android">在采用 H.265 编码模式时，如果 Web 端加入互动，会导致 Native 端出现冗余的  <codeph><apiname keyref="onUserEnableLocalVideo"/></codeph> 回调：当主播调用 <codeph><apiname keyref="enableLocalVideo"/>(true)</codeph>时，接收端在收到 <codeph><apiname keyref="onUserEnableLocalVideo"/></codeph> (<codeph>enabled</codeph> 为 <codeph>true</codeph>) 回调之前，会先收到一个 <codeph><apiname keyref="onUserEnableLocalVideo"/></codeph> (<codeph>enabled</codeph> 为 <codeph>false</codeph>) 回调。</li>
+                        <li props="cpp">Occasional crashes and dropped frames occured in screen sharing scenarios.</li>
+                        <li props="android">When using the H.265 encoding mode, when a Web client joined the interactivity, it caused a redundant <codeph><apiname keyref="onUserEnableLocalVideo"/></codeph> callback on the native side: when the host called <codeph><apiname keyref="enableLocalVideo"/> (true)</codeph>, the receiving end first received a <codeph><apiname keyref="onUserEnableLocalVideo"/></codeph> callback with (<codeph>enabled</codeph> as <codeph>false</codeph>) before receiving a <codeph><apiname keyref="onUserEnableLocalVideo"/></codeph> callback with (<codeph>enabled</codeph> as <codeph>true</codeph>).</li>
                         <li props="mac unity flutter"><p><ph>加入频道偶现的崩溃。 </ph><ph>(macOS)</ph></p></li>
                         <li>本地系统时间不正确时，偶现加入频道失败。</li>
                         <li>调用 playEffect 使用相同的 soundId 播放两个不同的音效文件，偶现第一个音效文件播放完毕后会重复播放。</li>
@@ -70,8 +67,8 @@
                         <li props="android ios unity flutter rn"><p><ph>合唱场景下，调用 <codeph><apiname keyref="preload"/></codeph> 加载音乐，偶现加载失败。 </ph>(Android, iOS)<ph props="unity flutter"></ph></p></li>
                         <li props="android unity flutter rn"><p><ph>在特定机型上开启 AI 降噪偶现崩溃。 </ph><ph props="unity flutter rn">(Android)</ph></p></li>
                         <li props="android ios unity flutter rn"><p><ph>当本地系统时间不准确时，歌曲榜单加载失败。 </ph><ph props="unity flutter">(Android, iOS)</ph></p></li>
-                        <li>调用一次 takeSnapshotEx 获取视频截图会收到多次 onSnapshotTaken 视频截图结果回调。</li>
-                        <li props="android unity flutter rn"><p><ph>在仅调用 <codeph><apiname keyref="joinChannelEx"/></codeph> 加入的频道中，调用 <codeph><apiname keyref="setEnableSpeakerphone"/></codeph> 无法将音频路由从扬声器切换至听筒。 </ph>(Android)<ph props="unity flutter rn"></ph></p></li>
+                        <li>调用一次 <codeph><apiname keyref="takeSnapshotEx"/></codeph> 获取视频截图会收到多次 <codeph><apiname keyref="onSnapshotTaken"/></codeph> 视频截图结果回调。</li>
+                        <li props="android unity flutter rn"><p><ph>在仅调用 <codeph><apiname keyref="joinChannelEx"/></codeph> 加入的频道中，调用 <codeph><apiname keyref="setEnableSpeakerphone"/></codeph> 无法将音频路由从扬声器切换至听筒。 </ph><ph props="unity flutter rn">(Android)</ph></p></li>
                     </ul>
                 </body>
             </topic>