Merge pull request #88 from sophongo/fixhtt

remove the word of daocloud
sophongo · Nov 18, 2024 · a710b7d · a710b7d
2 parents bea70df + 0b1520a
commit a710b7d
Show file tree

Hide file tree

Showing 9 changed files with 11 additions and 13 deletions.
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -1,5 +1,5 @@
 ---
-name: "\U0001F6D1 Report a bug in the DaoCloud Enterprise Documents"
+name: "\U0001F6D1 Report a bug in the Documents"
 about: Create a report to help us improve
 title: ''
 labels: bug

diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: ✅ Connect US when your having questions.
-    url: https://www.daocloud.io
-    about: If you have questions about DaoCloud product or need support building applicaion, please ask us
+    url: https://sophongo.github.io/sophdoc/
+    about: If you have questions about product or need support building applicaion, please ask us
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -1,6 +1,6 @@
 ---
-name: "\U0001F7E1 Request a feature in the DaoCloud Enterprise Documents"
-about: If you have feature idea for DaoCloud Enterprise Documents
+name: "\U0001F7E1 Request a feature in the Documents"
+about: If you have feature idea for Documents
 title: ''
 labels: enhancement
 assignees: ''

diff --git a/docs/en/admin/baize/best-practice/change-notebook-image.md b/docs/en/admin/baize/best-practice/change-notebook-image.md
@@ -5,7 +5,7 @@ In most cases, this will meet the developers' needs.
 
 ![Creating notebook interface](../images/notebook-images.png)
 
-DaoCloud provides a default Notebook image that contains all necessary development tools and resources.
+This AI platform provides a default Notebook image that contains all necessary development tools and resources.
 
 ```markdown
 baize/baize-notebook
@@ -21,7 +21,7 @@ This Notebook includes basic development tools. Taking `baize-notebook:v0.5.0` (
 | conda(mamba)  | 23.3.1   |                                                           |
 | jupyterlab    | 3.6.6    | JupyterLab image, providing a complete Notebook experience |
 | codeserver    | v4.89.1  | Mainstream Code development tool for a familiar experience |
-| *baizectl     | v0.5.0   | DaoCloud built-in CLI task management tool                |
+| *baizectl     | v0.5.0   | A built-in CLI task management tool                |
 | *SSH          | -        | Supports local SSH direct access to the Notebook container |
 | *kubectl      | v1.27    | Kubernetes CLI for managing container resources within Notebook |
 

diff --git a/docs/en/admin/kpanda/namespaces/createns.md b/docs/en/admin/kpanda/namespaces/createns.md
@@ -27,7 +27,7 @@ Supports easy creation of namespaces through forms, and quick creation of namesp
 
     !!! info
 
-        - After binding a namespace to a workspace, the resources of that namespace will be shared with the bound workspace. For a detailed explanation of workspaces, refer to [Workspaces and Hierarchies](../../../ghippo/workspace/workspace.md).
+        - After binding a namespace to a workspace, the resources of that namespace will be shared with the bound workspace. For a detailed explanation of workspaces, refer to [Workspaces and Folders](../../ghippo/workspace/workspace.md).
 
         - After the namespace is created, you can still bind/unbind the workspace.
 

diff --git a/docs/en/admin/kpanda/workloads/create-daemonset.md b/docs/en/admin/kpanda/workloads/create-daemonset.md
@@ -7,7 +7,7 @@ Date: 2024-02-28
 
 This page introduces how to create a daemonSet through image and YAML files.
 
-DaemonSet is connected to [taint](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) through [node affinity]( ://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) feature ensures that a replica of a Pod is running on all or some of the nodes. For nodes that newly joined the cluster, DaemonSet automatically deploys the proper Pod on the new node and tracks the running status of the Pod. When a node is removed, the DaemonSet deletes all Pods it created.
+DaemonSet is connected to [taint](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) through [node affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) feature ensures that a replica of a Pod is running on all or some of the nodes. For nodes that newly joined the cluster, DaemonSet automatically deploys the proper Pod on the new node and tracks the running status of the Pod. When a node is removed, the DaemonSet deletes all Pods it created.
 
 Common cases for daemons include:
 

diff --git a/docs/en/end-user/kpanda/namespaces/createns.md b/docs/en/end-user/kpanda/namespaces/createns.md
@@ -27,7 +27,7 @@ Supports easy creation of namespaces through forms, and quick creation of namesp
 
     !!! info
 
-        - After binding a namespace to a workspace, the resources of that namespace will be shared with the bound workspace. For a detailed explanation of workspaces, refer to [Workspaces and Hierarchies](../../../ghippo/workspace/workspace.md).
+        - After binding a namespace to a workspace, the resources of that namespace will be shared with the bound workspace. For a detailed explanation of workspaces, refer to [Workspaces and Folders](../../ghippo/workspace/workspace.md).
 
         - After the namespace is created, you can still bind/unbind the workspace.
 

diff --git a/docs/en/end-user/kpanda/workloads/create-daemonset.md b/docs/en/end-user/kpanda/workloads/create-daemonset.md
@@ -7,7 +7,7 @@ Date: 2024-02-28
 
 This page introduces how to create a daemonSet through image and YAML files.
 
-DaemonSet is connected to [taint](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) through [node affinity]( ://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) feature ensures that a replica of a Pod is running on all or some of the nodes. For nodes that newly joined the cluster, DaemonSet automatically deploys the proper Pod on the new node and tracks the running status of the Pod. When a node is removed, the DaemonSet deletes all Pods it created.
+DaemonSet is connected to [taint](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) through [node affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) feature ensures that a replica of a Pod is running on all or some of the nodes. For nodes that newly joined the cluster, DaemonSet automatically deploys the proper Pod on the new node and tracks the running status of the Pod. When a node is removed, the DaemonSet deletes all Pods it created.
 
 Common cases for daemons include:
 

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -80,8 +80,6 @@ theme:
 # Plugins
 plugins:
   search:
-    jieba_dict: dict.txt.small
-    jieba_dict_user: dict.txt.daocloud
     lang:
       zh
       en