fix tab syntax (#154)

Author: rosieyohannan

docs/guides/modules/config-policies/pages/config-policies-for-self-hosted-runner.adoc

@@ -88,7 +88,10 @@ You can now push your new policy to your organization for it to take effect. You
 * Push the policy manually using the CLI from your local environment
 * Push your changes to your config policy repository if you are xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[managing policies via your VCS].
 
-[tab.allow.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -106,13 +109,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
-
-[tab.allow.push_to_vcs]
+Push to VCS::
++
 --
 If you have set up your config policies repository with the sample configuration shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Create and manage config policies guide], push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 NOTE: If you would like to write tests for your policy, check out the xref:test-config-policies.adoc[Test config policies] guide.
 

docs/guides/modules/config-policies/pages/create-and-manage-config-policies.adoc

@@ -216,7 +216,10 @@ You can now push your new policy to your organization for it to take effect. You
 * Push the policy manually using the CLI from your local environment
 * Push your changes to your config policy repository if you are managing policies via your VCS as shown <<manage-policies-with-your-vcs,above>>.
 
-[tab.allow.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -234,13 +237,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
-
-[tab.allow.push_to_vcs]
+Push to VCS::
++
 --
 If you have set up your config policies with the sample configuration shown <<manage-policies-with-your-vcs,above>>, push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 Now, when a pipeline is triggered within your organization, the project's `.circleci/config.yml` will be validated against this policy.
 
@@ -261,7 +265,10 @@ To illustrate making a change to an existing policy, suppose you made an error w
 
 . Push the policy directory containing the updated policy:
 +
-[tab.change.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -279,13 +286,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
+Push to vcs::
 +
-[tab.change.push_to_vcs]
 --
 Push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 [#next-steps]
 == Next steps

docs/guides/modules/config-policies/pages/manage-contexts-with-config-policies.adoc

@@ -134,7 +134,10 @@ You can now push your new policy to your organization for it to take effect. You
 * Push the policy manually using the CLI from your local environment
 * Push your changes to your config policy repository if you are managing policies via your VCS as shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide].
 
-[tab.allow.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -152,13 +155,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
-
-[tab.allow.push_to_vcs]
+Push to VCS::
++
 --
 If you have set up your config policies repository with the sample configuration shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide], push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 NOTE: If you would like to write tests for your policy, check out the xref:test-config-policies.adoc[Test config policies] guide.
 
@@ -294,7 +298,10 @@ You can now push your new policy to your organization for it to take effect. You
 * Push the policy manually using the CLI from your local environment, or;
 * Push your changes to your config policy repository if you are managing policies via your VCS as shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide].
 
-[tab.block.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -312,13 +319,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
-
-[tab.block.push_to_vcs]
+Push to VCS::
++
 --
 If you have set up your config policies repository with the sample configuration shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide], push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 NOTE: If you would like to write tests for your policy, check out the xref:test-config-policies.adoc[Test config policies] guide.
 
@@ -391,7 +399,10 @@ You can now push your new policy to your organization for it to take effect. You
 * Push the policy manually using the CLI from your local environment, or;
 * Push your changes to your config policy repository if you are managing policies via your VCS as shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide].
 
-[tab.reserve.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -409,13 +420,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
-
-[tab.reserve.push_to_vcs]
+Push to VCS::
++
 --
 If you have set up your config policies repository with the sample configuration shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide], push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 NOTE: If you would like to write tests for your policy, check out the xref:test-config-policies.adoc[Test config policies] guide.
 
@@ -495,7 +507,10 @@ You can now push your new policy to your organization for it to take effect. You
 * Push the policy manually using the CLI from your local environment, or;
 * Push your changes to your config policy repository if you are managing policies via your VCS as shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide].
 
-[tab.branch.manual]
+[tabs]
+====
+Manual::
++
 --
 Create and upload the policy bundle using CircleCI CLI:
 
@@ -513,13 +528,14 @@ If the upload was successful, you will see something like the following:
 }
 ----
 --
-
-[tab.branch.push_to_vcs]
+Push to VCS::
++
 --
 If you have set up your config policies repository with the sample configuration shown in the xref:create-and-manage-config-policies.adoc#manage-policies-with-your-vcs[Manage policies with your VCS guide], push your changes to the `main` branch of your config policies repository, and head to the CircleCI web app to see your policy pipeline run.
 
 You can also push to a development branch, in which case you will get a diff of your policy bundle when you push your changes, rather than your new policy being pushed to your CircleCI organization. This is useful when developing your policies.
 --
+====
 
 NOTE: If you would like to write tests for your policy, check out the xref:test-config-policies.adoc[Test config policies] guide.
 

docs/guides/modules/insights/pages/insights.adoc

@@ -24,20 +24,24 @@ CircleCI web application.
 
 To access a specific project's Insights, view a pipeline's workflow and click the *Insights* button. Alternatively, you may access the Insights page by opening a pipeline's *Actions* menu while viewing the pipelines dashboard.
 
-[tab.access-insights.Access_by_sidebar]
+[tabs]
+====
+Access_by_sidebar::
++
 --
 image::guides:ROOT:screen_insights_access-3.png[Access insights from the CircleCI web app sidebar]
 --
-
-[tab.access-insights.Access_by_workflow]
+Access_by_workflow::
++
 --
 image::guides:ROOT:screen_insights_access-2.png[Access insights from a workflow in the CircleCI web app]
 --
-
-[tab.access-insights.Access_by_pipeline]
+Access_by_pipeline::
++
 --
 image::guides:ROOT:screen_insights_access-1.png[Access insights from a pipeline in the CircleCI web app]
 --
+====
 
 [#workflow-overview]
 === Workflow overview

docs/guides/modules/orchestrate/pages/triggers-overview.adoc

@@ -10,7 +10,10 @@ Pipelines are triggered in response to actions or scheduled to run at specific t
 
 Trigger a pipeline on an event in your repository. The options available to you will be different depending on which integration you have set up, and for GitHub accounts, which GitHub authentication method you use. For steps to add a trigger for a project, see the xref:pipelines.adoc#add-a-trigger[Pipelines and triggers] page.
 
-[tab.event-trigger.GitHub]
+[tabs]
+====
+GitHub::
++
 --
 include::ROOT:partial$tips/check-github-type-org.adoc[]
 
@@ -29,18 +32,19 @@ If you only use the **GitHub OAuth** integration, once a project is set up in Ci
 
 TIP: If your org uses the **GitHub OAuth** integration, you can install the GitHub App into your org to set up GitHub App pipelines and access the trigger options described above. An org admin must take the one-time action of installing the CircleCI GitHub App to enable this functionality. For more information, see the xref:integration:github-integration.adoc#installing-github-app-alongside-github-oauth-app[GitHub OAuth integration overview].
 --
-
-[tab.event-trigger.GitLab]
+GitLab::
++
 --
 NOTE: The available GitLab trigger options are the same for GitLab Cloud and self-managed.
 
 When you create a GitLab project in CircleCI you can set up multiple pipelines and triggers. The default trigger option is to build on every push to your repo. Select from a list or configure a combination of trigger options to control when each pipeline will trigger. You can choose from a selection of supported GitLab events. For a full list of options, see the xref:gitlab-trigger-options.adoc[GitLab trigger options] page.
 --
-
-[tab.event-trigger.BitBucket_Cloud]
+BitBucket_Cloud::
++
 --
 Once your Bitbucket Cloud project is set up in CircleCI, a pipeline is triggered each time a commit is pushed on a branch that has a `.circleci/config.yml` file included. One exception to this is if you use the "Only build pull requests" option. For more information on "Only build pull requests", see the xref:integration:oss.adoc[Build open source projects] page.
 --
+====
 
 Once triggered, a running pipeline appears on the pipelines dashboard, which is accessible by selecting **Dashboard** from the left hand sidebar in the CircleCI web app.
 

docs/guides/modules/orchestrate/pages/workflows.adoc

@@ -802,15 +802,19 @@ Workflows help to speed up your ability to respond to failures. One way to do th
 . Use the filters to find your project and pipeline.
 . Find the row in the pipeline view for the workflow you would like to rerun from failed and select the *Rerun from failed* icon. This option is also available in the workflow view using the rerun dropdown menu, which you can access by clicking on the workflow name or badge.
 
-[tab.rerun-screenshot.Rerun_from_the_pipelines_page]
+[tabs]
+====
+Rerun_from_the_pipelines_page::
++
 --
 image::guides:ROOT:orchestrate-and-trigger/rerun-from-failed-pipelines-page.png[Rerun a workflow from failed from the pipelines page]
 --
-
-[tab.rerun-screenshot.Rerun_from_the_workflows_page]
+Rerun_from_the_workflows_page::
++
 --
 image::guides:ROOT:orchestrate-and-trigger/rerun-from-failed-workflows-page.png[Rerun a workflow from failed from the workflows page]
 --
+====
 
 NOTE: If you rerun a workflow containing a job that was previously re-run with SSH, the new workflow runs with SSH enabled for that job, even after SSH capability is disabled at the project level.
 

docs/guides/modules/toolkit/pages/sample-config.adoc

@@ -440,11 +440,14 @@ NOTE: A job can only run when its dependencies are satisfied therefore it requir
 It is possible to use multiple xref:execution-managed:executor-intro.adoc[executor types]
 in the same workflow.
 
-In `Example-1` each push will build and test the project on Linux, Windows and macOS.
+In Example 1 each push will build and test the project on Linux, Windows and macOS.
 
-In `Example-2` each push of an iOS project will be built on macOS, and additional iOS tools (link:https://github.com/realm/SwiftLint[SwiftLint] and link:https://github.com/danger/danger[Danger]) will be run in Docker.
+In Example 2 each push of an iOS project will be built on macOS, and additional iOS tools (link:https://github.com/realm/SwiftLint[SwiftLint] and link:https://github.com/danger/danger[Danger]) will be run in Docker.
 
-[tab.multiple-executors.Example_1]
+[tabs]
+====
+Example 1::
++
 --
 [,yaml]
 ----
@@ -709,8 +712,8 @@ workflows:
               only: main
 ----
 --
-
-[tab.multiple-executors.Example_2]
+Example 2::
++
 --
 [,yaml]
 ----
@@ -766,6 +769,7 @@ workflows:
       - build-and-test
 ----
 --
+====
 
 [#see-also]
 == See also