fix numbering

Signed-off-by: Felixnoo <felixliu@kubesphere.io>

content/en/docs/devops-user-guide/how-to-use/create-a-pipeline-using-graphical-editing-panel.md

@@ -294,7 +294,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
 
 3. Click **Add Step** under the **Deploy to Dev** stage again. Select **container** from the list, name it `maven`, and click **OK**.
 
-3. Click **Add Nesting Steps** in the `maven` container step. Select **withCredentials** from the list, fill in the following fields in the displayed dialog box, and click **OK**.
+4. Click **Add Nesting Steps** in the `maven` container step. Select **withCredentials** from the list, fill in the following fields in the displayed dialog box, and click **OK**.
 
    - **Credential Name**: Select the kubeconfig credential you created, such as `demo-kubeconfig`.
    - **Kubeconfig Variable**: Enter `KUBECONFIG_CONTENT`.
@@ -308,7 +308,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
    envsubst < deploy/dev-ol/devops-sample.yaml | kubectl apply -f -
    ```
 
-4. If you want to receive email notifications when the pipeline runs successfully, click **Add Step** and select **mail** to add email information. Note that configuring the email server is optional, which means you can still run your pipeline if you skip this step.
+6. If you want to receive email notifications when the pipeline runs successfully, click **Add Step** and select **mail** to add email information. Note that configuring the email server is optional, which means you can still run your pipeline if you skip this step.
 
    {{< notice note >}}
 
@@ -316,7 +316,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
 
    {{</ notice >}} 
 
-5. When you finish the steps above, click **Save** in the lower-right corner. You can see the pipeline now has a complete workflow with each stage clearly listed on the pipeline. When you define a pipeline using the graphical editing panel, KubeSphere automatically creates its corresponding Jenkinsfile. Click **Edit Jenkinsfile** to view the Jenkinsfile.
+7. When you finish the steps above, click **Save** in the lower-right corner. You can see the pipeline now has a complete workflow with each stage clearly listed on the pipeline. When you define a pipeline using the graphical editing panel, KubeSphere automatically creates its corresponding Jenkinsfile. Click **Edit Jenkinsfile** to view the Jenkinsfile.
 
    {{< notice note >}}
    

content/zh/docs/devops-user-guide/how-to-use/create-a-pipeline-using-graphical-editing-panel.md

@@ -294,7 +294,7 @@ KubeSphere 中的图形编辑面板包含用于 Jenkins [阶段 (Stage)](https:/
 
 3. 再次点击 **Deploy to Dev** 阶段下的**添加步骤**。在列表中选择**指定容器**，将其命名为 `maven` 然后点击**确定**。
 
-3. 点击 `maven` 容器步骤下的**添加嵌套步骤**。在列表中选择**添加凭证**，在弹出的对话框中填写以下字段，然后点击**确定**。
+4. 点击 `maven` 容器步骤下的**添加嵌套步骤**。在列表中选择**添加凭证**，在弹出的对话框中填写以下字段，然后点击**确定**。
 
    - 凭证名称：选择您创建的 kubeconfig 凭证，例如 `demo-kubeconfig`。
    - kubeconfig 变量：输入 `KUBECONFIG_CONTENT`。
@@ -308,7 +308,7 @@ KubeSphere 中的图形编辑面板包含用于 Jenkins [阶段 (Stage)](https:/
    envsubst < deploy/dev-ol/devops-sample.yaml | kubectl apply -f -
    ```
 
-4. 如果您想在流水线成功运行时接收电子邮件通知，请点击**添加步骤**，选择**邮件**，以添加电子邮件信息。请注意，配置电子邮件服务器是可选操作，如果您跳过该步骤，依然可以运行流水线。
+6. 如果您想在流水线成功运行时接收电子邮件通知，请点击**添加步骤**，选择**邮件**，以添加电子邮件信息。请注意，配置电子邮件服务器是可选操作，如果您跳过该步骤，依然可以运行流水线。
 
    {{< notice note >}}
 
@@ -316,7 +316,7 @@ KubeSphere 中的图形编辑面板包含用于 Jenkins [阶段 (Stage)](https:/
 
    {{</ notice >}} 
 
-5. 待您完成上述步骤，请在右下角点击**保存**。随后，您可以看到该流水线有完整的工作流，并且每个阶段也清晰列示。当您用图形编辑面板定义流水线时，KubeSphere 会自动创建相应的 Jenkinsfile。点击**编辑 Jenkinsfile** 查看该 Jenkinsfile。
+7. 待您完成上述步骤，请在右下角点击**保存**。随后，您可以看到该流水线有完整的工作流，并且每个阶段也清晰列示。当您用图形编辑面板定义流水线时，KubeSphere 会自动创建相应的 Jenkinsfile。点击**编辑 Jenkinsfile** 查看该 Jenkinsfile。
 
    {{< notice note >}}