@tencent-rtc/mcp 1.6.4 → 1.6.5

package/resource/knowledge/chat/preset/flutter/features/search.md

@@ -2,9 +2,8 @@
 
 The Search component provides a full-featured search experience, including a search bar, results display, and seamless page navigation. It supports searching for users, groups, and messages, and offers extensive interactive Webhook integration for custom workflows.
 
-> **Note****：**
+> **Note：**
 >
-
 > Search is available in the Pro edition and Enterprise edition. To use Search function, you need to purchase either the Pro or Enterprise package. For details, see [Billing Information](https://trtc.io/document/67650).
 >
 
@@ -22,10 +21,10 @@ Search is included in TUIKit Flutter. To use the Search component, integrate TUI
 
 |Method|Parameter|Description|
 |---------|---------|---------|
-|SearchBar|`onContactSelect: (`[FriendSearchInfo](https://pub.dev/documentation/atomic_x_core/latest/api_search_search_store/FriendSearchInfo-class.html)` selectedContact) {}`|Webhook triggered when a contact result is clicked; optional parameter.|
-|SearchBar|`onGroupSelect: (`[GroupSearchInfo](https://pub.dev/documentation/atomic_x_core/latest/api_search_search_store/GroupSearchInfo-class.html)` selectedGroup) {}`|Webhook triggered when a group result is clicked; optional parameter.|
-|SearchBar|`onConversationSelect: (`[MessageSearchResultItem](https://pub.dev/documentation/atomic_x_core/latest/api_search_search_store/MessageSearchResultItem-class.html)` selectedConversation) {}`|Webhook triggered when a conversation result is clicked; optional parameter.|
-|SearchBar|`onMessageSelect: (`[MessageInfo](https://pub.dev/documentation/atomic_x_core/latest/api_message_message_list_store/MessageInfo-class.html)` selectedMessage) {}`|Webhook triggered when a message result is clicked; optional parameter.|
+|SearchBar|`onContactSelect: (`[FriendSearchInfo](https://pub.dev/documentation/atomic_x_core/latest/api_search_search_store/FriendSearchInfo-class.html) `selectedContact) {}`|Webhook triggered when a contact result is clicked; optional parameter.|
+|SearchBar|`onGroupSelect: (`[GroupSearchInfo](https://pub.dev/documentation/atomic_x_core/latest/api_search_search_store/GroupSearchInfo-class.html) `selectedGroup) {}`|Webhook triggered when a group result is clicked; optional parameter.|
+|SearchBar|`onConversationSelect: (`[MessageSearchResultItem](https://pub.dev/documentation/atomic_x_core/latest/api_search_search_store/MessageSearchResultItem-class.html) `selectedConversation) {}`|Webhook triggered when a conversation result is clicked; optional parameter.|
+|SearchBar|`onMessageSelect: (`[MessageInfo](https://pub.dev/documentation/atomic_x_core/latest/api_message_message_list_store/MessageInfo-class.html) `selectedMessage) {}`|Webhook triggered when a message result is clicked; optional parameter.|
 
 ## Basic Usage
 

package/resource/knowledge/chat/preset/flutter/features/theme.md

@@ -39,7 +39,7 @@ All theme configuration and queries are managed through the `ThemeState` API.
 |`setPrimaryColor`|`String`|`Unit`|Sets the primary theme color using a Hex string (e.g., "#1C66E5").|
 |`clearPrimaryColor`|None|`Unit`|Removes the custom theme color and resets to the default blue.|
 
-> **Notes****：**
+> **Notes：**
 >
 > - Both `setThemeMode` and `setPrimaryColor` automatically persist the configuration. No manual save is required. Settings are restored on app startup.
 > - Changing theme configuration automatically clears the cache to ensure real-time updates. Manual cache management is not needed.
@@ -214,7 +214,7 @@ final themeState = BaseThemeProvider.of(context);
 themeState.setPrimaryColor('#1C66E5');
 ```
 
-> **Recommendations****：**
+> **Recommendations：**
 >
 > - For most use cases, we recommend managing appearance via a JSON configuration file for simplicity, reliability, and cross-platform consistency.
 > - Always use colors from `themeState.colors` throughout your app to maintain a consistent look when switching themes.

package/resource/knowledge/chat/preset/ios/features/chat-setting.md

@@ -23,7 +23,7 @@ ChatSetting contains two main components: C2CChatSetting (C2C Chat Settings) and
 |---------|---------|---------|
 |`userID`|`String`|The user ID of the chat partner.|
 |`onSendMessageClick`|`(() -> Void)?`|The webhook triggered when the Send Message button is clicked (optional).|
-|`onContactDelete`|`(() -> Void)? `|The webhook triggered when the Delete Contact button is clicked (optional).|
+|`onContactDelete`|`(() -> Void)?` |The webhook triggered when the Delete Contact button is clicked (optional).|
 
 #### Initialization Interface
 

package/resource/knowledge/chat/preset/ios/features/conversation-list.md

@@ -124,11 +124,10 @@ ConversationList(
 
 > **Note:**
 >
-
 > Local configuration takes precedence over global configuration.
 >
 
 The following images show the customization effects:
-| <strong>Conversation Actions</strong><br><strong> (Default Options)</strong> | <strong>Conversation Actions</strong><br><strong> (Delete Option Hidden)</strong> | <strong>Conversation Actions </strong><br><strong>(Share Option Added)</strong> |
+| <strong>Conversation Actions</strong><br><strong>(Default Options)</strong> | <strong>Conversation Actions</strong><br><strong>(Delete Option Hidden)</strong> | <strong>Conversation Actions</strong><br><strong>(Share Option Added)</strong> |
 | --- | --- | --- |
 |  |  |  |

package/resource/knowledge/chat/preset/ios/features/message-list.md

@@ -152,11 +152,10 @@ MessageList(
 
 > **Note：**
 >
-
 > Local configuration overrides global configuration.
 >
 
 The following images show the customization effects:
-| <strong>Message List Actions</strong><br><strong> (Default Options)</strong> | <strong>Message List Actions </strong><br><strong>(Hide Copy Option)</strong> | <strong>Message List Actions </strong><br><strong>(Add Share Option)</strong> |
+| <strong>Message List Actions</strong><br><strong>(Default Options)</strong> | <strong>Message List Actions</strong><br><strong>(Hide Copy Option)</strong> | <strong>Message List Actions</strong><br><strong>(Add Share Option)</strong> |
 | --- | --- | --- |
 |  |  |  |

package/resource/knowledge/chat/preset/ios/features/search.md

@@ -4,7 +4,6 @@ Search is a search component that provides users with a complete set of features
 
 > **Note：**
 >
-
 > Search function is available only in the Pro Edition or Enterprise Edition. You can use this feature after purchasing the Pro Edition or Enterprise Edition package. For details, see [Pricing Information](https://trtc.io/document/67650).
 >
 

package/resource/knowledge/chat/preset/ios-uikit/integration.md

@@ -45,10 +45,10 @@ TUIKit is a UI component library built on the Chat SDK. It enables rapid impleme
 
 > **Note：**
 >
-> 3. Starting from version 8.5.6870, TUIKit supports Swift components.
-> 4. If you add only `pod 'TUIChat'` in your Podfile without specifying Classic or Minimalist UI, both UI component versions will be integrated by default.
-> 5. **Classic and Minimalist UI cannot be mixed.** When integrating multiple components, select either all Classic UI or all Minimalist UI components. For example, the Classic `TUIChat` component must be used with Classic `TUIConversation` and `TUIContact` components. Similarly, the Minimalist `TUIChat` component must be used with Minimalist `TUIConversation` and `TUIContact` components.
-> 6. If you use Swift, enable `use_modular_headers!` and use the @import module format for header imports.
+> 1. Starting from version 8.5.6870, TUIKit supports Swift components.
+> 2. If you add only `pod 'TUIChat'` in your Podfile without specifying Classic or Minimalist UI, both UI component versions will be integrated by default.
+> 3. **Classic and Minimalist UI cannot be mixed.** When integrating multiple components, select either all Classic UI or all Minimalist UI components. For example, the Classic `TUIChat` component must be used with Classic `TUIConversation` and `TUIContact` components. Similarly, the Minimalist `TUIChat` component must be used with Minimalist `TUIConversation` and `TUIContact` components.
+> 4. If you use Swift, enable `use_modular_headers!` and use the @import module format for header imports.
 
 Add the required component libraries to your Podfile as needed:
 
@@ -348,8 +348,8 @@ pod install
 
 > **Note：**
 >
-> 7. If you cannot install the latest version of TUIKit, run `pod repo update` to update your local CocoaPods repository, then run `pod update` to update the component library version.
-> 8. If you encounter third-party library version conflicts, see CocoaPods FAQs - Dependency Version Conflicts.
+> 1. If you cannot install the latest version of TUIKit, run `pod repo update` to update your local CocoaPods repository, then run `pod update` to update the component library version.
+> 2. If you encounter third-party library version conflicts, see CocoaPods FAQs - Dependency Version Conflicts.
 
 After successfully integrating all TUIKit components, your project directory should resemble the following:
 
@@ -533,10 +533,10 @@ pod install
 
 > **Notes：**
 >
-> 4. When using local integration, you must obtain the latest component code from GitHub and overwrite your local TUIKit directory when upgrading.
-> 5. If you have private modifications that conflict with the remote repository, manually merge and resolve conflicts.
-> 6. TUIKit plugins depend on the TUICore version. Ensure the plugin version matches the `spec.version` in `../TUIKit/TUICore/TUICore.spec`.
-> 7. If you encounter third-party library version conflicts, see CocoaPods FAQs - Dependency Version Conflicts.
+> 1. When using local integration, you must obtain the latest component code from GitHub and overwrite your local TUIKit directory when upgrading.
+> 2. If you have private modifications that conflict with the remote repository, manually merge and resolve conflicts.
+> 3. TUIKit plugins depend on the TUICore version. Ensure the plugin version matches the `spec.version` in `../TUIKit/TUICore/TUICore.spec`.
+> 4. If you encounter third-party library version conflicts, see CocoaPods FAQs - Dependency Version Conflicts.
 
       Now you have successfully integrated TUIKit into your project. To continue building basic interfaces such as chat and conversation, see [Build Chat Interface](https://www.tencentcloud.com/zh/document/product/1047/61215) and [Build Conversation List.](https://www.tencentcloud.com/zh/document/product/1047/61217)
 
@@ -549,13 +549,13 @@ pod install
 
    **Solution 1**: Change your Xcode project’s `Project Format` version to Xcode 13.0.
 
-   ** Solution 2**: Upgrade your local version of CocoaPods. (Upgrade steps not detailed here.)
+    **Solution 2**: Upgrade your local version of CocoaPods. (Upgrade steps not detailed here.)
 
 - **Assertion failed: (false && "compact unwind compressed function offset doesn't fit in 24 bits"), function operator(), file Layout.cpp.**
 
    Alternatively, when integrating TUIRoom with Xcode 15, you may encounter symbol conflicts in TUIRoomEngine caused by the latest linker. Both issues have the same root cause.
 
-   **Solution**: Update the linker configuration. Add `-ld64` to `Other Linker Flags` in Build Settings.
+    **Solution**: Update the linker configuration. Add `-ld64` to `Other Linker Flags` in Build Settings.
 
     Official document: [https://developer.apple.com/forums/thread/735426](https://links.jianshu.com/go)
 
@@ -620,9 +620,7 @@ pod install
 
   2. In the [TUICore.podspec](https://github.com/TencentCloud/chat-uikit-ios/blob/main/TUIKit/TUICore/TUICore.podspec) file, set the version number to the same remote version (for example, 7.5.4852).By ensuring all components use a consistent version, you can avoid dependency conflicts during integration.
 
--
-
-**Which third-party libraries does TUIKit depend on? What should I do if there are version conflicts?**
+- **Which third-party libraries does TUIKit depend on? What should I do if there are version conflicts?**
 
    TUIKit manages dependencies automatically via CocoaPods, so manual intervention is typically unnecessary. If you encounter version conflicts, ensure your third-party library versions meet the following minimum requirements:
 

package/resource/knowledge/chat/preset/react/features/conversation-list.md

@@ -147,7 +147,7 @@ import { ConversationList } from '@tencentcloud/chat-uikit-react';
 
 |**Prop Name**|**Type**|**Default**|**Description**|
 |---------|---------|---------|---------|
-|children|`ReactNode`|-|Custom center component for the conversation list header. When used in ``,  and `` are passed in by default.|
+|children|`ReactNode`|-|Custom center component for the conversation list header. When used in ``,  and` ` are passed in by default.|
 |left|`ReactElement`|-|Custom component for the left side of the conversation list header.|
 |right|`ReactElement`|-|Custom component for the right side of the conversation list header.|
 |className|`String`|-|Custom CSS class name for the root element.|
@@ -252,10 +252,10 @@ By default, it displays the current conversation list data (`filteredAndSortedCo
 
 |**Prop Name**|**Type**|**Default**|**Description**|
 |---------|---------|---------|---------|
-|children|`ReactNode`|-|Custom component for the conversation list content area. When used in , the `filteredAndSortedConversationList` is passed in and iterated as a list of `` components.|
-|empty|`Boolean`|`false`|Flag for empty conversation list. When used in ``, it checks if `filteredAndSortedConversationList.length === 0` and passes this in.|
-|loading|`Boolean`|`false`|Flag for conversation list loading state. When used in ``, it uses `useConversationList()` to get `isLoading` and passes it in.|
-|error|`Boolean`|`false`|Flag for conversation list load error. When used in ``, it uses `useConversationList()` to get `isLoadError` and passes it in.|
+|children|`ReactNode`|-|Custom component for the conversation list content area. When used in  , the `filteredAndSortedConversationList` is passed in and iterated as a list of `` components.|
+|empty|`Boolean`|`false`|Flag for empty conversation list. When used in ``, it checks if` filteredAndSortedConversationList.length === 0` and passes this in.|
+|loading|`Boolean`|`false`|Flag for conversation list loading state. When used in ``, it uses` useConversationList() `to get` isLoading` and passes it in.|
+|error|`Boolean`|`false`|Flag for conversation list load error. When used in ``, it uses` useConversationList() `to get` isLoadError` and passes it in.|
 |PlaceholderEmptyList|`ReactNode`|``|Custom placeholder element when the conversation list is empty.|
 |PlaceholderLoading|`ReactNode`|``|Custom placeholder element when the conversation list is loading.|
 |PlaceholderLoadError|`ReactNode`|``|Custom placeholder element when the conversation list fails to load.|

package/resource/knowledge/chat/preset/react/features/message-input.md

@@ -71,11 +71,10 @@ Sets the display mode for the attachment picker. Default: `'collapsed'`.
 
    > **Note:**
    >
-
    > The default AttachmentPicker includes file, image, and video selection.
    >
->   1. When `attachmentPickerMode` is `"collapsed"`, clicking the attachment picker opens a popup menu with file, image, and video options.
->   2. When `attachmentPickerMode` is `"expanded"`, the picker displays file, image, and video options inline by default.
+   > 1. When `attachmentPickerMode` is `"collapsed"`, clicking the attachment picker opens a popup menu with file, image, and video options.
+   > 2. When `attachmentPickerMode` is `"expanded"`, the picker displays file, image, and video options inline by default.
 
 ### actions
 

package/resource/knowledge/chat/preset/react/features/search.md

@@ -4,7 +4,6 @@ Search is a complete search solution with a full set of components, including se
 
 > **Note:**
 >
-
 > Note: This feature belongs to VAS. You need to purchase cloud search plugin. Please click [purchase](https://console.trtc.io/chat/plugin/TUICloudSearch).
 >
 

package/resource/knowledge/chat/preset/react/features/theme.md

@@ -45,7 +45,6 @@ Use the `useUIKit` Hook to access theme and language features.
 
 > **Note:**
 >
-
 > Note: Since the theme feature is implemented using React Context, `useUIKit()` is unable to be called in the root component.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/AudioEffectStore.md

@@ -2,21 +2,18 @@
 
 `AudioEffectStore` provides a complete set of audio effect management APIs, including voice changer effects, reverb effects, and ear monitor functionality. Through this class, anchors can adjust their voice effects in real-time during live streaming to enhance the experience.
 
-> **Important: **
+> **Important:**
 >
-
 > Use the **AudioEffectStore.shared** singleton to get the `AudioEffectStore` instance. The set effects will automatically become invalid after leaving the room, and need to be set again for the next room entry.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Audio effect state updates are delivered through the **audioEffectState** publisher. Subscribe to it to receive real-time updates about voice changer, reverb, and ear monitor states.
 >
 
-> **Warning: **
+> **Warning:**
 >
-
 > Due to the very high hardware latency of Bluetooth earphones, the ear monitor feature cannot be enabled when the anchor is wearing Bluetooth earphones. Please prompt the anchor to wear wired earphones in the user interface.
 >
 
@@ -80,9 +77,8 @@ Call after entering the room and when voice changer effect is needed.
 
 **Notes**
 
-> **Note: **
+> **Note:**
 >
-
 > The set effect will automatically become invalid after leaving the room. If you need the corresponding effect for the next room entry, you need to call this interface again to set it.
 >
 
@@ -115,9 +111,8 @@ Call after entering the room and when reverb effect is needed.
 
 **Notes**
 
-> **Note: **
+> **Note:**
 >
-
 > The set effect will automatically become invalid after leaving the room. If you need the corresponding effect for the next room entry, you need to call this interface again to set it.
 >
 
@@ -152,9 +147,8 @@ Call after entering the room and when the anchor is wearing wired earphones.
 
 **Notes**
 
-> **Warning: **
+> **Warning:**
 >
-
 > Due to the very high hardware latency of Bluetooth earphones, this effect cannot be enabled when the anchor is wearing Bluetooth earphones. Please try to prompt the anchor to wear wired earphones in the user interface.
 >
 
@@ -183,9 +177,8 @@ Call after enabling the ear monitor feature.
 
 **Notes**
 
-> **Note: **
+> **Note:**
 >
-
 > If the volume is still too low after setting it to 100, you can set the volume to a maximum of 150, but a volume exceeding 100 may cause distortion, please operate with caution.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/BarrageStore.md

@@ -2,15 +2,13 @@
 
 `BarrageStore` provides a complete set of barrage management APIs, including sending text barrages, sending custom barrages, and adding local tip messages. Through this class, you can implement barrage interaction functionality in live rooms.
 
-> **Important: **
+> **Important:**
 >
-
 > Use the **BarrageStore.create** factory method to create a `BarrageStore` instance, which requires a valid live room ID.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Barrage state updates are delivered through the **barrageState** publisher. Subscribe to it to receive real-time updates of barrage data in the room.
 >
 
@@ -77,7 +75,7 @@ Supported since version 3.5.
 |**Parameter**|**Type**|**Description**|
 |---------|---------|---------|
 |text|String?|Text barrage content.|
-|extensionInfo|Map<String,String>?|Extension information, can contain custom fields (such as specifying barrage color, font size, etc.).|
+|extensionInfo|Map<String, String>?|Extension information, can contain custom fields (such as specifying barrage color, font size, etc.).|
 |completion|CompletionHandler?|Completion callback (success/failure status).|
 
 #### sendCustomMessage
@@ -118,9 +116,8 @@ Supported since version 3.5.
 
 **Notes**
 
-> **Note: **
+> **Note:**
 >
-
 > This message is only displayed locally and will not be sent to other users through the network.
 >
 
@@ -153,7 +150,7 @@ Barrage data model, containing complete attribute information of a single barrag
 |timestampInSecond|Long|Barrage sending timestamp (unit: seconds), used to display sending time order.|
 |messageType|BarrageType|Barrage message type (text or custom).|
 |textContent|String|Message content of text type barrage, i.e., the text content of the barrage.|
-|extensionInfo|Map<String,String>|Barrage extension information, customizable fields (such as display style, priority, etc.). Valid when messageType is TEXT.|
+|extensionInfo|Map<String, String>|Barrage extension information, customizable fields (such as display style, priority, etc.). Valid when messageType is TEXT.|
 |businessID|String|Business identifier ID of custom type barrage, used to distinguish custom barrages from different business scenarios.|
 |data|String|Specific data content of custom type barrage (usually JSON format string), valid when messageType is CUSTOM.|
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/BattleStore.md

@@ -2,21 +2,18 @@
 
 PK feature enables real-time interactive battles between hosts. `BattleStore` provides a comprehensive set of APIs to manage the entire PK lifecycle.
 
-> **Important: **
+> **Important:**
 >
-
 > Always use the factory method **BattleStore.create** with a valid live room ID to create a `BattleStore` instance. Do not attempt to initialize directly.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > PK state updates are delivered through the **battleState** publisher. Subscribe to it to receive real-time updates about PK information, participating users, and scores.
 >
 
-> **Warning: **
+> **Warning:**
 >
-
 > If a PK request does not receive a response within the specified timeout, a timeout event will be triggered. Always handle timeout scenarios in the UI.
 >
 
@@ -37,7 +34,7 @@ PK feature enables real-time interactive battles between hosts. `BattleStore` pr
 |---------|---------|---------|
 |currentBattleInfo|StateFlow<BattleInfo?>|Current PK information.|
 |battleUsers|StateFlow<List<SeatUserInfo>>|PK user list.|
-|battleScore|StateFlow<Map<String,Int>>|PK score mapping.|
+|battleScore|StateFlow<Map<String, Int>>|PK score mapping.|
 
 ## API List
 
@@ -226,15 +223,15 @@ PK-related callback events received.
 
 |**Method**|**Description**|
 |---------|---------|
-|onBattleStarted|ThiscallbackistriggeredwhenPKofficiallystarts,notifyingallparticipantsthatPKhasbegun.|
-|onBattleEnded|ThiscallbackistriggeredwhenPKends.|
-|onUserJoinBattle|ThiscallbackistriggeredwhenauserjoinsPK.|
-|onUserExitBattle|ThiscallbackistriggeredwhenauserexitsPK.|
-|onBattleRequestReceived|ThiscallbackistriggeredwhenaPKrequestisreceived.|
-|onBattleRequestCancelled|ThiscallbackistriggeredwhenaPKrequestiscancelled.|
-|onBattleRequestTimeout|ThiscallbackistriggeredwhenaPKrequesttimesout.|
-|onBattleRequestAccept|ThiscallbackistriggeredwhenaPKrequestisaccepted.|
-|onBattleRequestReject|ThiscallbackistriggeredwhenaPKrequestisrejected.|
+|onBattleStarted|This callback is triggered when PK officially starts, notifying all participants that PK has begun.|
+|onBattleEnded|This callback is triggered when PK ends.|
+|onUserJoinBattle|This callback is triggered when a user joins PK.|
+|onUserExitBattle|This callback is triggered when a user exits PK.|
+|onBattleRequestReceived|This callback is triggered when a PK request is received.|
+|onBattleRequestCancelled|This callback is triggered when a PK request is cancelled.|
+|onBattleRequestTimeout|This callback is triggered when a PK request times out.|
+|onBattleRequestAccept|This callback is triggered when a PK request is accepted.|
+|onBattleRequestReject|This callback is triggered when a PK request is rejected.|
 
 ### BattleConfig
 
@@ -265,7 +262,7 @@ PK-related state data provided by BattleStore.
 |---------|---------|---------|
 |currentBattleInfo|StateFlow<BattleInfo?>|Current PK information.|
 |battleUsers|StateFlow<List<SeatUserInfo>>|PK user list.|
-|battleScore|StateFlow<Map<String,Int>>|PK score mapping.|
+|battleScore|StateFlow<Map<String, Int>>|PK score mapping.|
 
 ### BattleRequestCallback
 
@@ -283,7 +280,7 @@ fun onSuccess(battleInfo: BattleInfo, resultMap: Map<String, Int>)
 |**Parameter**|**Type**|**Description**|
 |---------|---------|---------|
 |battleInfo|BattleInfo|PK information, containing detailed configuration and status of the PK.|
-|resultMap|Map<String,Int>|Response result callback for PK request.|
+|resultMap|Map<String, Int>|Response result callback for PK request.|
 
 **onError**: Failure callback.
 ``` kotlin

package/resource/knowledge/livekit/core-sdk/api-reference/android/CameraView.md

@@ -2,9 +2,8 @@
 
 `CameraView` is a view component specifically designed to display camera preview. When starting camera test, the camera rendering view will be displayed on this view.
 
-> **Note: **
+> **Note:**
 >
-
 > This class is only available on Android platform.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/CoGuestStore.md

@@ -2,21 +2,18 @@
 
 Co-guest feature enables real-time interaction between hosts and audience members through a seat-based system. `CoGuestStore` provides a comprehensive set of APIs to manage the entire co-guest lifecycle.
 
-> **Important: **
+> **Important:**
 >
-
 > Always use the factory method **CoGuestStore.create** with a valid live room ID to create a `CoGuestStore` instance. Do not attempt to initialize directly.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Co-guest state updates are delivered through the **coGuestState** publisher. Subscribe to it to receive real-time updates about connected users, invitations and applications.
 >
 
-> **Warning: **
+> **Warning:**
 >
-
 > If a co-guest request does not receive a response within the specified timeout, an event with `NoResponseReason.timeout` will be triggered. Always handle timeout scenarios in your UI.
 >
 
@@ -171,9 +168,8 @@ Supported since version 3.5.
 
 **Notes**
 
-> **Note: **
+> **Note:**
 >
-
 > If no host responds within the timeout, {ref2} event with **NoResponseReason.TIMEOUT** will be triggered.
 >
 
@@ -203,9 +199,8 @@ Supported since version 3.5.
 
 **Notes**
 
-> **Note: **
+> **Note:**
 >
-
 > If the application has already been processed by a host, the cancellation may have no effect.
 >
 
@@ -374,11 +369,11 @@ Callback events received on host side.
 
 |**Method**|**Description**|
 |---------|---------|
-|onGuestApplicationReceived|Thiscallbackistriggeredwhenanaudienceappliesforco-guest.|
-|onGuestApplicationCancelled|Thiscallbackistriggeredwhenanaudiencecancelsco-guestapplication.|
-|onGuestApplicationProcessedByOtherHost|Thiscallbackistriggeredwhenanaudience'sco-guestapplicationisprocessedbyanotherhost.|
-|onHostInvitationResponded|Thiscallbackistriggeredwhenaco-guestinvitationsentbyhostreceivesaresponsefromaudience.|
-|onHostInvitationNoResponse|Thiscallbackistriggeredwhenaco-guestinvitationsentbyhostreceivesnoresponse.|
+|onGuestApplicationReceived|This callback is triggered when an audience applies for co-guest.|
+|onGuestApplicationCancelled|This callback is triggered when an audience cancels co-guest application.|
+|onGuestApplicationProcessedByOtherHost|This callback is triggered when an audience's co-guest application is processed by another host.|
+|onHostInvitationResponded|This callback is triggered when a co-guest invitation sent by host receives a response from audience.|
+|onHostInvitationNoResponse|This callback is triggered when a co-guest invitation sent by host receives no response.|
 
 ### GuestListener
 
@@ -388,11 +383,11 @@ Callback events received on guest side.
 
 |**Method**|**Description**|
 |---------|---------|
-|onHostInvitationReceived|Thiscallbackistriggeredwhenreceivingaco-guestinvitationfromhost.|
-|onHostInvitationCancelled|Thiscallbackistriggeredwhenhostcancelsco-guestinvitation.|
-|onGuestApplicationResponded|Thiscallbackistriggeredwhenaudience'sco-guestapplicationreceivesaresponsefromhost.|
-|onGuestApplicationNoResponse|Thiscallbackistriggeredwhenaudience'sco-guestapplicationreceivesnoresponse.|
-|onKickedOffSeat|Thiscallbackistriggeredwhenaudienceiskickedoffseatbyhost.|
+|onHostInvitationReceived|This callback is triggered when receiving a co-guest invitation from host.|
+|onHostInvitationCancelled|This callback is triggered when host cancels co-guest invitation.|
+|onGuestApplicationResponded|This callback is triggered when audience's co-guest application receives a response from host.|
+|onGuestApplicationNoResponse|This callback is triggered when audience's co-guest application receives no response.|
+|onKickedOffSeat|This callback is triggered when audience is kicked off seat by host.|
 
 ### CoGuestState
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/CoHostStore.md

@@ -2,21 +2,18 @@
 
 Cross-room connection feature allows hosts from different live rooms to interact in real-time. `CoHostStore` provides a comprehensive set of APIs to manage the entire cross-room connection lifecycle.
 
-> **Important: **
+> **Important:**
 >
-
 > Always use the factory method **CoHostStore.create** with a valid live room ID to create a `CoHostStore` instance. Do not attempt to initialize directly.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Connection state updates are delivered through the **coHostState** publisher. Subscribe to it to receive real-time updates about connection status, connected hosts, invitations and applications.
 >
 
-> **Warning: **
+> **Warning:**
 >
-
 > If a connection request does not receive a response within the specified timeout, the timeout event will be triggered. Always handle timeout scenarios in your UI.
 >
 
@@ -298,13 +295,13 @@ Connection request callback events.
 
 |**Method**|**Description**|
 |---------|---------|
-|onCoHostRequestReceived|Thiscallbackistriggeredwhenaconnectionrequestisreceived.|
-|onCoHostRequestCancelled|Thiscallbackistriggeredwhenaconnectionrequestiscancelled.|
-|onCoHostRequestAccepted|Thiscallbackistriggeredwhenaconnectionrequestisaccepted.|
-|onCoHostRequestRejected|Thiscallbackistriggeredwhenaconnectionrequestisrejected.|
-|onCoHostRequestTimeout|Thiscallbackistriggeredwhenaconnectionrequesttimesout.|
-|onCoHostUserJoined|Thiscallbackistriggeredwhenauserjoinstheconnection.|
-|onCoHostUserLeft|Thiscallbackistriggeredwhenauserleavestheconnection.|
+|onCoHostRequestReceived|This callback is triggered when a connection request is received.|
+|onCoHostRequestCancelled|This callback is triggered when a connection request is cancelled.|
+|onCoHostRequestAccepted|This callback is triggered when a connection request is accepted.|
+|onCoHostRequestRejected|This callback is triggered when a connection request is rejected.|
+|onCoHostRequestTimeout|This callback is triggered when a connection request times out.|
+|onCoHostUserJoined|This callback is triggered when a user joins the connection.|
+|onCoHostUserLeft|This callback is triggered when a user leaves the connection.|
 
 ### CoHostState
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/DeviceStore.md

@@ -2,15 +2,13 @@
 
 `DeviceStore` provides a comprehensive set of APIs to manage audio and video devices, including microphone, camera and screen sharing features.
 
-> **Important: **
+> **Important:**
 >
-
 > Use **DeviceStore.shared** singleton to get the `DeviceStore` instance. Do not attempt to initialize directly.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Device state updates are delivered through the **deviceState** publisher. Subscribe to it to receive real-time updates about microphone, camera, network and other states.
 >
 

package/resource/knowledge/livekit/core-sdk/api-reference/android/GiftStore.md

@@ -2,15 +2,13 @@
 
 `GiftStore` provides a complete set of gift management APIs, including sending gifts, refreshing gift lists, setting language, and listening to gift events. Through this class, gift interaction features can be implemented in live rooms.
 
-> **Important: **
+> **Important:**
 >
-
 > Use the **GiftStore.create** factory method to create a `GiftStore` instance, passing a valid live room ID.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Gift state updates are delivered through the **giftState** publisher. Subscribe to it to receive real-time updates of gift data in the room.
 >
 
@@ -132,7 +130,7 @@ Gift data model, containing complete attribute information of a single gift.
 |resourceURL|String|Network URL of the gift animation resource file, used to load gift display animations.|
 |level|Long|Gift level, used to distinguish gift rarity or value tier.|
 |coins|Long|Gift price (coins).|
-|extensionInfo|Map<String,String>|Gift extension information, customizable fields (such as effect type, sending restrictions, etc.).|
+|extensionInfo|Map<String, String>|Gift extension information, customizable fields (such as effect type, sending restrictions, etc.).|
 
 ### GiftCategory
 
@@ -143,7 +141,7 @@ Gift category.
 |categoryID|String|Category unique identifier ID, used to distinguish different gift categories.|
 |name|String|Category display name, used for UI category display (such as "Popular Gifts", "Premium Gifts").|
 |desc|String|Category description information, used to explain the characteristics of this category.|
-|extensionInfo|Map<String,String>|Category extension information, containing custom fields (such as sorting weight, display style, etc.).|
+|extensionInfo|Map<String, String>|Category extension information, containing custom fields (such as sorting weight, display style, etc.).|
 |giftList|List<Gift>|All gifts under the current category.|
 
 ### GiftState

package/resource/knowledge/livekit/core-sdk/api-reference/android/LikeStore.md

@@ -2,15 +2,13 @@
 
 `LikeStore` provides a complete set of like management APIs, including sending likes, listening to like events, and getting like states. Through this class, you can implement like interaction features in live rooms.
 
-> **Important: **
+> **Important:**
 >
-
 > Use the **LikeStore.create** factory method to create a `LikeStore` instance, which requires a valid live room ID.
 >
 
-> **Note: **
+> **Note:**
 >
-
 > Like state updates are delivered through the **likeState** publisher. Subscribe to it to receive real-time updates of like data in the room.
 >