Deployed 742071d with MkDocs version: 1.6.0

admin/kpanda/inspect/report.html

@@ -584,11 +584,9 @@ <h2 id="_3">操作步骤<a class="headerlink" href="#_3" title="Permanent link">
 <p>点击想要查看的巡检记录名称。</p>
 <ul>
 <li>每执行一次巡检，就会生成一条巡检记录。</li>
-<li>
-<p>当巡检记录超过<a href="config.html">巡检配置</a>中设置的最大保留条数时，从执行时间最早的记录开始删除。</p>
-<p><img alt="start" src="../images/inspection-report-02.png"/></p>
-</li>
+<li>当巡检记录超过<a href="config.html">巡检配置</a>中设置的最大保留条数时，从执行时间最早的记录开始删除。</li>
 </ul>
+<p><img alt="start" src="../images/inspection-report-02.png"/></p>
 </li>
 <li>
 <p>查看巡检的详细信息，根据巡检配置可能包括集群资源概览、系统组件的运行情况等。</p>

en/admin/baize/best-practice/add-scheduler.html

@@ -604,16 +604,16 @@ <h3 id="enable-scheduler-plugins-in-ai-lab">Enable Scheduler Plugins in AI Lab<a
 you can easily deploy scheduler plugins in the cluster.</p>
 <!-- add screenshot later -->
 <p>Then, click <strong>Install</strong> in the top right corner.
-(If the <code>baize-agent</code> has already been deployed, you can update it in the Helm Application list.)
+(If the <code>baize-agent</code> has already been deployed, you can update it in the Helm App list.)
 Add the scheduler.</p>
 <!-- add screenshot later -->
 <p>Note the parameter hierarchy of the scheduler. After adding, click <strong>OK</strong> .</p>
 <blockquote>
 <p>Note: Do not omit this configuration when updating the <code>baize-agent</code> in the future.</p>
 </blockquote>
 <h2 id="specify-scheduler-when-creating-a-job">Specify Scheduler When Creating a Job<a class="headerlink" href="#specify-scheduler-when-creating-a-job" title="Permanent link">¶</a></h2>
-<p>Once you have successfully deployed the corresponding scheduler plugin in the cluster and
-correctly added the corresponding scheduler configuration in the <code>baize-agent</code>,
+<p>Once you have successfully deployed the proper scheduler plugin in the cluster and
+correctly added the proper scheduler configuration in the <code>baize-agent</code>,
 you can specify the scheduler when creating a job.</p>
 <p>If everything is set up correctly, you will see the scheduler plugin you deployed in the scheduler dropdown menu.</p>
 <!-- add screenshot later -->

en/admin/baize/best-practice/change-notebook-image.html

@@ -724,7 +724,7 @@ <h2 id="add-to-the-notebook-image-list-helm">Add to the Notebook Image List (Hel
 <p>Note that this must be done by the platform administrator. Be cautious with changes.</p>
 </div>
 <p>Currently, the image selector needs to be modified by updating the <code>Helm</code> parameters of <code>baize</code>. The specific steps are as follows:</p>
-<p>In the <code>Helm Applications</code> list of the kpanda-global-cluster global management cluster,
+<p>In the <code>Helm Apps</code> list of the kpanda-global-cluster global management cluster,
 find baize, enter the update page, and modify the Notebook image in the <code>YAML</code> parameters:</p>
 <p><img alt="Update Baize" src="../images/update-baize.png"/></p>
 <p>Note the parameter modification path <code>global.config.notebook_images</code>:</p>
@@ -737,7 +737,7 @@ <h2 id="add-to-the-notebook-image-list-helm">Add to the Notebook Image List (Hel
 <a href="#__codelineno-3-7" id="__codelineno-3-7" name="__codelineno-3-7"></a><span class="w">      </span><span class="l l-Scalar l-Scalar-Plain">names</span><span class="p p-Indicator">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">release.daocloud.io/baize/baize-notebook:v0.5.0</span>
 <a href="#__codelineno-3-8" id="__codelineno-3-8" name="__codelineno-3-8"></a><span class="w">      </span><span class="c1"># Add your image information here</span>
 </code></pre></div>
-<p>After the update is completed and the Helm application restarts successfully,
+<p>After the update is completed and the Helm App restarts successfully,
 you can see the new image in the Notebook creation interface image selection.</p>
 </article>
 </div>

en/admin/baize/best-practice/finetunel-llm.html

@@ -830,7 +830,7 @@ <h2 id="use-notebook-as-ide">Use Notebook as IDE<a class="headerlink" href="#use
 <p>You can use the JupyterLab Notebook provided by AI Lab for the ChatGLM3 fine-tuning task.</p>
 <h3 id="create-jupyterlab-notebook">Create JupyterLab Notebook<a class="headerlink" href="#create-jupyterlab-notebook" title="Permanent link">¶</a></h3>
 <!-- add image later -->
-<p>In the Notebook list, you can create a Notebook according to the page operation guide. Note that you need to configure the corresponding Notebook resource parameters according to the resource requirements mentioned earlier to avoid resource issues affecting the fine-tuning process.</p>
+<p>In the Notebook list, you can create a Notebook according to the page operation guide. Note that you need to configure the proper Notebook resource parameters according to the resource requirements mentioned earlier to avoid resource issues affecting the fine-tuning process.</p>
 <!-- add image later -->
 <div class="admonition note">
 <p class="admonition-title">Note</p>

en/admin/baize/developer/notebooks/baizess.html

@@ -316,7 +316,7 @@ <h3 id="command-format">Command Format<a class="headerlink" href="#command-forma
 <p>The basic format of the <code>baizess</code> command is as follows:</p>
 <div class="highlight"><pre><span></span><code><a href="#__codelineno-1-1" id="__codelineno-1-1" name="__codelineno-1-1"></a>baizess<span class="w"> </span><span class="o">[</span>command<span class="o">]</span><span class="w"> </span><span class="o">[</span>package-manager<span class="o">]</span>
 </code></pre></div>
-<p>Here,<code>[command]</code> refers to the specific operation command, and <code>[package-manager]</code> is used to specify the corresponding package manager for the operation.</p>
+<p>Here,<code>[command]</code> refers to the specific operation command, and <code>[package-manager]</code> is used to specify the proper package manager for the operation.</p>
 <h4 id="command">Command<a class="headerlink" href="#command" title="Permanent link">¶</a></h4>
 <ul>
 <li><code>set</code>：Backup the source, perform speed test, and switch the specified package manager's source to the fastest domestic source based on speed test result.</li>

en/admin/baize/developer/notebooks/notebook-auto-close.html

@@ -297,7 +297,7 @@ <h1 id="automatic-shutdown-of-idle-notebooks">Automatic Shutdown of Idle Noteboo
 </div>
 <h2 id="change-configurations">Change Configurations<a class="headerlink" href="#change-configurations" title="Permanent link">¶</a></h2>
 <p>Currently, configuration changes must be made manually, but more convenient options will be available in the future.</p>
-<p>To modify the deployment parameters of <code>baize-agent</code> in your worker cluster, update the Helm application.</p>
+<p>To modify the deployment parameters of <code>baize-agent</code> in your worker cluster, update the Helm App.</p>
 <h3 id="modify-on-ui">Modify on UI<a class="headerlink" href="#modify-on-ui" title="Permanent link">¶</a></h3>
 <ol>
 <li>

en/admin/ghippo/access-control/group.html

@@ -570,7 +570,7 @@
 <h1 id="group">Group<a class="headerlink" href="#group" title="Permanent link">¶</a></h1>
 <p>A group is a collection of users. By joining a group, a user can inherit the role permissions of the group. Authorize users in batches through groups to better manage users and their permissions.</p>
 <h2 id="use-cases">Use cases<a class="headerlink" href="#use-cases" title="Permanent link">¶</a></h2>
-<p>When a user's permission changes, it only needs to be moved to the corresponding group without affecting other users.</p>
+<p>When a user's permission changes, it only needs to be moved to the proper group without affecting other users.</p>
 <p>When the permissions of a group change, you only need to modify the role permissions of the group to apply to all users in the group.</p>
 <h2 id="create-group">Create group<a class="headerlink" href="#create-group" title="Permanent link">¶</a></h2>
 <p>Prerequisite: Admin or IAM Owner.</p>

en/admin/ghippo/access-control/iam.html

@@ -539,7 +539,7 @@ <h2 id="benefits">Benefits<a class="headerlink" href="#benefits" title="Permanen
 </li>
 <li>
 <p>Enterprise-grade access control</p>
-<p>When you want your company's employees to use the company's internal authentication system to log in to the AI platform without creating corresponding users on the AI platform, you can use the identity provider feature of access control to establish a trust relationship between your company and Suanova, Through joint authentication, employees can directly log in to the AI platform with the existing account of the enterprise, realizing single sign-on.</p>
+<p>When you want your company's employees to use the company's internal authentication system to log in to the AI platform without creating proper users on the AI platform, you can use the identity provider feature of access control to establish a trust relationship between your company and Suanova, Through joint authentication, employees can directly log in to the AI platform with the existing account of the enterprise, realizing single sign-on.</p>
 </li>
 </ul>
 <h2 id="usage-process">Usage Process<a class="headerlink" href="#usage-process" title="Permanent link">¶</a></h2>

en/admin/ghippo/access-control/ldap.html

@@ -583,7 +583,7 @@ <h1 id="ldap">LDAP<a class="headerlink" href="#ldap" title="Permanent link">¶</
 </tr>
 <tr>
 <td>Full name mapping</td>
-<td>Corresponding First name and Last Name</td>
+<td>proper First name and Last Name</td>
 </tr>
 <tr>
 <td>User Name Mapping</td>

en/admin/ghippo/access-control/oauth2.0.html

@@ -431,9 +431,9 @@
 </a>
 </li>
 <li class="md-nav__item">
-<a class="md-nav__link" href="#corresponding-fields-in-wecom">
+<a class="md-nav__link" href="#proper-fields-in-wecom">
 <span class="md-ellipsis">
-      Corresponding fields in WeCom
+      proper fields in WeCom
     </span>
 </a>
 </li>
@@ -549,9 +549,9 @@
 </a>
 </li>
 <li class="md-nav__item">
-<a class="md-nav__link" href="#corresponding-fields-in-wecom">
+<a class="md-nav__link" href="#proper-fields-in-wecom">
 <span class="md-ellipsis">
-      Corresponding fields in WeCom
+      proper fields in WeCom
     </span>
 </a>
 </li>
@@ -580,7 +580,7 @@ <h2 id="steps">Steps<a class="headerlink" href="#steps" title="Permanent link">
 <p><img alt="Oauth2.0" src="../images/oauth2.png"/></p>
 </li>
 </ol>
-<h2 id="corresponding-fields-in-wecom">Corresponding fields in WeCom<a class="headerlink" href="#corresponding-fields-in-wecom" title="Permanent link">¶</a></h2>
+<h2 id="proper-fields-in-wecom">proper fields in WeCom<a class="headerlink" href="#proper-fields-in-wecom" title="Permanent link">¶</a></h2>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Before integration, you need to create a custom application in the WeCom management console. Refer to

en/admin/ghippo/access-control/role.html

@@ -645,7 +645,7 @@ <h1 id="role-and-permission-management">Role and Permission Management<a class="
 <li><a href="#folder-roles">Folder Roles</a></li>
 </ul>
 <h2 id="platform-roles">Platform Roles<a class="headerlink" href="#platform-roles" title="Permanent link">¶</a></h2>
-<p>Platform roles are coarse-grained permissions that grant corresponding permissions to
+<p>Platform roles are coarse-grained permissions that grant proper permissions to
 all relevant resources on the platform. By assigning platform roles, users can have
 permissions to create, delete, modify, and view all clusters and workspaces, but not
 specifically to a particular cluster or workspace. AI platform provides 5 pre-defined
@@ -680,7 +680,7 @@ <h3 id="platform-role-authorization-methods">Platform Role Authorization Methods
 <p><img alt="Add permissions" src="https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/ghippo/images/newrole04.png"/></p>
 </li>
 <li>
-<p>In the <strong>Global Management</strong> -&gt; <strong>Access Control</strong> -&gt; <strong>Roles</strong> section, find the corresponding platform role
+<p>In the <strong>Global Management</strong> -&gt; <strong>Access Control</strong> -&gt; <strong>Roles</strong> section, find the proper platform role
   in the role list, click the role name to access details, click the <strong>Related Members</strong> button, select the user or group, and click <strong>OK</strong> .</p>
 <p><img alt="Related Members Button" src="https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/ghippo/images/newrole05.png"/></p>
 </li>
@@ -718,7 +718,7 @@ <h2 id="folder-roles">Folder Roles<a class="headerlink" href="#folder-roles" tit
 in enterprises. For example, User B is a leader of a first-level department and usually has management
 permissions over the first-level department, all second-level departments under it, and projects within
 those departments. In this scenario, User B is granted admin permissions for the first-level folder,
-which also grants corresponding permissions for the second-level folders and workspaces below them.
+which also grants proper permissions for the second-level folders and workspaces below them.
 AI platform provides 3 pre-defined folder roles that users can directly use:</p>
 <ul>
 <li>Folder Admin</li>

en/admin/ghippo/access-control/user.html

@@ -584,7 +584,7 @@
 <h1 id="user">User<a class="headerlink" href="#user" title="Permanent link">¶</a></h1>
 <p>A user refers to a user created by the platform administrator Admin or the access control administrator IAM Owner on the <strong>Global Management</strong> -&gt; <strong>Access Control</strong> -&gt; <strong>Users</strong> page, or a user connected through LDAP / OIDC .
 The username represents the account, and the user logs in to the Suanova Enterprise platform through the username and password.</p>
-<p>Having a user account is a prerequisite for users to access the platform. The newly created user does not have any permissions by default. For example, you need to assign corresponding role permissions to users, such as granting administrator permissions to submodules in <strong>User List</strong> or <strong>User Details</strong> .
+<p>Having a user account is a prerequisite for users to access the platform. The newly created user does not have any permissions by default. For example, you need to assign proper role permissions to users, such as granting administrator permissions to submodules in <strong>User List</strong> or <strong>User Details</strong> .
 The sub-module administrator has the highest authority of the sub-module, and can create, manage, and delete all resources of the module.
 If a user needs to be granted permission for a specific resource, such as the permission to use a certain resource, please see <a href="#authorize-for-user">Resource Authorization Description</a>.</p>
 <p>This page introduces operations such as creating, authorizing, disabling, enabling, and deleting users.</p>

en/admin/ghippo/audit/open-audit.html

@@ -742,9 +742,9 @@ <h4 id="enable-collection-of-k8s-audit-logs">Enable Collection of K8s Audit Logs
 <p><img alt="Select Cluster" src="https://docs.daocloud.io/daocloud-docs-images/docs/ghippo/images/worker04.png"/></p>
 </li>
 <li>
-<p>Go to the Helm application management page and update the insight-agent configuration (if insight-agent is not installed, 
+<p>Go to the Helm App management page and update the insight-agent configuration (if insight-agent is not installed, 
    you can <a href="../../insight/quickstart/install/install-agent.html">install it</a>).</p>
-<p><img alt="Go to Helm Applications" src="https://docs.daocloud.io/daocloud-docs-images/docs/ghippo/images/worker05.png"/></p>
+<p><img alt="Go to Helm Apps" src="https://docs.daocloud.io/daocloud-docs-images/docs/ghippo/images/worker05.png"/></p>
 </li>
 <li>
 <p>Enable/Disable the collection of K8s audit logs switch.</p>

en/admin/ghippo/best-practice/gproduct/nav.html

@@ -602,7 +602,7 @@ <h2 id="docking-method">Docking method<a class="headerlink" href="#docking-metho
 <p>The <code>kpanda</code> front-end is integrated into the AI platform parent application <code>Anakin</code> as a micro-frontend.</p>
 <p>AI platform frontend uses <a href="https://qiankun.umijs.org">qiankun</a> to connect the sub-applications UI.
 See <a href="https://qiankun.umijs.org/guide/getting-started">getting started</a>.</p>
-<p>After registering the GProductNavigator CR, the corresponding registration information will be generated for the front-end parent application. For example, <code>kpanda</code> will generate the following registration information:</p>
+<p>After registering the GProductNavigator CR, the proper registration information will be generated for the front-end parent application. For example, <code>kpanda</code> will generate the following registration information:</p>
 <div class="highlight"><pre><span></span><code><a href="#__codelineno-1-1" id="__codelineno-1-1" name="__codelineno-1-1"></a><span class="p">{</span>
 <a href="#__codelineno-1-2" id="__codelineno-1-2" name="__codelineno-1-2"></a><span class="w">  </span><span class="s">"id"</span><span class="p">:</span><span class="w"> </span><span class="s">"kpanda"</span><span class="p">,</span>
 <a href="#__codelineno-1-3" id="__codelineno-1-3" name="__codelineno-1-3"></a><span class="w">  </span><span class="s">"title"</span><span class="p">:</span><span class="w"> </span><span class="s">"容器管理"</span><span class="p">,</span>
@@ -611,7 +611,7 @@ <h2 id="docking-method">Docking method<a class="headerlink" href="#docking-metho
 <a href="#__codelineno-1-6" id="__codelineno-1-6" name="__codelineno-1-6"></a><span class="w">  </span><span class="s">"needImportLicense"</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span>
 <a href="#__codelineno-1-7" id="__codelineno-1-7" name="__codelineno-1-7"></a><span class="p">},</span>
 </code></pre></div>
-<p>The corresponding relation between the above registration and the qiankun sub-application fields is:</p>
+<p>The proper relation between the above registration and the qiankun sub-application fields is:</p>
 <div class="highlight"><pre><span></span><code><a href="#__codelineno-2-1" id="__codelineno-2-1" name="__codelineno-2-1"></a><span class="p p-Indicator">{</span>
 <a href="#__codelineno-2-2" id="__codelineno-2-2" name="__codelineno-2-2"></a><span class="nt">    name</span><span class="p">:</span><span class="w"> </span><span class="nv">id</span><span class="p p-Indicator">,</span>
 <a href="#__codelineno-2-3" id="__codelineno-2-3" name="__codelineno-2-3"></a><span class="nt">    entry</span><span class="p">:</span><span class="w"> </span><span class="nv">uiAssetsUrl</span><span class="p p-Indicator">,</span>

en/admin/ghippo/best-practice/ws-best-practice.html

@@ -625,7 +625,7 @@ <h2 id="workspace-features">Workspace features<a class="headerlink" href="#works
 <p>Best practice: The operation and maintenance department has a high-availability cluster 01, and wants to allocate it to department A (workspace A) and department B (workspace B), where department A allocates 50 CPU cores, and department B allocates CPU 100 cores.
 Then you can borrow the concept of shared resources, share cluster 01 with department A and department B respectively, and limit the CPU usage quota of department A to 50, and the CPU usage quota of department B to 100.
 Then the administrator of department A (workspace A Admin) can create and use a namespace in Workbench, and the sum of the namespace quotas cannot exceed 50 cores, and the administrator of department B (workspace B Admin) can create a namespace in Workbench And use namespaces, where the sum of namespace credits cannot exceed 100 cores.
-The namespaces created by the administrators of department A and department B will be automatically bound to the department, and other members of the department will have the roles of Namesapce Admin, Namesapce Edit, and Namesapce View corresponding to the namespace (the department here refers to Workspace, workspace can also be mapped to other concepts such as organization, and supplier). The whole process is as follows:</p>
+The namespaces created by the administrators of department A and department B will be automatically bound to the department, and other members of the department will have the roles of Namesapce Admin, Namesapce Edit, and Namesapce View proper to the namespace (the department here refers to Workspace, workspace can also be mapped to other concepts such as organization, and supplier). The whole process is as follows:</p>
 <table>
 <thead>
 <tr>