Fix: Merge main branch (#10377)

### What problem does this PR solve?


### Type of change

- [x] Bug Fix (non-breaking change which fixes an issue)

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: jinhai <haijin.chn@gmail.com>
Signed-off-by: Jin Hai <haijin.chn@gmail.com>
Co-authored-by: Lynn <lynn_inf@hotmail.com>
Co-authored-by: chanx <1243304602@qq.com>
Co-authored-by: balibabu <cike8899@users.noreply.github.com>
Co-authored-by: 纷繁下的无奈 <zhileihuang@126.com>
Co-authored-by: huangzl <huangzl@shinemo.com>
Co-authored-by: writinwaters <93570324+writinwaters@users.noreply.github.com>
Co-authored-by: Wilmer <33392318@qq.com>
Co-authored-by: Adrian Weidig <adrianweidig@gmx.net>
Co-authored-by: Zhichang Yu <yuzhichang@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Yongteng Lei <yongtengrey@outlook.com>
Co-authored-by: Liu An <asiro@qq.com>
Co-authored-by: buua436 <66937541+buua436@users.noreply.github.com>
Co-authored-by: BadwomanCraZY <511528396@qq.com>
Co-authored-by: cucusenok <31804608+cucusenok@users.noreply.github.com>
Co-authored-by: Russell Valentine <russ@coldstonelabs.org>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Billy Bao <newyorkupperbay@gmail.com>
Co-authored-by: Zhedong Cen <cenzhedong2@126.com>
Co-authored-by: TensorNull <129579691+TensorNull@users.noreply.github.com>
Co-authored-by: TensorNull <tensor.null@gmail.com>
Co-authored-by: Ajay <160579663+aybanda@users.noreply.github.com>
Co-authored-by: AB <aj@Ajays-MacBook-Air.local>
Co-authored-by: 天海蒼灆 <huangaoqin@tecpie.com>
Co-authored-by: He Wang <wanghechn@qq.com>
Co-authored-by: Atsushi Hatakeyama <atu729@icloud.com>
Co-authored-by: Jin Hai <haijin.chn@gmail.com>
Co-authored-by: Mohamed Mathari <155896313+melmathari@users.noreply.github.com>
Co-authored-by: Mohamed Mathari <nocodeventure@Mac-mini-van-Mohamed.fritz.box>
Co-authored-by: Stephen Hu <stephenhu@seismic.com>
Co-authored-by: Shaun Zhang <zhangwfjh@users.noreply.github.com>
Co-authored-by: zhimeng123 <60221886+zhimeng123@users.noreply.github.com>
Co-authored-by: mxc <mxc@example.com>
Co-authored-by: Dominik Novotný <50611433+SgtMarmite@users.noreply.github.com>
Co-authored-by: EVGENY M <168018528+rjohny55@users.noreply.github.com>
Co-authored-by: mcoder6425 <mcoder64@gmail.com>
Co-authored-by: TeslaZY <TeslaZY@outlook.com>
Co-authored-by: lemsn <lemsn@msn.com>
Co-authored-by: lemsn <lemsn@126.com>
Co-authored-by: Adrian Gora <47756404+adagora@users.noreply.github.com>
Co-authored-by: Womsxd <45663319+Womsxd@users.noreply.github.com>
Co-authored-by: FatMii <39074672+FatMii@users.noreply.github.com>

docs/guides/team/join_or_leave_team.md

@@ -11,7 +11,7 @@ Accept an invite to join a team, decline an invite, or leave a team.
 
 Once you join a team, you can do the following:
 
-- Upload documents to the team owner's shared datasets (knowledge bases).
+- Upload documents to the team owner's shared datasets.
 - Parse documents in the team owner's shared datasets.
 - Use the team owner's shared Agents.
 
@@ -22,7 +22,7 @@ You cannot invite users to a team unless you are its owner.
 ## Prerequisites
 
 1. Ensure that your Email address that received the team invitation is associated with a RAGFlow user account.
-2. The team owner should share his knowledge bases by setting their **Permission** to **Team**.
+2. The team owner should share his datasets by setting their **Permission** to **Team**.
 
 ## Accept or decline team invite
 
@@ -32,6 +32,6 @@ You cannot invite users to a team unless you are its owner.
 
 _On the **Team** page, you can view the information about members of your team and the teams you have joined._
 
-_After accepting the team invite, you should be able to view and update the team owner's knowledge bases whose **Permissions** is set to **Team**._
+_After accepting the team invite, you should be able to view and update the team owner's datasets whose **Permissions** is set to **Team**._
 
 ## Leave a joined team

docs/guides/team/manage_team_members.md

@@ -11,7 +11,7 @@ Invite or remove team members.
 
 By default, each RAGFlow user is assigned a single team named after their name. RAGFlow allows you to invite RAGFlow users to your team. Your team members can help you:
 
-- Upload documents to your shared datasets (knowledge bases).
+- Upload documents to your shared datasets.
 - Parse documents in your shared datasets.
 - Use your shared Agents.
 
@@ -23,7 +23,7 @@ By default, each RAGFlow user is assigned a single team named after their name.
 ## Prerequisites
 
 1. Ensure that the invited team member is a RAGFlow user and that the Email address used is associated with a RAGFlow user account.
-2. To allow your team members to view and update your knowledge base, ensure that you set **Permissions** on its **Configuration** page from **Only me** to **Team**.
+2. To allow your team members to view and update your dataset, ensure that you set **Permissions** on its **Configuration** page from **Only me** to **Team**.
 
 ## Invite team members
 

docs/guides/team/share_knowledge_bases.md

@@ -3,16 +3,16 @@ sidebar_position: 4
 slug: /share_datasets
 ---
 
-# Share knowledge base
+# Share dataset
 
-Share a knowledge base with team members.
+Share a dataset with team members.
 
 ---
 
-When ready, you may share your knowledge bases with your team members so that they can upload and parse files in them. Please note that your knowledge bases are not shared automatically; you must manually enable sharing by selecting the appropriate **Permissions** radio button:
+When ready, you may share your datasets with your team members so that they can upload and parse files in them. Please note that your datasets are not shared automatically; you must manually enable sharing by selecting the appropriate **Permissions** radio button:
 
-1. Navigate to the knowledge base's **Configuration** page.
+1. Navigate to the dataset's **Configuration** page.
 2. Change **Permissions** from **Only me** to **Team**.
 3. Click **Save** to apply your changes.
 
-*Once completed, your team members will see your shared knowledge bases.*
+*Once completed, your team members will see your shared datasets.*