fix grep command error (#769)

Author: leto-b

src/UserGuide/Master/Tree/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -397,7 +397,7 @@ sbin/remove-datanode.bat [datanode_id]
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/Master/Tree/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md

@@ -161,7 +161,7 @@ When the status is all running, it indicates that the service has started succes
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -397,7 +397,7 @@ sbin/remove-datanode.bat [datanode_id]
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/V1.3.x/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -442,7 +442,7 @@ sbin/remove-datanode.bat [datanode_id]
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md

@@ -161,7 +161,7 @@ When the status is all running, it indicates that the service has started succes
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/V1.3.x/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md

@@ -203,7 +203,7 @@ When you see the display "Activated" on the far right, it indicates successful a
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -388,7 +388,7 @@ remove datanode [datanode_id]
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/dev-1.3/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -429,7 +429,7 @@ remove datanode [datanode_id]
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md

@@ -161,7 +161,7 @@ When the status is all running, it indicates that the service has started succes
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>

src/UserGuide/dev-1.3/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md

@@ -203,7 +203,7 @@ When you see the display "Activated" on the far right, it indicates successful a
       # 2. Check for any remaining processes
       jps
       # Or
-      ps -ef|gerp iotdb
+      ps -ef|grep iotdb
 
       # 3. If there are any remaining processes, manually kill the
       kill -9 <pid>