diff --git a/docs/jenkins.md b/docs/jenkins.md
index ac696242..a11020d2 100644
--- a/docs/jenkins.md
+++ b/docs/jenkins.md
@@ -59,11 +59,6 @@
* [opensource.com: Getting started with Jenkins Configuration as Code πππ](https://opensource.com/article/20/4/getting-started-jcasc-jenkins) JCasC uses YAML formats to set up Jenkins configurations.
* [opensource.com: Jenkins Pipeline as Code Tutorial For Beginners πππ](https://devopscube.com/jenkins-pipeline-as-code/)
-## Cloudbees Flow
-* [**Cloudbees Flow** πππ](https://www.cloudbees.com/products/flow/overview)
-
-
-
## Jenkins Cheat Sheet
* [edureka.co: Jenkins Cheat Sheet ππππ](https://www.edureka.co/blog/cheatsheets/jenkins-cheat-sheet/)
* [medium: Jenkins Cheat Sheet](https://medium.com/edureka/jenkins-cheat-sheet-e0f7e25558a3)
@@ -141,6 +136,11 @@
* [20 Jenkins Plugins You Canβt Live Without](https://caylent.com/jenkins-plugins)
* [youtube - CloudBeesTV: Jenkins Performance: Avoiding Pitfalls, Diagnosing Issues & Scaling for Growth](https://www.youtube.com/watch?v=yTafQ-e84eY)
+## Cloudbees Flow
+* [**Cloudbees Flow** πππ](https://www.cloudbees.com/products/flow/overview)
+
+
+
## Jenkins X
Jenkins X is a specialized Jenkins for Kubernetes: This is how it works from a bird eye the CI/CD: a developer creates a branch, then Jenkins X creates a ephemeral namespace with that branch. The developer tests it and once it is ok, a PR is created, then, the branch is deployed in staging. When I merge it, it goes to QA, and with a manual command "jx promote" it goes to production. Jenkins X deletes automatically after N hours the branch namespace.