[camel-website] 03/29: Update content/blog/2022/10/camel-k-cicd/index.md

[pc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit 576c91d611e3f5549c86a754b7663c0b6124c63a
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu Oct 6 11:09:26 2022 +0200

    Update content/blog/2022/10/camel-k-cicd/index.md
    
    Co-authored-by: Zoran Regvart <zo...@regvart.com>
---
 content/blog/2022/10/camel-k-cicd/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2022/10/camel-k-cicd/index.md b/content/blog/2022/10/camel-k-cicd/index.md
index 99088b9c..5b7943f2 100644
--- a/content/blog/2022/10/camel-k-cicd/index.md
+++ b/content/blog/2022/10/camel-k-cicd/index.md
@@ -14,7 +14,7 @@ The application I'm building is a REST API backed by a PostgreSQL database. It w
   1. checkout the code repository with the latest changes,
   2. release the Integration in a development environment,
   3. run a complete suite of automated test,
-  4. promote to production environment and 
+  4. promote to production environment and
   5. run some smoke test on the production endpoints as last check stage.
 
 It should sound quite a familiar development process. We may just need to implement the first 3 tasks as a basic **Continuous Integration**, but, given the presence of `kamel promote` we can easily extend it to a CD pipeline. But that's not all. As an additional feature we're finally reusing the CD to enable a **Continuous Deployment** process triggering the pipeline when any change is pushed to the repo. Your journey from code to production has never been that fast!!