fix: display tabs for GitHub + GitLab with Argo Workflows (fix #76) (#…

…395)

docs/common/gitops.mdx

@@ -25,20 +25,24 @@ The pipelines then continue with promotion of the release through the `preprod`
 
 Once the release is ready, the release chart is published and delivered to production, and the application chart's version will be prepared for the next release.
 
-### GitHub Integration with Argo Workflows
+<!--tabs-->
+
+# GitHub Integration with Argo Workflows
 
 ![Argo Workflows with GitHub](../img/kubefirst/github/github-argo-workflow.png)
 
 The integration that we've established between GitHub and Argo Workflows will surface your powerful Argo Workflows engine directly in GitHub Actions, so that your developers have all of the workflow execution information available, directly associated with their commit in their application repository.
 
-### GitLab Integration with Argo Workflows
+# GitLab Integration with Argo Workflows
 
 ![Argo Workflows Integration with GitLab](../img/kubefirst/gitops/gitlab-workflows-integration.png)
 
 The integration that we've established between GitLab and Argo Workflows will surface your powerful Argo Workflows engine directly in GitLab's native CI, so that your developers have all of the workflow execution information available directly associated with their commit in their application repository.
 
 ![Argo Workflows with GitLab](../img/kubefirst/gitlab/gitlab-argo-workflow.png)
 
+<!--/tabs-->
+
 ## GitOps Resources
 
 Our registry includes GitOps patterns for numerous source types including: