@tencent-rtc/mcp 1.4.6 → 1.6.0-beta.1

package/resource/{doc → knowledge}/livekit/core-sdk/live/android/live-live-list.md

@@ -8,12 +8,13 @@
 - **Real-Time Event Listening**: Listen for key events such as live session end or users being removed from a room.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibility & Description** |
-| --- | --- | --- |
-| `LiveInfo` | `data class` | Represents the complete information model of a live room. Includes the live room ID (liveID), name (liveName), owner information (liveOwner), and custom metadata (metaData), among other properties. |
-| `LiveListState` | `data class` | Represents the current state of the live list module. The core property liveList is a StateFlow containing the fetched live room list; currentLive represents the information of the live room the user is currently in. |
-| `LiveListListener` | `abstract class` | Handles global live room events, including onLiveEnded (live ended) and onKickedOutOfLive (user removed from live), for responding to key room state changes. |
-| `LiveListStore` | `abstract class` | The core management class for interacting with the live room list and room lifecycle. It is a global singleton responsible for all operations such as creating, joining, and updating live room information. |
+
+|**Core Concept**|**Type**|**Core Responsibility & Description**|
+|---------|---------|---------|
+|`LiveInfo`|`data class`|Represents the complete information model of a live room. Includes the live room ID (liveID), name (liveName), owner information (liveOwner), and custom metadata (metaData), among other properties.|
+|`LiveListState`|`data class`|Represents the current state of the live list module. The core property liveList is a StateFlow containing the fetched live room list; currentLive represents the information of the live room the user is currently in.|
+|`LiveListListener`|`abstract class`|Handles global live room events, including onLiveEnded (live ended) and onKickedOutOfLive (user removed from live), for responding to key room state changes.|
+|`LiveListStore`|`abstract class`|The core management class for interacting with the live room list and room lifecycle. It is a global singleton responsible for all operations such as creating, joining, and updating live room information.|
 
 ## Implementation
 
@@ -140,16 +141,17 @@ class LiveListAdapter(
 ```
 
 #### LiveInfo Parameter Reference
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `liveID` | `String` | Unique identifier for the live room |
-| `liveName` | `String` | Title of the live room |
-| `coverURL` | `String` | Cover image URL for the live room |
-| `liveOwner` | [LiveUserInfo](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-live-user-info/index.html) | Personal information of the room owner |
-| `totalViewerCount` | `Int` | Total number of viewers in the live room |
-| `categoryList` | `List<Int>` | List of category tags for the live room |
-| `notice` | `String` | Announcement information for the live room |
-| `metaData` | `Map<String, String>` | Developer-defined metadata for implementing advanced business scenarios |
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`liveID`|`String`|Unique identifier for the live room|
+|`liveName`|`String`|Title of the live room|
+|`coverURL`|`String`|Cover image URL for the live room|
+|`liveOwner`|[LiveUserInfo](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-live-user-info/index.html)|Personal information of the room owner|
+|`totalViewerCount`|`Int`|Total number of viewers in the live room|
+|`categoryList`|`List<Int>`|List of category tags for the live room|
+|`notice`|`String`|Announcement information for the live room|
+|`metaData`|`Map<String, String>`|Developer-defined metadata for implementing advanced business scenarios|
 
 ## Advanced Features
 
@@ -384,10 +386,11 @@ class LiveFeedActivity : AppCompatActivity() {
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [LiveListStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-live-list-store/index.html) and related classes, refer to the official API documentation included with the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Android/index.html) framework. The relevant Stores used in this document are as follows:
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| LiveCoreView | Core view component for live video stream display and interaction. Responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host linking. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html) |
-| LiveListStore | Full lifecycle management of live rooms: create, join, leave, destroy rooms; query room list; modify live information (name, announcement, etc.); listen to live status (such as being removed or ended). | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-live-list-store/index.html) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|LiveCoreView|Core view component for live video stream display and interaction. Responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host linking.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html)|
+|LiveListStore|Full lifecycle management of live rooms: create, join, leave, destroy rooms; query room list; modify live information (name, announcement, etc.); listen to live status (such as being removed or ended).|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-live-list-store/index.html)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/live/flutter/live-audience-list.md

@@ -1,38 +1,39 @@
 `LiveAudienceStore` is a module in `AtomicXCore` specialized in managing live streaming room audience information. With `LiveAudienceStore`, you can build a complete audience list and management system for your live stream application.
 
 ## Core Features
-- **Real-time Audience List**: Get and show ALL audience information currently in the live streaming room.
+- **Real-Time Audience List**: Access and display details for all current audience members in the live room.
 
-- **Audience Statistics**: Get the accurate total number of audience in the live streaming room in real time.
+- **Audience Count Statistics**: Get the real-time total number of audience members in the live room.
 
-- **Audience Dynamics Monitoring**: Perceive audience join and leave in real time through event subscription.
+- **Audience Events**: Subscribe to events to instantly detect when audience members join or leave.
 
-- **Administrator Permissions**: The Anchor can set a general audience as administrator or revoke their administrator privileges.
+- **Admin Privileges**: Hosts can promote audience members to administrators or revoke their admin status.
 
-- **Room Management**: The Anchor or admin can kick out any general audience from the live streaming room.
+- **Room Management**: Hosts or administrators can remove (kick out) any regular audience member from the live room.
 
 ## Core Concepts
 
 The following table introduces the core concepts of `LiveAudienceStore`:
-| **Core Concepts** | **Type** | **Core Responsibilities and Description** |
-| --- | --- | --- |
-| [LiveUserInfo](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveUserInfo-class.html) | `class` | Represents a foundation Information Model for an audience (user). It contains the user's unique identifier (`userID`), Nickname (`userName`) and profile photo url (`avatarURL`). |
-| [LiveAudienceState](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceState-class.html) | `class` | Represents the current status of the audience module. Its core attribute `audienceList` is a `ValueListenable<List<LiveUserInfo>>`, storing a snapshot of the audience list; `audienceCount` signifies the total number of current audience. |
-| [LiveAudienceListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceListener-class.html) | `class` | Represents a real-time event listener for audience dynamics. It includes two callbacks, `onAudienceJoined` (audience joined) and `onAudienceLeft` (audience left), used to incrementally update the audience list. |
-| [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html) | `class` | This is the core management class for interacting with the audience list function. Through it, you can obtain audience list snapshots, perform operation management, and receive real-time updates via `addLiveAudienceListener`. |
+
+|**Core Concepts**|**Type**|**Core Responsibilities and Description**|
+|---------|---------|---------|
+|[LiveUserInfo](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveUserInfo-class.html)|`class`|Represents the basic information model for an audience member. Includes the user’s unique identifier (`userID`), nickname (`userName`), and avatar URL (`avatarURL`).|
+|[LiveAudienceState](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceState-class.html)|`class`|Represents the current status of the audience module. Its core attribute `audienceList` is a `ValueListenable<List<LiveUserInfo>>`, storing a snapshot of the audience list; `audienceCount` signifies the total number of current audience.|
+|[LiveAudienceListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceListener-class.html)|`class`|Handles real-time event listening for audience activity. Includes two callbacks: `onAudienceJoined` (audience member joins) and `onAudienceLeft` (audience member leaves), used for incremental updates to the audience list.|
+|[LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html)|`class`|The main management class for audience list operations. Use it to get audience snapshots, perform management actions, and receive real-time updates via `addLiveAudienceListener`.|
 
 ## Implementation Steps
 
-### Step 1: Component Integration
+### Step 1: Integrate the Components
 - **Live streaming**: Refer to Quick Access for seamless integration with **AtomicXCore** and service access.
 
 - **Voice chat room**: Refer to Quick Access for integration with **AtomicXCore** and access completed.
 
 ### Step 2: Initialize and Obtain Audience List
 
-Retrieve a `LiveAudienceStore` instance bound to the current live streaming room liveId, actively pull the current audience list once for first-time show.
+Retrieve a `LiveAudienceStore` instance bound to the current live streaming room `liveId`, actively pull the current audience list once for first-time show.
 
-When exiting the live streaming room, you can reclaim resources by calling the `AudienceManager`'s `dispose` method.
+To release resources when leaving the live room, call the `dispose` method on AudienceManager.
 ``` java
 import 'package:atomic_x_core/atomicxcore.dart';
 
@@ -86,7 +87,7 @@ The audience list and other `state` subscriptions will be explained in detail in
 
 ### Step 3: Monitoring the Audience List Status and Real-Time Updates
 
-Subscribe to `audienceStore`'s `liveAudienceState` and `LiveAudienceListener` to receive full list snapshots and real-time audience Enter/Exit Events, thereby driving UI updates.
+Subscribe to `liveAudienceState` and `LiveAudienceListener` on `audienceStore` to receive full audience list snapshots and real-time join/leave events, driving UI updates.
 ``` java
 extension AudienceManagerSubscription on AudienceManager {
     /// Subscribe to state to obtain the total count of audience and list snapshots
@@ -132,11 +133,11 @@ extension AudienceManagerSubscription on AudienceManager {
 }
 ```
 
-### Step 4: Manage Audience (Remove User and Set Administrator)
+### Step 4: Manage Audience Members
 
-As an Anchor or admin, perform management operations on the audience in the live streaming room.
+As a host or administrator, you can manage audience members in the live room.
 
-#### 4.1 Kick Out Audience From Live Streaming Room
+#### 4.1 Remove Audience Member from Live Room
 
 Call the `kickUserOutOfRoom` API to remove designated users from the live streaming room.
 ``` java
@@ -153,7 +154,7 @@ extension AudienceManagerActions on AudienceManager {
 }
 ```
 
-#### 4.2 Set/Revoke Admin
+#### 4.2 Set or Revoke Administrator Privileges
 
 Use the `setAdministrator` and `revokeAdministrator` APIs to manage user administrator privileges.
 ``` java
@@ -178,15 +179,15 @@ extension AudienceManagerAdmin on AudienceManager {
 
 ## Advanced Features
 
-### Show the Welcome Message in the Bullet Screen Area
+### Show Welcome Message in Live Comments
 
 When a new audience enters the live room, the bullet screen/chat area will automatically display a welcome message locally, such as "Welcome [user nickname] to the live room."
 
-#### Implementation Method
+#### Implementation
 
-We subscribe to the audience join event (`onAudienceJoined`) of `LiveAudienceStore` to get real-time notifications of new audience joins. Once the event is triggered, we extract the nickname information of the new audience, then immediately call the local insert API `appendLocalTip` of `BarrageStore`.
+Subscribe to the `onAudienceJoined` event from `LiveAudienceStore` to receive real-time notifications when a new audience member joins. When triggered, extract the user’s nickname and call the `appendLocalTip` API from BarrageStore to insert the welcome message.
 
-When exiting the live streaming room, you can reclaim resources by calling the `LiveRoomManager`'s `dispose` method.
+Release resources when leaving the live room by calling the `dispose` method on `LiveRoomManager`.
 ``` java
 import 'package:atomic_x_core/atomicxcore.dart';
 
@@ -230,31 +231,30 @@ class LiveRoomManager {
 
 ## API documentation
 
-For details about ALL public interfaces, properties, and methods of [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html) and its related classes, refer to the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Store used in this document is as follows:
-| **Store/Component** | **Feature Description** | **API Reference** |
-| --- | --- | --- |
-| **LiveCoreWidget** | The core view component for live video stream display and interaction: responsible for stream rendering and view widget processing, supporting live streaming, audience co-broadcasting, cross-room connection with other anchors, and other scenarios. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html) |
-| **LiveCoreController** | LiveCoreWidget controller: used to set up live streaming ID, control preview, and perform other operations. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html) |
-| **LiveAudienceStore** | Audience management: get real-time audience list (ID/name/avatar), check audience size, listen to Enter/Exit Event. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html) |
-| **BarrageStore** | Danmaku function: send text/custom barrage item, maintain bullet screen list, monitor in real time. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/api_barrage_barrage_store-library.html) |
+For detailed information on all public APIs, properties, and methods for [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html) and related classes, see the official [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) API documentation. The relevant Stores used in this guide are listed below:
 
-## FAQs
+|**Store/Component**|**Feature Description**|**API Reference**|
+|---------|---------|---------|
+|**LiveCoreWidget**|Core view component for live video stream display and interaction. Handles video stream rendering and widget management, supporting host live streaming, audience co-hosting, and host connection scenarios.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html)|
+|**LiveCoreController**|LiveCoreWidget controller: used to set up live streaming ID, control preview, and perform other operations.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html)|
+|**LiveAudienceStore**|Audience management: get real-time audience list (ID/name/avatar), check audience size, listen to Enter/Exit Event.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html)|
+|**BarrageStore**|Live comments: send text/custom comments, maintain the comment list, and monitor comment status in real time.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/api_barrage_barrage_store-library.html)|
 
-### `LiveAudienceState` How Is the Number of Online Users (`AudienceCount`) Updated? What Is the Timing and How Often?
+## FAQs
 
-`audienceCount` update is not always real-time. The mechanism is as follows:
-- **Proactive enter and exit rooms**: When users proactively join or normally exit live streaming room, the change notification of number of online users will immediate trigger. You will soon observe the changes of `audienceCount` in `LiveAudienceState`.
+### How is the online audience count (audienceCount) in LiveAudienceState updated? What are the timing and frequency?
+- **Active Room Entry/Exit:** When a user joins or leaves the live room normally, the audience count notification is triggered instantly. You will immediately see the change in audienceCount in LiveAudienceState.
 
-- **Unexpected disconnection**: When a user unexpectedly disconnects due to network issue, application crash, etc., the system needs to determine their actual status through heartbeat mechanism. Only when the user has no heartbeat for 90 consecutive seconds will the system deem them offline and trigger the change notification of number of users.
+- **Abnormal Disconnection**: If a user disconnects due to network issues, app crashes, or similar problems, the system uses a heartbeat mechanism to determine their status. Only after missing heartbeats for 90 consecutive seconds will the system consider the user offline and trigger a count change notification.
 
-- **Update mechanism and frequency control:**
+- **Update Mechanism & Frequency Control**:
 
-  - Whether it is immediate trigger or delay trigger, all change notifications of number of users are broadcast in the room in the form of messages.
+  - Whether triggered instantly or delayed, all audience count change notifications are sent as messages within the room.
 
-  - The message total inside the room has a capacity limit per second, with a single room message frequency control of **40 messages per second**.
+  - Each room is limited to a maximum of 40 messages per second.
 
-  - **Key points:** In scenarios with extremely high message traffic such as "bullet screen storm" or gift spam, if the message rate inside the room exceeds the threshold of 40 messages per second, to ensure the delivery of core messages (for example, bullet screen), **messages of number of users change may be dropped by the frequency control policy**.
+- Key Point: In high-traffic scenarios, such as live comment storms or gift spamming, if the room’s message rate exceeds 40 messages per second, the system prioritizes core messages (like live comments). Audience count change messages may be dropped due to frequency control.
 
-      **What does this mean for developers?**
+   **What does this mean for developers?**
 
-      `audienceCount` is a **high-precision estimate** very close to real time, but under extreme high concurrency scenarios, it may have brief delay or data loss. Therefore, we recommend that you use it for **UI display** and should not take it as the only basis for scenarios requiring absolute accuracy such as billing or statistics.
+   `audienceCount` is a **high-precision estimate** very close to real time, but under extreme high concurrency scenarios, it may have brief delay or data loss. Therefore, we recommend that you use it for **UI display** and should not take it as the only basis for scenarios requiring absolute accuracy such as billing or statistics.

package/resource/{doc → knowledge}/livekit/core-sdk/live/flutter/live-audio-effect.md

@@ -1,34 +1,35 @@
-This document aims to guide you on how to use the `AtomicXCore` framework's `AudioEffectStore` and `DeviceStore` modules to quickly integrate audio effect control features for your live stream app, including Microphone Volume, listen, and add multiple fun voice-changing effects and reverb effects.
+This guide shows you how to use the `AudioEffectStore` and `DeviceStore` modules from the `AtomicXCore` framework to quickly add audio effect controls to your live streaming app. With these modules, you can implement features like microphone volume adjustment, in-ear monitoring, and a range of engaging voice changer and reverb effects.
 
 ## Core Features
 
-By combining `AudioEffectStore` and `DeviceStore`, you can implement the following core features:
-- **Vocal Volume Adjustment**: Controls the capturing volume of Local Audio Uplink, which determines the Anchor's sound level heard by the audience.
+By integrating `AudioEffectStore` and `DeviceStore`, you can enable the following features in your live streaming app:
+- **Microphone Volume Control**: Adjust the local capture volume to control how loud the host sounds to the audience.
 
-- **Ear monitoring function**: Allows the Anchor or co-streaming users to hear their own sound in real-time through headphones for listening and pronunciation correction.
+- **In-Ear Monitor**: Let hosts or guests hear their own voice in real time through headphones for monitoring and pronunciation correction.
 
-- **Voice-changing effects**: Offers multiple fun voice changing options, such as lolita, uncle, and mischievous child.
+- **Voice Changer Effects**: Provide multiple voice changer options, such as Child, Girl, Uncle, and more.
 
-- **Reverb effect**: Simulates sound field effects in different environments, such as KTV, metallic sound, deep, and resonant.
+- **Reverb Effects**: Simulate various acoustic environments, including KTV, metallic, deep, bright, and others.
 
-## Conceptual Introduction
-| **Core Concept** | **Type** | **Core Responsibilities and Description** |
-| --- | --- | --- |
-| [AudioEffectState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectState-class.html) | `class` | Represents the current status of the audio effect module, usually used for UI rendering. Includes voice-changing status, reverberation status, ear return enabled status, ear return volume. All attributes are `ValueListenable` data type, support subscription listen. |
-| [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html) | `class` | Represents the **singleton data management class** of the audio effect module. Through it you can call the audio effect API to modify sound effects. When you call the API, the appropriate `audioEffectState` property will auto-update. You can subscribe to this state's responsive data to receive and listen for status updates. |
-| [DeviceState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceState-class.html) | `class` | Represents the current status of the device module, usually used for UI rendering. Core attributes include device status of camera, microphone, capturing volume. All attributes are `ValueListenable` data type, support subscription listen. |
-| [DeviceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) | `class` | Represents the **singleton data management class** of the device module. Through it you can call the API to operate camera and microphone. When you call the API, the appropriate `state` property will auto-update. You can subscribe to this state's responsive data to receive and listen for status updates. |
+## Concept Overview
+
+|Core Concept|Type|Key Responsibilities & Description|
+|---------|---------|---------|
+|[AudioEffectState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectState-class.html)|class|Tracks the current state of the audio effects module, typically for UI rendering. Includes voice changer status, reverb status, in-ear monitor enabled status, and in-ear monitor volume. All properties are ValueListenable and support state change subscriptions.|
+|[AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html)|class|Singleton data manager for the audio effects module. Use this to call audio effect APIs. After you call an API, the relevant audioEffectState property updates automatically; subscribe to this reactive state for real-time updates.|
+|[DeviceState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceState-class.html)|class|Tracks the current state of the device module, typically for UI rendering. Key properties include camera and microphone device status, capture volume, and more. All properties are ValueListenable and support state change subscriptions.|
+|[DeviceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html)|class|Singleton data manager for the device module. Use this to control camera and microphone APIs. After you call an API, the relevant state property updates automatically; subscribe to this reactive state for real-time updates.|
 
 ## Implementation Steps
 
-### Step 1: Integrating the Component
-- **Live streaming**: Refer to quick integration to integrate **AtomicXCore** and complete service access.
+### Step 1: Integrate the Component
+- **Live streaming**: Refer to Quick Integration to integrate **AtomicXCore** and complete service access.
 
-- **Voice chat room**: Refer to quick integration to integrate **AtomicXCore** and complete service access.
+- **Voice chat room**: Refer to Quick Integration to integrate **AtomicXCore** and complete service access.
 
 ### Step 2: Obtain a Store Instance
 
-`AudioEffectStore` and `DeviceStore` are singleton objects. You can directly get instance via the `shared` property in any location in the project. You can also refer to the [audio_effect_panel_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/component/audio_effect/audio_effect_panel_widget.dart) file in the TUILiveKit open-source UI demo project to learn about the complete implementation logic.
+Both `AudioEffectStore` and `DeviceStore` are singletons. You can access their instances anywhere in your project using the shared property. For a full implementation example, refer to the [audio_effect_panel_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/component/audio_effect/audio_effect_panel_widget.dart) file in the TUILiveKit open-source UI demo project.
 ``` java
 import 'package:flutter/material.dart';
 import 'package:atomic_x_core/atomicxcore.dart';
@@ -39,9 +40,9 @@ class _AudioEffectPanelWidgetState {
 }
 ```
 
-### Step 3: Implement the In-Ear Monitoring Feature
+### Step 3: Implement the In-Ear Monitor
 
-Ear monitoring function allows users to monitor their own microphone sound in real time. Calling the API introduced in this section can manage the ear monitoring function.
+In-ear monitor allows users to hear their own microphone input in real time. You can manage this feature using the APIs described below.
 
 > **Note:**
 >
@@ -49,12 +50,11 @@ Ear monitoring function allows users to monitor their own microphone sound in re
 > The in-ear monitoring feature typically needs to connect to headphones to work properly.
 >
 
-#### Implementation Method
-1. **Enable/Disable Ear Monitoring**: You can use the `Switch` control to implement the ear monitoring function.
+1. **Enable/Disable Ear Monitoring**: Use a Switch widget to enable or disable in-ear monitor.
 
-2. **Set the Volume of IEMs**: You can use the `Slider` control to implement the function of dragging the slider left and right to adjust volume, and map the `Slider` value to the volume value, then call `setVoiceEarMonitorVolume(volume)`. Please note, this API accepts a parameter range of `[0, 150]`, so you need to map the UI control value (such as the Slider's `0.0 - 1.0`) to the `0 - 150` range.
+2. **Set the Volume of IEMs**: Use a Slider widget to set the volume. Map the slider value to the volume parameter and call `setVoiceEarMonitorVolume(volume)`. The valid range is [0, 150], so map your UI control's value (e.g., slider 0.0 - 1.0) to 0 - 150.
 
-3. **Listen for Status Updates to Update UI**: You can subscribe to real-time ear monitoring status value updates to refresh the UI.
+3. **Listen for Status Updates to Update UI**: Listen for real-time in-ear monitor state changes to update your UI accordingly.
 
 #### Sample Code
 ``` java
@@ -111,24 +111,22 @@ class EarMonitorWidget extends StatelessWidget {
 }
 ```
 
-#### SetVoiceEarMonitorEnable API Parameter
-| **Parameter Name** | **Type** | **Description** |
+#### SetVoiceEarMonitorEnable API Parameters
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `enable` | `bool` | Enable earpiece feedback.<br>-  true: Enable<br>-  false: Disable |
+| <code>enable</code> | <code>bool</code> | Enable in-ear monitor:<br>- <code>true</code>: Enable.<br>- <code>false</code>: Disable. |
 
-#### SetVoiceEarMonitorVolume API Parameter
-| **Parameter Name** | **Type** | **Description** |
+#### SetVoiceEarMonitorVolume API Parameters
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `volume` | `int` | Ear return volume.<br>- Value ranges from 0 to 150.<br>- Default value: 100. |
-
-### Step 4: Implement Vocal Volume Adjustment
+| <code>volume</code> | <code>int</code> | Ear return volume.<br>- Value ranges from 0 to 150.<br>- Default value: 100. |
 
-When the Anchor hopes to adjust their own uplink capturing volume, call the `DeviceStore`'s `setCaptureVolume(volume)` method to input the volume value.
+### Step 4: Adjust Microphone Volume
 
-#### Implementation Method
+To control the host's microphone capture volume, call `DeviceStore.setCaptureVolume(volume)` with your desired value.
 1. **Set Capturing Volume**: You can use the `Slider` control to drag the slider left and right to adjust volume, and map the `Slider` value to the volume value before calling `setCaptureVolume(volume)`. Please note, this API accepts a parameter range of `[0, 150]`, so you need to map the UI control value (such as the Slider's `0.0 - 1.0`) to the `0 - 150` range.
 
-2. **Listen for Status Updates to Update UI**: You can subscribe to real-time volume level status value updates to refresh the UI.
+2. **Subscribe to State Updates**: Listen for real-time capture volume changes to update your UI.
 
 #### Sample Code
 ``` java
@@ -165,14 +163,14 @@ class CaptureVolumeWidget extends StatelessWidget {
 }
 ```
 
-#### SetCaptureVolume API Parameter
-| **Parameter Name** | **Type** | **Description** |
+#### SetCaptureVolume API Parameters
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `volume` | `int` | Capture volume size.<br>- Value ranges from 0 to 150.<br>- Default value: 100. |
+| <code>volume</code> | <code>int</code> | Capture volume size.<br>- Value ranges from 0 to 150.<br>- Default value: 100. |
 
-### Step 5: Implement Voice-Changing Effects
+### Step 5: Apply Voice Changer Effects
 
-When the Anchor hopes to change their own sound, you can call the `setAudioChangerType(type)` method, input the appropriate Type enumeration value to switch effect.
+To change the host's voice, call `setAudioChangerType(type)` and pass the desired enum value.
 
 #### Sample Code
 ``` java
@@ -238,14 +236,15 @@ class VoiceChangerWidget extends StatelessWidget {
 }
 ```
 
-#### SetAudioChangerType API Parameter
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `type` | [AudioChangerType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioChangerType.html) | Voice-changing effects enumeration. |
+#### SetAudioChangerType API Parameters
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`type`|[AudioChangerType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioChangerType.html)|Voice-changing effects enumeration.|
 
-### Step 6: Implement Reverb Effect
+### Step 6: Apply Reverb Effects
 
-When the Anchor hopes to add reverb effect to their own sound, you can call the `setAudioReverbType(type)` method, input the appropriate Type enumeration value to switch effect.
+To add reverb effects to the host's voice, call `setAudioReverbType(type)` and pass the desired enum value.
 
 #### Sample Code
 ``` java
@@ -319,10 +318,11 @@ class ReverbWidget extends StatelessWidget {
 }
 ```
 
-#### SetAudioReverbType API Parameter
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `type` | [AudioReverbType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioReverbType.html) | Reverb effects enumeration. |
+#### SetAudioReverbType API Parameters
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`type`|[AudioReverbType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioReverbType.html)|Reverb effects enumeration.|
 
 ### Step 7: Reset Sound Effect Settings
 
@@ -360,7 +360,7 @@ You may need to reset sound effect settings in the following two scenarios:
    }
    ```
 
-## Complete Example
+## Complete Sample Code
 ``` java
 import 'package:flutter/material.dart';
 import 'package:atomic_x_core/atomicxcore.dart';
@@ -561,37 +561,38 @@ class AudioEffectPage extends StatelessWidget {
 ## API documentation
 
 For detailed information about all public interfaces and attributes of [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html), [DeviceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) and its related classes, see the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework.
-| **Store/Component** | **Feature Description** | **API Reference** |
-| --- | --- | --- |
-| **AudioEffectStore** | Audio effect management: Perform audio effect settings and obtain real-time audio effect status. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html) |
-| **DeviceStore** | Device management: perform camera and microphone operations and obtain real-time device status. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) |
+
+|**Store/Component**|**Feature Description**|**API Reference**|
+|---------|---------|---------|
+|**AudioEffectStore**|Audio effect management: Perform audio effect settings and obtain real-time audio effect status.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html)|
+|**DeviceStore**|Device management: perform camera and microphone operations and obtain real-time device status.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html)|
 
 ## FAQs
 
-### Is There a Requirement for the Timing of Invocation of Sound Effects and Device Interfaces?
+### Are there any restrictions on when to call audio effect and device APIs?
 
-No limit. The settings of `AudioEffectStore` and `DeviceStore` take effect globally. You can call APIs (such as setting voice-changing, reverb, or ear monitoring) at any time before or after entering the live room. The settings will take effect immediately and be reserved.
+No, there are no restrictions. Settings in `AudioEffectStore` and `DeviceStore` are global. You can call related APIs (such as setting voice changer, reverb, or in-ear monitor) at any time before or after joining a live room. Changes take effect immediately and persist.
 
-### What Is the Difference between Voice Volume and Ear Return Volume?
+### What is the difference between "Microphone Volume" and "In-Ear Monitor Volume"?
 
-This is a very important and confusing concept. The difference is as follows:
-- **Voice Volume (CaptureVolume):** Set via `DeviceStore.shared.setCaptureVolume()`. It determines the Anchor's sound level heard by the audience.
+This is a common source of confusion. The differences are:
+- Microphone Volume (Capture Volume): Set via `DeviceStore.shared.setCaptureVolume()`. Controls how loud the host sounds to the audience.
 
-- **Ear Return Volume (EarMonitorVolume):** Set via `AudioEffectStore.shared.setVoiceEarMonitorVolume()`. It only determines the Anchor's headphone monitoring volume and **does not** impact the audience.
+- In-Ear Monitor Volume (Ear Monitor Volume): Set via `AudioEffectStore.shared.setVoiceEarMonitorVolume()`. Controls only how loud the host hears themselves in their headphones and does not affect the audience.
 
-### Why Does a Newly Created Live Streaming Room Have Sound Effects Directly or Issues Like Very High or Low Volume?
+### Why does a newly created live room already have audio effects, or the volume is unexpectedly high or low?
 
-`AudioEffectStore` and `DeviceStore` are singletons, which means audio effects and device settings take effect globally. This situation probably occurs because you set audio effects earlier but did not reset them. You need to call the `reset()` method in an appropriate place.
+Because `AudioEffectStore` and `DeviceStore` are singletons, audio effect and device settings are global. This usually happens if you previously set audio effects and didn't reset them. Be sure to call reset() when appropriate.
 
-### Why Did I Enable "Ear Return" but Cannot Hear My Own Sound?
+### Why can't I hear myself after enabling "In-Ear Monitor"?
 
-Please check by the following steps:
-1. **Whether to insert headphones**: The in-ear monitoring feature depends on headphones most of the time for the changes to take effect. Please ensure wired or Bluetooth headphones are connected.
+Check the following:
+1. Are headphones connected? In-ear monitor usually requires headphones. Make sure wired or Bluetooth headphones are connected.
 
-2. **Whether the volume is 0**: Check if the "ear return volume" is set to 0.
+2. Is the volume set to 0? Verify that "In-Ear Monitor Volume" is not set to 0.
 
-3. **Is the microphone enabled**: Confirm that the microphone in `DeviceStore` is enabled (the `openLocalMicrophone()` call has been made).
+3. Is the microphone enabled? Ensure that the microphone in DeviceStore is enabled (i.e., openLocalMicrophone() has been called).
 
-### Can Voice-Changing Effects and Reverb Effects Take Effect at the Same Time?
+### Can I use voice changer and reverb effects at the same time?
 
-Yes. `AudioChangerType` and `AudioReverbType` can take effect in superposition. For example, you can simultaneously set `AudioChangerType.girl` voice-changing and `AudioReverbType.ktv` reverb.
+Yes. `AudioChangerType` and `AudioReverbType` can be used together. For example, you can apply both `AudioChangerType.girl` and `AudioReverbType.ktv` simultaneously.