@tencent-rtc/mcp 1.4.7 → 1.6.0

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

@@ -12,12 +12,12 @@
 - **Room Management**: The host or administrator can remove specific viewers from the live room.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibilities & Description** |
+| <strong>Core Concept</strong> | <strong>Type</strong> | <strong>Core Responsibilities & Description</strong> |
 | --- | --- | --- |
-| `LiveUserInfo` | `class` | - Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL. |
-| `LiveAudienceState` | `struct` | - State container for the audience module.<br>- Exposes `audienceList` (StateFlow) for the real-time user list and `audienceCount` for the total viewer count. |
-| `LiveAudienceEvent` | `enum` | - Event listener for audience changes.<br>- Provides callbacks like `.onAudienceJoined` and` .onAudienceLeft` to handle incremental list updates. |
-| `LiveAudienceStore` | `class` | - Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events. |
+| <code>LiveUserInfo</code> | <code>class</code> | - Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL. |
+| <code>LiveAudienceState</code> | <code>struct</code> | - State container for the audience module.<br>- Exposes <code>audienceList</code> (StateFlow) for the real-time user list and <code>audienceCount</code> for the total viewer count. |
+| <code>LiveAudienceEvent</code> | <code>enum</code> | - Event listener for audience changes.<br>- Provides callbacks like <code>.onAudienceJoined</code> and<code> .onAudienceLeft</code> to handle incremental list updates. |
+| <code>LiveAudienceStore</code> | <code>class</code> | - Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events. |
 
 ## Implementation
 
@@ -235,11 +235,12 @@ When a new audience member enters the live room, a welcome message is automatica
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) and its related classes, refer to the official API documentation included with the [AtomicX Core](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) 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-to-host connection. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview) |
-| LiveAudienceStore | Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) |
-| BarrageStore | Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) |
+
+|**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-to-host connection.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview)|
+|LiveAudienceStore|Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore)|
+|BarrageStore|Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)|
 
 ## FAQs
 

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

@@ -12,14 +12,15 @@ By combining `AudioEffectStore` and `DeviceStore`, you can implement the followi
 - **Reverb Effects**: Simulate different acoustic environments, such as KTV, metallic, deep, bright, and others.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibility & Description** |
-| --- | --- | --- |
-| `AudioChangerType` | `enum` | Enumerates available voice changing effects, such as "child", "man", etc. |
-| `AudioReverbType` | `enum` | Enumerates available reverb effects, such as "ktv", "hall", etc. |
-| `AudioEffectState` | `struct` | Represents the current state of the audio effect module, typically used for UI rendering. Includes voice changing effect state, reverb state, ear monitoring enabled state, and ear monitor volume. |
-| `AudioEffectStore` | `class` | Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
-| `DeviceState` | `struct` | Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status. |
-| `DeviceStore` | `class` | Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
+
+|**Core Concept**|**Type**|**Core Responsibility & Description**|
+|---------|---------|---------|
+|`AudioChangerType`|`enum`|Enumerates available voice changing effects, such as "child", "man", etc.|
+|`AudioReverbType`|`enum`|Enumerates available reverb effects, such as "ktv", "hall", etc.|
+|`AudioEffectState`|`struct`|Represents the current state of the audio effect module, typically used for UI rendering. Includes voice changing effect state, reverb state, ear monitoring enabled state, and ear monitor volume.|
+|`AudioEffectStore`|`class`|Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.|
+|`DeviceState`|`struct`|Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status.|
+|`DeviceStore`|`class`|Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.|
 
 ## Implementation
 
@@ -80,14 +81,14 @@ audioEffectStore.state
 ```
 
 #### setVoiceEarMonitorEnable Parameters
-| **Parameter Name** | **Type** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `enable` | `Bool` | Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable |
+| <code>enable</code> | <code>Bool</code> | Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable |
 
 #### setVoiceEarMonitorVolume Parameters
-| **Parameter Name** | **Type** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `volume` | `Int` | Ear monitor volume.<br>- Value range: [0, 150]<br>- Default: 100 |
+| <code>volume</code> | <code>Int</code> | Ear monitor volume.<br>- Value range: [0, 150]<br>- Default: 100 |
 
 ### Step 4: Implement Microphone Volume Adjustment
 
@@ -115,9 +116,9 @@ deviceStore.state
 ```
 
 #### setCaptureVolume Parameters
-| **Parameter Name** | **Type** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Description</strong> |
 | --- | --- | --- |
-| `volume` | `Int` | Microphone (capture) volume.<br>- Value range: [0, 150]<br>- Default: 100 |
+| <code>volume</code> | <code>Int</code> | Microphone (capture) volume.<br>- Value range: [0, 150]<br>- Default: 100 |
 
 ### Step 5: Implement Voice Effects
 
@@ -132,9 +133,10 @@ audioEffectStore.setAudioChangerType(type: .none)
 ```
 
 #### setAudioChangerType Parameters
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `type` | `AudioChangerType` | Voice changer effect enumeration. |
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`type`|`AudioChangerType`|Voice changer effect enumeration.|
 
 ### Step 6: Implement Reverb Effects
 
@@ -147,9 +149,10 @@ audioEffectStore.setAudioReverbType(type: .none)
 ```
 
 #### setAudioReverbType Parameters
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `type` | `AudioReverbType` | Reverb effect enumeration. |
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`type`|`AudioReverbType`|Reverb effect enumeration.|
 
 ### Step 7: Reset Audio Effect Settings
 
@@ -176,10 +179,11 @@ Reset audio effect settings in the following scenarios:
 ## API Documentation
 
 For detailed information on all public interfaces and properties of [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/audioeffectstore), [DeviceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/devicestore), and related classes, refer to the official API documentation for the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework.
-| **Store/Component** | **Description** | **API Reference** |
-| --- | --- | --- |
-| DeviceStore | Controls audio/video devices: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, and real-time device status monitoring. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/devicestore) |
-| AudioEffectStore | Audio effects: voice changing (child/male), reverb (KTV, etc.), ear monitoring adjustment, and real-time effect switching. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/audioeffectstore) |
+
+|**Store/Component**|**Description**|**API Reference**|
+|---------|---------|---------|
+|DeviceStore|Controls audio/video devices: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, and real-time device status monitoring.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/devicestore)|
+|AudioEffectStore|Audio effects: voice changing (child/male), reverb (KTV, etc.), ear monitoring adjustment, and real-time effect switching.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/audioeffectstore)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/voice/ios/voice-barrage.md

@@ -12,11 +12,12 @@ This document provides a comprehensive guide for iOS developers to quickly integ
 - Inserting system tips into the local message list (for example, "Welcome XX to the live room").
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibility & Description** |
-| --- | --- | --- |
-| [Barrage](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barrage) | struct | Represents the data model for a single barrage message. Contains all essential information such as sender (sender), message content (textContent or data), message type (messageType), and more. |
-| [BarrageState](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestate) | struct | Represents the current state of the barrage module. The main property, messageList, is an array of [Barrage] storing all barrage messages in chronological order for the current live room. This serves as the data source for UI rendering. |
-| [BarrageStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) | class | The core management class for barrage functionality. Use it to send messages (sendTextMessage, sendCustomMessage), and subscribe to its state property to receive all barrage message updates. |
+
+|**Core Concept**|**Type**|**Core Responsibility & Description**|
+|---------|---------|---------|
+|[Barrage](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barrage)|struct|Represents the data model for a single barrage message. Contains all essential information such as sender (sender), message content (textContent or data), message type (messageType), and more.|
+|[BarrageState](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestate)|struct|Represents the current state of the barrage module. The main property, messageList, is an array of [Barrage] storing all barrage messages in chronological order for the current live room. This serves as the data source for UI rendering.|
+|[BarrageStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)|class|The core management class for barrage functionality. Use it to send messages (sendTextMessage, sendCustomMessage), and subscribe to its state property to receive all barrage message updates.|
 
 ## Implementation
 
@@ -91,11 +92,12 @@ extension BarrageManager {
 ```
 
 #### API Parameters
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `text` | `String` | The text content to send. |
-| `extensionInfo` | `[String: String]?` | Additional extension information for business customization. |
-| `completion` | `CompletionClosure?` | Callback after sending is complete, containing the success or failure result. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`text`|`String`|The text content to send.|
+|`extensionInfo`|`[String: String]?`|Additional extension information for business customization.|
+|`completion`|`CompletionClosure?`|Callback after sending is complete, containing the success or failure result.|
 
 ### Step 4: Send Custom Barrage
 
@@ -129,11 +131,12 @@ extension BarrageManager {
 ```
 
 #### API Parameters
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `businessId` | `String` | Unique business identifier, e.g., "live_gift", used by the receiver to distinguish different custom messages. |
-| `data` | `String` | Business data, usually a JSON-formatted string. |
-| `completion` | `CompletionClosure?` | Callback after sending is complete. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`businessId`|`String`|Unique business identifier, e.g., "live_gift", used by the receiver to distinguish different custom messages.|
+|`data`|`String`|Business data, usually a JSON-formatted string.|
+|`completion`|`CompletionClosure?`|Callback after sending is complete.|
 
 ### Step 5: Insert Local Tip Message
 
@@ -155,9 +158,10 @@ extension BarrageManager {
 ```
 
 #### API Parameters
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| message | Barrage | The message object to insert locally. The SDK appends this message to the messageList in BarrageState. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|message|Barrage|The message object to insert locally. The SDK appends this message to the messageList in BarrageState.|
 
 ### Step 6: Manage User Speaking Permissions (Mute and Unmute)
 

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

@@ -270,9 +270,10 @@ seatStore.unmuteMicrophone(completion: nil) // Unmute
 ```
 
 #### unmuteMicrophone Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `completion` | `CompletionClosure?` | Callback after the operation completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`completion`|`CompletionClosure?`|Callback after the operation completes.|
 
 ### Host Remotely Controls On-Mic User’s Microphone
 
@@ -327,16 +328,18 @@ seatStore.liveSeatEventPublisher
 ```
 
 #### closeRemoteMicrophone Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `userID` | `String` | The userID of the target user. |
-| `completion` | `CompletionClosure?` | Callback after the request completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`userID`|`String`|The userID of the target user.|
+|`completion`|`CompletionClosure?`|Callback after the request completes.|
 
 #### openRemoteMicrophone Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `userID` | `String` | The userID of the target user. |
-| `completion` | `CompletionClosure?` | Callback after the request completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`userID`|`String`|The userID of the target user.|
+|`completion`|`CompletionClosure?`|Callback after the request completes.|
 
 ### Host Removes On-Mic User from the Seat
 
@@ -376,10 +379,11 @@ guestStore
 ```
 
 #### kickUserOutOfSeat Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `userID` | `String` | The userID of the user to be removed from the mic seat. |
-| `completion` | `CompletionClosure?` | Callback after the request completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`userID`|`String`|The userID of the user to be removed from the mic seat.|
+|`completion`|`CompletionClosure?`|Callback after the request completes.|
 
 ### Host Locks and Unlocks Mic Seats
 
@@ -408,16 +412,18 @@ seatStore.unlockSeat(seatIndex: 2) { result in
 ```
 
 #### lockSeat Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `seatIndex` | `Int` | Index of the seat to lock. |
-| `completion` | `CompletionClosure?` | Callback after the request completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`seatIndex`|`Int`|Index of the seat to lock.|
+|`completion`|`CompletionClosure?`|Callback after the request completes.|
 
 #### unlockSeat Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `seatIndex` | `Int` | Index of the seat to unlock. |
-| `completion` | `CompletionClosure?` | Callback after the request completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`seatIndex`|`Int`|Index of the seat to unlock.|
+|`completion`|`CompletionClosure?`|Callback after the request completes.|
 
 ### Move Mic Seats
 
@@ -442,20 +448,22 @@ seatStore.moveUserToSeat(userID: "userC",
 ```
 
 #### moveUserToSeat Parameters:
-| **Parameter** | **Type** | **Description** |
-| --- | --- | --- |
-| `userID` | `String` | The userID of the user to move. |
-| `targetIndex` | `Int` | Target seat index. |
-| `policy` | `MoveSeatPolicy?` | Seat movement policy if the target seat is occupied:<br>- `abortWhenOccupied`: Abort move if seat is occupied (default)<br>- `forceReplace`: Force replace the user on the target seat; replaced user will be removed<br>- `swapPosition`: Swap positions with the user on the target seat. |
-| `completion` | `CompletionClosure?` | Callback after the request completes. |
+
+|**Parameter**|**Type**|**Description**|
+|---------|---------|---------|
+|`userID`|`String`|The userID of the user to move.|
+|`targetIndex`|`Int`|Target seat index.|
+|`policy`|`MoveSeatPolicy?`|Seat movement policy if the target seat is occupied:<br>- `abortWhenOccupied`: Abort move if seat is occupied (default)<br>- `forceReplace`: Force replace the user on the target seat; replaced user will be removed<br>- `swapPosition`: Swap positions with the user on the target seat.|
+|`completion`|`CompletionClosure?`|Callback after the request completes.|
 
 ## API Documentation
 
 For detailed information about all public interfaces, properties, and methods of [CoGuestStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/cogueststore), [LiveSeatStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveseatstore), and related classes, refer to the official [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework API documentation. The relevant stores used in this guide are as follows:
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| CoGuestStore | Audience mic-link management: mic-link requests/invitations/accept/reject, member permission control (microphone/camera), state synchronization. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/cogueststore) |
-| LiveSeatStore | Mic seat management: mute/unmute, lock/unlock seats, remove users from mic, remote mic control, mic seat list state monitoring | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveseatstore) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|CoGuestStore|Audience mic-link management: mic-link requests/invitations/accept/reject, member permission control (microphone/camera), state synchronization.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/cogueststore)|
+|LiveSeatStore|Mic seat management: mute/unmute, lock/unlock seats, remove users from mic, remote mic control, mic seat list state monitoring|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveseatstore)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/voice/ios/voice-gift.md

@@ -1,7 +1,8 @@
 `GiftStore` is a dedicated module within **AtomicXCore** for managing live room gifting features. It enables you to build a complete gifting system for your live streaming application, supporting robust monetization and interactive experiences.
-| **Gift Panel** | **Barrage Gift** | **Full-Screen Gift** |
-| --- | --- | --- |
-|  |  |  |
+
+|**Gift Panel**|**Barrage Gift**|**Full-Screen Gift**|
+|---------|---------|---------|
+||||
 
 ## Core Features
 - **Gift List Retrieval**: Retrieve gift panel data from the server, including gift categories and details.
@@ -11,13 +12,13 @@
 - **Gift Event Broadcasting:** Real-time synchronization of gift events across all clients in the room to trigger animations and barrage notifications.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibilities & Description** |
+| <strong>Core Concept</strong> | <strong>Type</strong> | <strong>Core Responsibilities & Description</strong> |
 | --- | --- | --- |
-| `Gift` | `struct` | Represents a gift data model, including ID, name, icon URL, animation resource URL (resourceURL), price (coins), and more. |
-| `GiftCategory` | `struct` | - Represents a grouping of gifts (e.g., "Popular", "Luxury").<br>- Contains a category name and an array of Gift objects. |
-| `GiftState` | `struct` | - Represents the current state of the gift module.<br>- The core property, usableGifts, is a StateFlow containing the full gift list from the server. |
-| `GiftEvent` | `enum` | Defines the event listener for gift events in the live room. Currently, only `onReceiveGift` is available. This event is broadcast to all users in the room (including the sender) whenever a gift is successfully sent. |
-| `GiftStore` | `class` | - The core management class for gift features.<br>- Used to fetch gift lists, execute send requests, and listen for global gift events. |
+| <code>Gift</code> | <code>struct</code> | Represents a gift data model, including ID, name, icon URL, animation resource URL (resourceURL), price (coins), and more. |
+| <code>GiftCategory</code> | <code>struct</code> | - Represents a grouping of gifts (e.g., "Popular", "Luxury").<br>- Contains a category name and an array of Gift objects. |
+| <code>GiftState</code> | <code>struct</code> | - Represents the current state of the gift module.<br>- The core property, usableGifts, is a StateFlow containing the full gift list from the server. |
+| <code>GiftEvent</code> | <code>enum</code> | Defines the event listener for gift events in the live room. Currently, only <code>onReceiveGift</code> is available. This event is broadcast to all users in the room (including the sender) whenever a gift is successfully sent. |
+| <code>GiftStore</code> | <code>class</code> | - The core management class for gift features.<br>- Used to fetch gift lists, execute send requests, and listen for global gift events. |
 
 ## Implementation
 
@@ -94,26 +95,26 @@ class GiftManager {
 #### Gift List Struct Parameters
 - **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` | `[String: String]` | Extension information field. |
-| `giftList` | `[`[Gift](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/gift)`]` | Array of Gift objects contained in this category. |
+   |**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`|`[String: String]`|Extension information field.|
+   |`giftList`|`[`[Gift](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/gift)`]`|Array of Gift objects contained in 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` | Gift icon URL. |
-| `resourceURL` | `String` | Gift animation resource URL. |
-| `level` | `UInt` | Gift level. |
-| `coins` | `UInt` | Gift price. |
-| `extensionInfo` | `[String: String]` | Extension information field. |
+   |**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`|Gift icon URL.|
+   |`resourceURL`|`String`|Gift animation resource URL.|
+   |`level`|`UInt`|Gift level.|
+   |`coins`|`UInt`|Gift price.|
+   |`extensionInfo`|`[String: String]`|Extension information field.|
 
 ### Step 3: Retrieve Gift List
 
@@ -175,11 +176,12 @@ extension GiftManager {
 ```
 
 #### sendGift API Parameters
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `giftID` | `String` | The unique ID of the gift to send. |
-| `count` | `UInt` | The number of gifts to send. |
-| `completion` | `CompletionClosure?` | Callback after sending is complete. |
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`giftID`|`String`|The unique ID of the gift to send.|
+|`count`|`UInt`|The number of gifts to send.|
+|`completion`|`CompletionClosure?`|Callback after sending is complete.|
 
 ## Advanced Features
 
@@ -199,18 +201,18 @@ You can fully customize your gift inventory (names, icons, prices, animations) t
 #### 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 |
+| <strong>​Gift Management</strong> | Add Gift Information | Example |
 | Delete Gift Information | Example |  |
 | Query Gift Information | Example |  |
-| **Gift Category Management** | Add Gift Category Information | Example |
+| <strong>Gift Category Management</strong> | 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 |
+| <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 |  |
-| **Gift Multi-language Management** | Add Gift Multi-language Information | 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 |  |
@@ -233,9 +235,9 @@ AtomicXCore delegates the billing logic to your backend to ensure security and f
 #### Call Flow
 
 #### Related REST API Interfaces Overview
-| **Interface** | **Description** | **Request Example** |
+| <strong>Interface</strong> | <strong>Description</strong> | <strong>Request Example</strong> |
 | --- | --- | --- |
-| **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 |
+| <strong>Callback Configuration - Callback before sending a gift</strong> | 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 |
 
 ### Full-Screen Animation (SVGA Integration)
 
@@ -244,15 +246,16 @@ When a user sends a luxury gift (e.g., "Rocket", "Carnival"), play a full-screen
 #### Implementation
 
 **AtomicXCore** does not include a built-in gift animation player. Integrate a third-party library based on your requirements. Below is a comparison of two options:
-| **Comparison Item** | **Basic Solution (SVGAPlayer)** | **Gift AR (TCEffectPlayerKit)** |
-| --- | --- | --- |
-| Billing | Free (open source) | Paid (License Required). See [Billing Guide](https://trtc.io/document/69949?product=beautyar&menulabel=core%20sdk&platform=android#X-Series-Capabilities) |
-| Integration Method | Manual integration via Gradle | Requires additional integration and authentication |
-| Formats | SVGA only | SVGA, PAG, WebP, Lottie, MP4, and more |
-| Performance | Good for files < 10MB | Optimized for large assets & complex layering |
-| Recommended Scenario | Uniform SVGA format, controllable file size | Multiple formats or higher performance/device compatibility needs |
 
-This section demonstrates the basic solution. For the **Gift AR**, see the [TCEffectPlayer Integration Guide](https://trtc.io/document/70537?product=beautyar&menulabel=core%20sdk&platform=ios).
+|**Comparison Item**|**Basic Solution (SVGAPlayer)**|**Gift AR (TCEffectPlayerKit)**|
+|---------|---------|---------|
+|Billing|Free (open source)|Paid (License Required). See [Billing Guide](https://trtc.io/document/69949)|
+|Integration Method|Manual integration via Gradle|Requires additional integration and authentication|
+| Formats|SVGA only|SVGA, PAG, WebP, Lottie, MP4, and more|
+|Performance|Good for files < 10MB|Optimized for large assets & complex layering|
+|Recommended Scenario|Uniform SVGA format, controllable file size|Multiple formats or higher performance/device compatibility needs|
+
+This section demonstrates the basic solution. For the **Gift AR**, see the [TCEffectPlayer Integration Guide](https://trtc.io/document/70537).
 
 #### Basic Solution Implementation: Using SVGAPlayer
 1. **Integrate SVGAPlayer**: In your `Podfile`, add the dependency for `SVGAPlayer` and run `pod install` in the terminal.
@@ -370,10 +373,11 @@ private func setupGiftToBarrageFlow() {
 ## API Documentation
 
 For complete details on all public interfaces, properties, and methods of [GiftStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/giftstore) and related classes, see the official API documentation for [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore). Key stores referenced in this guide include:
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| GiftStore | Fetch gift list, send/receive gifts, listen for gift events (including sender and gift details). | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/giftstore) |
-| BarrageStore | Send text/custom barrage, maintain barrage list, listen to barrage status in real time. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|GiftStore|Fetch gift list, send/receive gifts, listen for gift events (including sender and gift details).|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/giftstore)|
+|BarrageStore|Send text/custom barrage, maintain barrage list, listen to barrage status in real time.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)|
 
 ## FAQs