@tencent-rtc/mcp 1.4.7 → 1.6.0

package/resource/{doc → knowledge}/livekit/core-sdk/live/flutter/live-co-guest-interaction.md

@@ -1,28 +1,28 @@
-**AtomicXCore** provided the [CoGuestStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) module, specialized to manage the complete business process of audience mic connection. Developers do not need to worry about complex state synchronization and signaling interaction, just call a few simple methods to add powerful audio-video interaction between audience and Anchor to your live stream.
+**AtomicXCore** provided the [CoGuestStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) module, specialized to manage the complete business process of audience mic connection. Developers do not need to handle complex state synchronization or signaling interactions; by simply calling a few straightforward methods, you can add powerful audience-host audio and video interaction capabilities to your live streaming experience.
 
-## Core Scenario
+## Core Scenarios
 
-`CoGuestStore` supports the following two most mainstream microphone-connected scenarios:
-- **Audience request to speak**: The audience proactively initiate mic connection request, and the Anchor can grant or reject after receiving the request.
+`CoGuestStore` supports the two most common guest interaction scenarios:
+- **Audience requests to join as a guest**: The audience member actively initiates a request to join. The host receives the request and can choose to accept or reject it.
 
-- **Anchor invitation to speak**: The Anchor can proactively initiate mic connection to any audience in the live streaming room.
+- **Host invites audience to join as a guest**: The host can proactively invite any audience member in the live room to join as a guest.
 
 ## Implementation Steps
 
-### Step 1: Integrating the Component
+### Step 1: Integrate the Component
 
-Refer to Quick Access for seamless integration with **AtomicXCore** and complete **LiveCoreWidget** access.
+Refer to Quick Start to integrate `AtomicXCore` and `LiveCoreWidget`.
 
-After integration, start implementing the co-anchoring function.
+Once integration is complete, proceed to implement the guest interaction feature.
 
-### Step 2: Implementing Audience Request to Speak
+### Step 2: Implement Audience Request to Join as Guest
 
-#### Client Implementation
+**Audience Side Implementation**
 
 As an audience member, your core task is to **initiate application, receive results** and **become a listener**.
-1. **Initiate mic connection**
+1. **Initiate a guest request**
 
-   When the user clicks the "apply for mic connection" button on the interface, call the `applyForSeat` method.
+   When the user clicks the **Request to Join** button in the UI, call the `applyForSeat` method.
 
    ``` java
    import 'package:atomic_x_core/atomicxcore.dart';
@@ -45,9 +45,9 @@ As an audience member, your core task is to **initiate application, receive resu
        }
    }
    ```
-2. **Listen to the anchor's response**
+2. **Listen for host response**
 
-   By adding a listener through `addGuestListener`, you can receive the anchor's processing result.
+        Add a listener using `addGuestListener` to receive the host’s response.
 
    ``` java
    late GuestListener _guestListener;
@@ -85,9 +85,9 @@ As an audience member, your core task is to **initiate application, receive resu
        super.dispose();
    }
    ```
-3. **Leave the mic**
+3. **Leave the guest seat**
 
-   When a mic-connecting audience wants to end the interaction, call the `disconnect` method to return to general audience status.
+   When a guest wants to end the interaction, call the `disconnect` method to return to the regular audience state.
 
    ``` java
    // User clicks "leave mic" button
@@ -100,9 +100,9 @@ As an audience member, your core task is to **initiate application, receive resu
        }
    }
    ```
-4. **(Optional) Cancel application**
+4. **(Optional) Cancel the request**
 
-   If the audience wants to withdraw the application before anchor processing, they can call the API `cancelApplication`.
+        If the audience wants to withdraw the request before the host processes it, call `cancelApplication`.
 
    ``` java
    // While waiting, the user clicks "Cancel Application"
@@ -116,10 +116,11 @@ As an audience member, your core task is to **initiate application, receive resu
    }
    ```
 
-#### Anchor Implementation
+   **Host Side Implementation**
 
-As an Anchor, your core task is to **receive applications, show the Application List** and **process applications**.
-1. **Listen for new mic connection requests**
+   As a host, your core tasks are to receive requests, display the request list, and process requests.
+
+1. **Listen for new guest requests**
 
    By adding a listener through `addHostListener`, you can receive immediate notification when a new audience applies and get prompted.
 
@@ -154,9 +155,9 @@ As an Anchor, your core task is to **receive applications, show the Application
        super.dispose();
    }
    ```
-2. **Show application list**
+2. **Display the request list**
 
-   `CoGuestStore`'s `coGuestState` maintains the current applicant list in real time. You can listen to it to update your UI.
+   The `coGuestState` in `CoGuestStore` maintains the current list of applicants in real time. You can listen to it to update your UI.
 
    ``` java
    // Subscription status update
@@ -179,7 +180,7 @@ As an Anchor, your core task is to **receive applications, show the Application
        super.dispose();
    }
    ```
-3. **Handle mic connection request**
+3. **Process guest requests**
 
    When you select an audience from the list and click "Grant" or "Reject", call the appropriate method.
 
@@ -201,12 +202,12 @@ As an Anchor, your core task is to **receive applications, show the Application
    }
    ```
 
-### Step 3: Implementing Anchor Invitation to Speak
+### Step 3: Host Invites Audience to Join as Guest
 
-#### Anchor Implementation
-1. **Initiate invitation to audience**
+**Host Side Implementation**
+1. I**nvite an audience member**
 
-   When the Anchor selects someone from the audience list and clicks "invite to mic connection", call the `inviteToSeat` method.
+   When the host selects someone from the audience list and clicks “**Invite to Join**”, call the `inviteToSeat` method.
 
    ``` java
    // Anchor selects audience and initiates invitation
@@ -224,9 +225,9 @@ As an Anchor, your core task is to **receive applications, show the Application
        }
    }
    ```
-2. **Listen to the audience response**
+2. **Listen for audience response**
 
-   Listen to the invitation event response via `HostListener`.
+   Use `HostListener` to listen for invitation response events.
 
    ``` java
    // Callback configured in HostListener
@@ -240,10 +241,11 @@ As an Anchor, your core task is to **receive applications, show the Application
    );
    ```
 
-#### Client Implementation
-1. **Receive the anchor's invitation**
+   **Audience Side Implementation**
+
+1. **Receive host invitation**
 
-   Listen to the invitation event via `GuestListener`.
+   Listen for the invitation events via `GuestListener`.
 
    ``` java
    // Callback configured in GuestListener
@@ -278,19 +280,19 @@ As an Anchor, your core task is to **receive applications, show the Application
    }
    ```
 
-### Execution Effect
+### Feature Demo
 
-After integrating the above feature implementation, perform a co-streaming operation using two audiences and an Anchor separately. Audience A turns on the camera and microphone simultaneously, while Audience B turns on microphone only. The execution effect is as follows. You can refer to the next chapter Refine UI Details to customize your desired UI logic.
+After integrating the above functionality, test guest interaction using two audience members and a host. Audience A turns on both camera and microphone, while audience B only turns on the microphone. The resulting effect is shown below. You can refer to the next section to further customize your UI logic.
 
 ## Refine UI Details
 
-You can use the "slot" capacity provided by the `VideoWidgetBuilder` parameter of `LiveCoreWidget` to add custom views on the video stream image of audience co-broadcasting, for displaying Nickname, avatar information, etc., or offer placeholder images when they turn camera off, to optimize visual experience.
+You can leverage the slot capability provided by the `VideoWidgetBuilder` parameter of `LiveCoreWidget` to add custom views on top of the guest video streams. This allows you to display nicknames, avatars, and other information, or provide placeholder images when the camera is off, enhancing the overall visual experience.
 
-### Implementing Nickname Display on Video Stream Image
+### Displaying Nicknames on Video Streams
 
-#### **Effect**
+**Demo Effect**
 
-#### **Implementation Method**
+#### **Implementation **Steps
 - **Step 1**: Create a foreground view (**CustomSeatForegroundView**) used for displaying user information above the video stream.
 
    ``` java
@@ -461,32 +463,33 @@ You can use the "slot" capacity provided by the `VideoWidgetBuilder` parameter o
    ```
 
 #### **Parameter description:**
-| **Parameter** | **Type** | **Note** |
+| <strong>Parameter</strong> | <strong>Type</strong> | <strong>Note</strong> |
 | --- | --- | --- |
-| `seatFullInfo` | `SeatFullInfo` | Seat information object, containing the Anchor's detailed information. |
-| `seatFullInfo.userInfo.userId` | `String` | Anchor's user ID. |
-| `seatFullInfo.userInfo.userName` | `String` | On-mic user's nickname. |
-| `seatFullInfo.userInfo.avatarUrl` | `String` | On-mic user's profile photo URL. |
-| `viewLayer` | `ViewLayer` | View hierarchy enumeration.<br>- `ViewLayer.foreground` represents the pendant view, always displayed on top of the video image.<br>- `ViewLayer.background` represents the background pendant view, located in the lower layer of the foreground view. It is displayed only when the corresponding user has no video stream (for example, when the camera is not turned on), usually used for displaying the default avatar or placeholder image of the user. |
+| <code>seatFullInfo</code> | <code>SeatFullInfo</code> | Seat information object, containing the Anchor's detailed information. |
+| <code>seatFullInfo.userInfo.userId</code> | <code>String</code> | Anchor's user ID. |
+| <code>seatFullInfo.userInfo.userName</code> | <code>String</code> | On-mic user's nickname. |
+| <code>seatFullInfo.userInfo.avatarUrl</code> | <code>String</code> | On-mic user's profile photo URL. |
+| <code>viewLayer</code> | <code>ViewLayer</code> | View layer enumeration:<br>- <code>ViewLayer.foreground</code> represents the pendant view, always displayed on top of the video image.<br>- <code>ViewLayer.background</code> means the background widget, below the foreground layer, only displayed when the user has no video stream (e.g., camera is off), usually used to show the user’s default avatar or placeholder image. |
 
-## API documentation
+## API Documentation
 
-For details about ALL public interfaces, properties, and methods of [CoGuestStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) and its related classes, see the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Stores used in this guide are as follows:
-| **Store/Component** | **Feature Description** | **API Reference** |
-| --- | --- | --- |
-| LiveCoreWidget | Core view component for live video stream display and interaction: Responsible for stream rendering and view widget processing, supporting scenarios such as Anchor live streaming, audience co-broadcasting, and cross-room connection with other anchors. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html) |
-| LiveCoreController | Controller for LiveCoreWidget: Used to set the live stream ID, control the preview, and perform other operations. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html) |
-| VideoWidgetBuilder | Video view adapter: Used for custom pendant views in scenarios such as mic-connecting audience, cross-room connection with other anchors, and PK. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/VideoWidgetBuilder-class.html) |
-| DeviceStore | Audio/Video device control: Microphone (on/off, volume), camera (on/off, switchover, video quality), screen sharing, and real-time monitoring of device status. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) |
-| CoGuestStore | Audience co-broadcasting management: Join microphone application/invite/grant/reject, attendee permission control (microphone/camera), state synchronization. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) |
+For details about all public interfaces, properties, and methods of [CoGuestStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) and its related classes, see the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Stores used in this guide are as follows:
+
+|Store/Component|Feature Description|API Documentation|
+|---------|---------|---------|
+|LiveCoreWidget|Core view component for live video stream display and interaction: responsible for video rendering and widget handling, supports host streaming, guest interaction, host connection, and other scenarios.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html)|
+|LiveCoreController|Controller for LiveCoreWidget: used to set the live ID, control preview, and other operations.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html)|
+|VideoWidgetBuilder|Video view adapter: used to customize video stream widgets for guest interaction, host connection, PK, and other scenarios.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/VideoWidgetBuilder-class.html)|
+|DeviceStore|Audio/video device control: microphone (on/off / volume), camera (on/off / switch / quality), screen sharing, real-time device status monitoring.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html)|
+|CoGuestStore|Guest interaction management: guest request/invite/accept/reject, guest member permissions (microphone/camera), state synchronization.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html)|
 
 ## FAQs
 
-### How to Manage the Lifecycle and Event of a Custom View Added Via `VideoWidgetBuilder`?
+### How do I manage the lifecycle and events of custom views added via VideoWidgetBuilder?
 
 **LiveCoreWidget** will automatically manage the addition and removal of views returned by the `coGuestWidgetBuilder` callback, so you don't need to handle them manually. If necessary to process user interaction (such as click events) in a custom view, just add corresponding event handling when creating the view.
 
-### `ViewLayer` What Are the Functions of the Parameter?
+### What is the purpose of the ViewLayer parameter?
 
 `ViewLayer` is used to distinguish between foreground and background widgets.
 - `ViewLayer.foreground`: The foreground layer, always displayed on top of the video image.

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

@@ -1,7 +1,8 @@
 `GiftStore` is a module in `AtomicXCore` specialized in managing the gift function of live streaming rooms. With it, you can build a complete gift system for your live stream application to achieve various revenue and interactive scenarios.
-| **Gift Panel** | **Barrage Gift** | **Full-Screen Gift** |
-| --- | --- | --- |
-|  |  |  |
+
+|**Gift Panel**|**Barrage Gift**|**Full-Screen Gift**|
+|---------|---------|---------|
+||||
 
 ## Core Features
 - **Gift List Retrieval**: Obtain the required data for the gift panel from the server, including gift categories and gift details.
@@ -13,17 +14,18 @@
 ## Core Concepts
 
 Before starting integration, let's learn about several core concepts related to `GiftStore` in the following table:
-| **Core Concepts** | **Type** | **Core Responsibilities and Description** |
-| --- | --- | --- |
-| [Gift](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/Gift-class.html) | `class` | Represents a specific gift data model. It contains the gift ID, name, icon address, animation resource URL and price (coins). |
-| [GiftCategory](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftCategory-class.html) | `class` | Represents a gift category, such as "popular" and "luxury". It contains the category name as well as the **Gift** list under this category. |
-| [GiftState](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftState-class.html) | `class` | Represents the current status of the gift module. Its core attribute `usableGifts` is a `ValueListenable<List<GiftCategory>>`, storing the complete gift list fetched from the server. |
-| [GiftListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftListener-class.html) | `class` | Gift event listener, receive gift giveaway event through the `onReceiveGift` callback. When anyone (including itself) sends a gift, all people in the room will receive this event. |
-| [GiftStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html) | `class` | This is the core management class for interacting with the gift function. Through it, you can fetch the gift list, send a gift, and receive gift events via `addGiftListener`. |
+
+|**Core Concepts**|**Type**|**Core Responsibilities and Description**|
+|---------|---------|---------|
+|[Gift](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/Gift-class.html)|`class`|Represents a specific gift data model. It contains the gift ID, name, icon address, animation resource URL and price (coins).|
+|[GiftCategory](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftCategory-class.html)|`class`|Represents a gift category, such as "popular" and "luxury". It contains the category name as well as the **Gift** list under this category.|
+|[GiftState](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftState-class.html)|`class`|Represents the current status of the gift module. Its core attribute `usableGifts` is a `ValueListenable<List<GiftCategory>>`, storing the complete gift list fetched from the server.|
+|[GiftListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftListener-class.html)|`class`|Gift event listener, receive gift giveaway event through the `onReceiveGift` callback. When anyone (including itself) sends a gift, all people in the room will receive this event.|
+|[GiftStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html)|`class`|This is the core management class for interacting with the gift function. Through it, you can fetch the gift list, send a gift, and receive gift events via `addGiftListener`.|
 
 ## Implementation Steps
 
-### Step 1: Integrating the Component
+### Step 1: Integrate the Component
 
 > **Note：**
 >
@@ -31,15 +33,13 @@ Before starting integration, let's learn about several core concepts related to
 > To use the gifting system, activate either the **Free Trial,** or **Pro **edition. The number of configurable gifts depends on the selected package. For details, see the **Gift System** section in Feature and Billing Description and choose the package that fits your needs.
 >
 
-- **Live streaming**: Refer to Quick Access for seamless integration with **AtomicXCore** and access completed.
+- **Live streaming**: Refer to Quick Integration for seamless integration with **AtomicXCore**.
 
-- **Voice chat room**: Refer to Quick Access for seamless integration with **AtomicXCore** and access completed.
+- **Voice chat room**: Refer to Quick Integration for seamless integration with **AtomicXCore**.
 
 ### Step 2: Initialize and Listen for Gift Events
 
 Get the `GiftStore` instance and set a listener for receiving gifts and list update events.
-
-#### Implementation Approach
 1. **Get instance**: Use `GiftStore.create(liveId)` to get the `GiftStore` instance bound to the current live streaming room.
 
 2. **Subscribe to events**: Add a gift event listener via `giftStore.addGiftListener(listener)`.
@@ -101,39 +101,37 @@ class GiftManager {
 ```
 
 #### Gift List Structure Parameter
-- `GiftCategory`**Parameter description**
-
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `categoryID` | `String` | Unique ID of the gift category. |
-| `name` | `String` | Display name of the gift category. |
-| `desc` | `String` | Description of the gift category. |
-| `extensionInfo` | `Map<String, String>` | Extended information field. |
-| `giftList` | `List<Gift>` | Array of Gift objects under this category. |
-
-- `Gift`**Parameter description**
-
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `giftID` | `String` | Unique ID of the gift. |
-| `name` | `String` | Display name of the gift. |
-| `desc` | `String` | Description of the gift. |
-| `iconURL` | `String` | Icon URL of the gift. |
-| `resourceURL` | `String` | Resource URL of the gift animation. |
-| `level` | `int` | Gift level. |
-| `coins` | `int` | Gift price. |
-| `extensionInfo` | `Map<String, String>` | Extended information field. |
+- `GiftCategory`**Parameters**
+
+   |**Parameter**|**Type**|**Description**|
+   |---------|---------|---------|
+   |`categoryID`|`String`|Unique ID of the gift category.|
+   |`name`|`String`|Display name of the gift category.|
+   |`desc`|`String`|Description of the gift category.|
+   |`extensionInfo`|`Map<String, String>`|Extended information field.|
+   |`giftList`|`List<Gift>`|Array of Gift objects under this category.|
+
+- `Gift`**Parameters**
+
+   |**Parameter**|**Type**|**Description**|
+   |---------|---------|---------|
+   |`giftID`|`String`|Unique ID of the gift.|
+   |`name`|`String`|Display name of the gift.|
+   |`desc`|`String`|Description of the gift.|
+   |`iconURL`|`String`|Icon URL of the gift.|
+   |`resourceURL`|`String`|Resource URL of the gift animation.|
+   |`level`|`int`|Gift level.|
+   |`coins`|`int`|Gift price.|
+   |`extensionInfo`|`Map<String, String>`|Extended information.|
 
 ### Step 3: Obtain the Gift List
 
 Call the `refreshUsableGifts` method to fetch gift data from the server.
-
-#### Implementation Approach
 1. **API call**: Call `giftStore.refreshUsableGifts()` at the appropriate timing (such as after entering the live room).
 
 2. **Processing result**: Optionally process the returned results to fetch the pull results.
 
-3. **Data reception**: After the update, the gift list is automatically received by listening to `giftStore.giftState.usableGifts` in procedure 2.
+3. **Receive Data**: After the update, the gift list is automatically received by listening to `giftStore.giftState.usableGifts` in Step 2.
 
 #### Sample code:
 ``` java
@@ -151,16 +149,14 @@ extension GiftManagerFetch on GiftManager {
 }
 ```
 
-### Step 4: Sending a Gift
+### Step 4: Send a Gift
 
 When a user selects a gift in the gift panel and clicks send, call the `sendGift` API to send the gift.
-
-#### Implementation Approach
-1. **Get parameter**: Obtain the giftID selected by the user and the number of messages sent (count) from the UI.
+1. **Get parameter**: Obtain the `giftID` selected by the user and the number of messages sent (`count`) from the UI.
 
 2. **API call**: Call `giftStore.sendGift(giftID:, count:)`.
 
-3. **Processing result**: Handle failure cases (such as insufficient account balance notification) in the returned result. UI updates (animation, bullet screen) after successful sending should be event-driven by `onReceiveGift`.
+3. **Handle result**: Handle failure cases (such as insufficient account balance notification) in the returned result. UI updates (animation, bullet screen) after successful sending should be event-driven by `onReceiveGift`.
 
 #### Sample code:
 ``` java
@@ -179,21 +175,20 @@ extension GiftManagerSend on GiftManager {
 }
 ```
 
-#### `SendGift` API Parameter
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `giftID` | `String` | Unique ID of the gift to send. |
-| `count` | `int` | The number of sent. |
+#### `SendGift` API Parameters
 
-## Advanced Features
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`giftID`|`String`|Unique ID of the gift to send.|
+|`count`|`int`|The number of sent.|
 
-`GiftStore` feature heavily depends on your business backend service. This chapter will guide you on how to build a feature-rich, outstanding experience interactive system through server configuration and client implementation.
+## Advanced Usage
 
-### **Gift Material Configuration**
+`GiftStore` feature heavily depends on your business backend service. This chapter will guide you on how to build a feature-rich, outstanding experience interactive system through server configuration and client implementation.
 
-You need to customize the available gift type, category, name, icon, price, and animated effects in the live streaming room to meet operational needs and brand feature.
+### **Gift **Asset Configuration
 
-#### Implementation
+Customize your live room's available gifts, categories, names, icons, prices, and animation effects to fit your operational and branding needs.
 1. **Server-Side Configuration**: Use the LiveKit server REST API to manage gift information, categories, and multi-language support. See the Gift Configuration Guide.
 
 2. **Client Fetch**: On the client, call `refreshUsableGifts` to retrieve configuration data.
@@ -203,30 +198,30 @@ You need to customize the available gift type, category, name, icon, price, and
 #### Configuration Sequence Diagram
 
 #### Related REST API Interfaces Overview
-| **Interface Category** | **Interface** | **Request Example** |
+| <strong>Interface Category</strong> | <strong>Interface</strong> | <strong>Request Example</strong> |
 | --- | --- | --- |
-| **​Gift Management** | Add Gift Information | Example |
-| Delete Gift Information | Example |  |
-| Query Gift Information | Example |  |
-| **Gift Category Management** | Add Gift Category Information | Example |
-| Delete Specific Gift Category Information | Example |  |
-| Get Specific Gift Category Information | Example |  |
-| **Gift Relationship Management** | Add Relationship between a Specific Gift Category and Gift | Example |
-| Delete Relationship between a Specific Gift Category and Gift | Example |  |
-| Get Gift Relationships under a Specific Gift Category | Example |  |
-| **Gift Multi-language Management** | Add Gift Multi-language Information | Example |
-| Delete Specific Gift Multi-language Information | Example |  |
-| Get Gift Multi-language Information | Example |  |
-| Add Gift Category Multi-language Information | Example |  |
-| Delete Specific Gift Category Multi-language Information | Example |  |
-| Get Gift Category Multi-language Information | Example |  |
-
-### Billing and Gift Sending Process
+| <strong>​Gift Management</strong> | Add Gift Information. | Example |
+| Delete Gift Information. | Example |  |
+| Query Gift Information. | Example |  |
+| <strong>Gift Category Management</strong> | Add Gift Category Information. | Example |
+| Delete Specific Gift Category Information. | Example |  |
+| Get Specific Gift Category Information. | Example |  |
+| <strong>Gift Relationship Management</strong> | Add Relationship between a Specific Gift Category and Gift. | Example |
+| Delete Relationship between a Specific Gift Category and Gift. | Example |  |
+| Get Gift Relationships under a Specific Gift Category. | Example |  |
+| <strong>Gift Multi-language Management</strong> | Add Gift Multi-language Information. | Example |
+| Delete Specific Gift Multi-language Information. | Example |  |
+| Get Gift Multi-language Information. | Example |  |
+| Add Gift Category Multi-language Information. | Example |  |
+| Delete Specific Gift Category Multi-language Information. | Example |  |
+| Get Gift Category Multi-language Information. | Example |  |
+
+### Billing and Gift Deduction Workflow
 
 When the audience sends gifts, ensure sufficient account balance and complete the actual deduction before triggering the gift effect playback and broadcast.
 
 #### Workflow
-1. **Backend Callback Configuration**: Configure your billing system's callback URL in the LiveKit backend. See Callback Configuration Documentation.
+1. **Configure Backend Webhook**: Configure your billing system's callback URL in the LiveKit backend. See Callback Configuration Documentation.
 
 2. **Client Request**: The client calls `sendGift`.
 
@@ -236,29 +231,31 @@ When the audience sends gifts, ensure sufficient account balance and complete th
 
 #### Call Flow
 
-#### Related REST API Interfaces Overview
-| **Interface** | **Description** | **Request Example** |
-| --- | --- | --- |
-| **Callback Configuration - Callback before sending a gift** | Pre-gifting validation hook.<br>Allows your backend to intercept gift requests to perform necessary checks (e.g., sufficient balance, risk control) before the gift is processed. | Example |
+#### REST API Overview
 
-### Play Full-Screen Gift Animation
+|**Interface**|**Description**|**Request Example**|
+|---------|---------|---------|
+|**Webhook Configuration - Pre-send Gift Webhook**|Allows your backend to validate and approve gift sending (e.g., pre-send checks).|Example|
 
-When a user (including itself) sends luxury gifts such as "rocket" or "carnival" in the live streaming room, play a cool gift animation (for example, SVGA animation) in full-screen playback to create a lively communication environment.
+### Play Full-Screen Gift Animations
 
-#### Implementation
+When a user sends a "Rocket", "Carnival", or other luxury gift, display a full-screen animation (e.g., SVGA) to boost engagement.
+
+#### Implementation Steps
 
 `AtomicXCore` itself does not include a gift animation player. You need to select and integrate a third-party library based on business requirements. The following is a comparison of two solutions:
-| **Comparison Item** | **Basic Solution (Svgaplayer_flutter)** | **Advanced Plan (TCEffectPlayerKit)** |
-| --- | --- | --- |
-| Billing | Free (open-source library) | Paid (License purchase required), please see [Payment Guide](https://trtc.io/document/69949?product=beautyar&menulabel=core%20sdk&platform=android#X-Series-Capabilities) |
-| Integration Method | Manual integration of the [svgaplayer_flutter](https://pub.dev/packages/svgaplayer_flutter) library is required. | Additional integration of the [flutter_effect_player](https://github.com/Tencent-RTC/EffectPlayer_Flutter) library and authentication are required. |
-| Animation Format Support | SVGA only | SVGA, PAG, WebP, Lottie, MP4, and other formats |
-| Performance | Recommend SVGA files ≤ 10MB | Support larger animation files, better performance for complex effects, multi-animation concurrency, and low-end devices |
-| Recommended scenarios | Gift animation format is unified as SVGA with controllable file size | Support multiple animation formats or higher performance/compatibility requirements |
 
-This section demonstrates the basic solution. If you select the advanced plan, refer to [EffectPlayer Flutter integration guide](https://trtc.io/document/73975?product=beautyar&menulabel=core%20sdk&platform=flutter).
+|**Comparison Item**|**Basic Solution (Svgaplayer_flutter)**|**Advanced Plan (TCEffectPlayerKit)**|
+|---------|---------|---------|
+|Billing|Free (open-source library)|Paid (License purchase required), please see [Payment Guide](https://trtc.io/document/69949)|
+|Integration Method|Manual integration of the [svgaplayer_flutter](https://pub.dev/packages/svgaplayer_flutter) library is required.|Additional integration of the [flutter_effect_player](https://github.com/Tencent-RTC/EffectPlayer_Flutter) library and authentication are required.|
+|Animation Format Support|SVGA only|SVGA, PAG, WebP, Lottie, MP4, and other formats|
+|Performance|Recommend SVGA files ≤ 10MB|Support larger animation files, better performance for complex effects, multi-animation concurrency, and low-end devices|
+|Recommended scenarios|Gift animation format is unified as SVGA with controllable file size|Support multiple animation formats or higher performance/compatibility requirements|
+
+This section demonstrates the basic solution. If you select the advanced plan, refer to [EffectPlayer Flutter integration guide](https://trtc.io/document/73975).
 
-#### Basic Solution Implementation: Use Svgaplayer_flutter
+#### Basic Solution: Use Svgaplayer_flutter
 1. **Integrate svgaplayer_flutter**: In your `pubspec.yaml` file, add dependency and run `flutter pub get`.
 
    ``` yaml
@@ -267,9 +264,9 @@ This section demonstrates the basic solution. If you select the advanced plan, r
    ```
 2. **Listen for gift events**: Add a listener via `GiftStore`'s `addGiftListener`.
 
-3. **Parse and play**: When the `onReceiveGift` event is received, check if `gift.resourceURL` is valid and points to an SVGA file. If so, use `SVGAAnimationController` to play the animation.
+3. **Parse and play animation**: When the `onReceiveGift` event is received, check if `gift.resourceURL` is valid and points to an SVGA file. If so, use `SVGAAnimationController` to play the animation.
 
-#### Sample Code
+#### Sample Code:
 ``` java
 import 'package:flutter/material.dart';
 import 'package:atomic_x_core/atomicxcore.dart';
@@ -349,11 +346,11 @@ class _LiveRoomWidgetState extends State<LiveRoomWidget> with SingleTickerProvid
 }
 ```
 
-### Show Gift Giveaway Messages in the Bullet Screen Area
+#### Display Gift Messages in Barrage Area
 
 When a user sends a gift, it not only plays the animation but also displays a system message in the on-screen comment area, such as "[Nickname] sent [gift name] x [quantity]", so all audience can see.
 
-#### Implementation Method
+#### Implementation Steps
 1. **Listen for events**: Add a listener via `giftStore.addGiftListener`.
 
 2. **Obtain information**: After the `onReceiveGift` event is received, extract the sender, gift, and count.
@@ -364,7 +361,7 @@ When a user sends a gift, it not only plays the animation but also displays a sy
 
 5. **Local insertion**: Call `barrageStore.appendLocalTip(giftTip)` to insert the message into the local list.
 
-#### Sample Code
+#### Sample Code:
 ``` java
 // In LiveRoomManager or similar top-level managers
 void _setupGiftToBarrageFlow() {
@@ -393,34 +390,35 @@ void _setupGiftToBarrageFlow() {
 ## API documentation
 
 For detailed information about all public interfaces, attributes, and methods of [GiftStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html) and its related classes, see the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Stores used in this guide are as follows:
-| **Store/Component** | **Feature Description** | **API Reference** |
-| --- | --- | --- |
-| **GiftStore** | Gift interaction: Get gift list, send/receive gifts, listen to gift events (including sender, gift details). | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-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/BarrageStore-class.html) |
+
+|**Store/Component**|**Feature Description**|**API Reference**|
+|---------|---------|---------|
+|**GiftStore**|Gift interaction: Get gift list, send/receive gifts, listen to gift events (including sender, gift details).|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-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/BarrageStore-class.html)|
 
 ## FAQs
 
-### `GiftStore` Gift List Is Empty. What Should Be Done?
+### Why is the gift list in GiftStore empty?
 
 You must actively call `refreshUsableGifts()` to fetch gift data from your backend. These gift data need to be configured in your backend via server-side REST API.
 
-### How to Achieve Multilingual Gift Display (Such As Chinese, English)
+### How do I show gifts in multiple languages (e.g., Chinese, English)?
 
 `GiftStore` provides the `setLanguage(String language)` API. You can call this method before `refreshUsableGifts`, input the target language code (such as "en" or "zh-CN"). The server will return the gift name and description in the corresponding language based on this language code.
 
-### I Called SendGift to Send the Gift, Why Did the Gift Animation Repeat Playback Twice?
+### Why does the gift animation play twice after sending a gift?
 
 `onReceiveGift` is a broadcast to all members in the room (including the sender). If you perform a UI operation in the success callback of `sendGift`, and simultaneously execute the same UI operation in the `onReceiveGift` callback, it can lead to duplication.
 - **Best practice**: UI updates (such as playing animation, bullet screen notification) should only be handled in the callback of the `onReceiveGift` event. The returned results of `sendGift` are only used to process the logic of sending failure (such as prompting the user "sending failure" or "insufficient balance").
 
-### Where Is the Gift Charge Logic Implemented?
+### Where is the gift deduction logic handled?
 
 The gift charge logic is fully handled by your self-built billing system. `AtomicXCore` connects with your billing system through a backend callback mechanism. The client calls `sendGift` to trigger the callback. After your backend service completes the charge, it returns the result to the `AtomicXCore` backend, thereby determining whether to broadcast the gift event.
 
-### Will Gift Sending Notifications Be Muted or Blocked by Frequency Control?
+### Are gift notifications affected by mute or message rate limiting?
 
 No. Gift sending notifications (`onReceiveGift` event) are not affected by muting or message frequency control, ensuring reliable delivery.
 
-### What to Do About Playback Lag in Gift Animation
+### What if gift animation playback is laggy?
 
 Please check your SVGA file size. Player SDKs recommend not exceeding 10MB. If the file is too large or the animation is complex, you can consider seamless integration with the advanced effect player provided by TUILiveKit to get better performance.