Merge pull request #48713 from mo3et/main

docs(zh-cn): update clusters intro contents and hide interactive page in TOC

content/zh-cn/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html

@@ -70,7 +70,7 @@ description: |-
                         <li><b>Nodes</b> are the workers that run applications</li>
                         -->
                         <li><b>控制面</b>调度整个集群</li>
-                        <li><b>节点</b>负责运行应用</li>
+                        <li><b>节点（Nodes）</b>负责运行应用</li>
                     </ul>
                 </p>
             </div>
@@ -126,13 +126,13 @@ description: |-
                 <p><b>控制面负责管理整个集群。</b> 
                 控制面协调集群中的所有活动，例如调度应用、维护应用的所需状态、应用扩容以及推出新的更新。</p>
                 <!--
-                <b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an <a href="/docs/concepts/overview/components/#etcd">etcd</a> member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.
+                <b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as {{< glossary_tooltip text="containerd" term_id="containerd" >}} or {{< glossary_tooltip term_id="cri-o" >}}. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an <a href="/docs/concepts/architecture/#etcd">etcd</a> member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.
                 -->
                 <p><b>节点是一个虚拟机或者物理机，它在 Kubernetes 集群中充当工作机器的角色。</b>
                 每个节点都有 Kubelet，它管理节点而且是节点与控制面通信的代理。
-                节点还应该具有用于​​处理容器操作的工具，例如 Docker 或 rkt。
-                处理生产级流量的 Kubernetes 集群至少应具有三个节点，因为如果一个节点出现故障其对应的
-                <a href="/zh-cn/docs/concepts/overview/components/#etcd">etcd</a> 成员和控制面实例都会丢失，
+                节点还应该具有用于​​处理容器操作的工具，例如 {{< glossary_tooltip text="containerd" term_id="containerd" >}} 或 {{< glossary_tooltip term_id="cri-o" >}}。
+                处理生产级流量的 Kubernetes 集群至少应具有三个节点，因为如果只有一个节点，出现故障时其对应的
+                <a href="/zh-cn/docs/concepts/architecture/#etcd">etcd</a> 成员和控制面实例都会丢失，
                 并且冗余会受到影响。你可以通过添加更多控制面节点来降低这种风险。</p>
 
             </div>
@@ -168,8 +168,8 @@ description: |-
                 Now that you know more about what Kubernetes is, visit <a href="/docs/tutorials/hello-minikube/">Hello Minikube</a>
                 to try this out on your computer.
                 -->
-                <p>既然你已经知道 Kubernetes 是什么，访问<a href="/zh-cn/docs/tutorials/hello-minikube/">你好 Minikube</a>，
-                在你的电脑上试试这个。</p>
+                <p>现在你已经知道 Kubernetes 是什么了，在你的电脑上访问<a href="/zh-cn/docs/tutorials/hello-minikube/">你好 Minikube</a>，
+                试试。</p>
 
             </div>
         </div>

content/zh-cn/docs/tutorials/kubernetes-basics/explore/explore-interactive-gone.html

@@ -1,6 +1,8 @@
 ---
 title: 交互式教程 - 探索你的应用
 weight: 20
+headless: true
+toc_hide: true
 ---
 <!--
 title: Interactive Tutorial - Exploring Your App

content/zh-cn/docs/tutorials/kubernetes-basics/update/update-interactive-gone.html

@@ -1,6 +1,8 @@
 ---
 title: 交互式教程 - 更新你的应用
 weight: 20
+headless: true
+toc_hide: true
 ---
 <!--
 ---