fix: video spacing

content/docs/14.best-practices/1.from-dev-to-prod.md

@@ -85,6 +85,8 @@ While we can be sure that our flows are valid, this will not check for logical e
   <iframe src="https://www.youtube.com/embed/4MqtD9VtGVs?si=6yuJkPkq29SzKy_r" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 </div>
 
+---
+
 We can use CI/CD to automatically deploy our flows from our Git repository to our production instance of Kestra when they are merged to the `main` branch. 
 
 With GitHub, we can use the official [Deploy Action](../version-control-cicd/cicd/01.github-action.md#kestra-actions), which uses the Kestra Server CLI under the hood, to deploy when a Pull Request is merged to `main`.

content/docs/14.best-practices/6.git.md

@@ -14,6 +14,8 @@ However, if you want to use Git to track changes to your [Flows](../04.workflow-
     <iframe src="https://www.youtube.com/embed/videoseries?si=wOyAUkgChRUuJxcy&amp;list=PLEK3H8YwZn1p7tyd9RV5-WDxh_ZGpMpA3" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 </div>
 
+---
+
 There are multiple ways to use Git with Kestra:
 - The [git.SyncFlows](/plugins/plugin-git/tasks/io.kestra.plugin.git.syncflows) pattern allows you to implement GitOps and use Git as a single source of truth for your flows.
 - The [git.SyncNamespaceFiles](/plugins/plugin-git/tasks/io.kestra.plugin.git.syncnamespacefiles) pattern allows you to implement GitOps and use Git as a single source of truth for your namespace files.