fix: submitting typo

Author: Peefy

docs/user_docs/guides/ci-integration/1-github-actions.md

@@ -94,7 +94,7 @@ We need the workflow in the source code repository to automatically trigger the
 
 ### 2. Commit the Application Code
 
-After submiting in the `flask-demo` repository, Github will automatically build a container image and push it to the Docker hub. It will also then trigger the Action of the `flask-demo-kcl-manifest` repository and modify the image value in the deployment manifest repository through [KCL Automation API](/docs/user_docs/guides/automation). Now let's create a submission in the `flask-demo` repository, and we can see that the code submission triggers the Github CI process for the application repository.
+After submitting in the `flask-demo` repository, Github will automatically build a container image and push it to the Docker hub. It will also then trigger the Action of the `flask-demo-kcl-manifest` repository and modify the image value in the deployment manifest repository through [KCL Automation API](/docs/user_docs/guides/automation). Now let's create a submission in the `flask-demo` repository, and we can see that the code submission triggers the Github CI process for the application repository.
 
 ![](/img/docs/user_docs/guides/ci-integration/app-ci.png)
 

versioned_docs/version-0.5.0/user_docs/guides/ci-integration/1-github-actions.md

@@ -94,7 +94,7 @@ We need the workflow in the source code repository to automatically trigger the
 
 ### 2. Commit the Application Code
 
-After submiting in the `flask-demo` repository, Github will automatically build a container image and push it to the Docker hub. It will also then trigger the Action of the `flask-demo-kcl-manifest` repository and modify the image value in the deployment manifest repository through [KCL Automation API](/docs/user_docs/guides/automation). Now let's create a submission in the `flask-demo` repository, and we can see that the code submission triggers the Github CI process for the application repository.
+After submitting in the `flask-demo` repository, Github will automatically build a container image and push it to the Docker hub. It will also then trigger the Action of the `flask-demo-kcl-manifest` repository and modify the image value in the deployment manifest repository through [KCL Automation API](/docs/user_docs/guides/automation). Now let's create a submission in the `flask-demo` repository, and we can see that the code submission triggers the Github CI process for the application repository.
 
 ![](/img/docs/user_docs/guides/ci-integration/app-ci.png)