test

docs/developer/local_up_kubeedge.md

@@ -1,5 +1,5 @@
 ---
-title: Kubeedge local up script guide
+title: Kubeedge Local Up
 sidebar_position: 10
 ---
 
@@ -30,24 +30,17 @@ hack/local_up_kubeedge.sh
 ```
 This script will run the environment setting, prerequesites verification, installation and so on. For details, please refer [Script Analysis](#script-analysis)
 
-3. Checking the Running Status:
-After the script completes, you can use kubectl commands to check the status of the cluster's nodes and the running status of KubeEdge components.
-
-```shell
-healthcheck
-kubectl get nodes | grep edge-node | grep -q -w Ready && break
-```
-
-4. Debugging and Log Viewing:
+3. Debugging and Log Viewing:
 If problems occur, you can view the log files generated by the script, typically located at 
 
 ```shell
 /tmp/cloudcore.log and
 /tmp/edgecore.log
 ```
 
-5. Shutting Down the Cluster:
-If the cluster is no longer needed, you can use the cleanup function provided in the script to stop and clean up the cluster and related resources.
+4. Shutting Down the Cluster:
+If the cluster is no longer needed, user can press **ctrl+c** to terminate the script and 
+call the cleanup function to clean up the environment.
 
 ```shell
 cleanup
@@ -92,6 +85,7 @@ source "${KUBEEDGE}/hack/lib/install.sh"
 ```
 
 Depending on the chosen container runtime type, verifies if the related tools are already installed.
+If user does not set runtime container, containerd will be used by default.
 
 ```shell
 install_docker
@@ -101,6 +95,7 @@ install_isulad
 
 For each installation, the script will verify whether the installation is successful. 
 
+
 ```shell
 verify_docker_installed
 verify_crio_installed
@@ -168,6 +163,8 @@ Regularly checks the running status of CloudCore and EdgeCore and provides clean
 healthcheck
 kubectl get nodes | grep edge-node | grep -q -w Ready && break
 ```
+Health check is generally used inside this script. For user, they could use k8s API to check the health status.
+
 
 **Note：**
 For CloudCore, EdgeCore and some related services, the module installation processes are detailed in `hack/lib/install.sh`