Format markdown

docs/clustertriggerbindings.md

@@ -6,6 +6,7 @@ designed to encourage reusability clusterwide. You can reference a
 ClusterTriggerBinding in any EventListener in any namespace.
 
 <!-- FILE: examples/clustertriggerbindings/clustertriggerbinding.yaml -->
+
 ```YAML
 apiVersion: tekton.dev/v1alpha1
 kind: ClusterTriggerBinding
@@ -21,14 +22,14 @@ spec:
       value: $(header.Content-Type)
 ```
 
-
 You can specify multiple ClusterTriggerBindings in a Trigger. You can use a
 ClusterTriggerBinding in multiple Triggers.
 
 In case of using a ClusterTriggerBinding, the `Binding` kind should be added.
 The default kind is TriggerBinding which represents a namespaced TriggerBinding.
 
 <!-- FILE: examples/eventlisteners/eventlistener-clustertriggerbinding.yaml -->
+
 ```YAML
 ---
 apiVersion: tekton.dev/v1alpha1
@@ -47,4 +48,3 @@ spec:
       template:
         name: pipeline-template
 ```
-

docs/eventlisteners.md

@@ -7,6 +7,7 @@ resources will be created (or at least attempted) with. The service account must
 have the following role bound.
 
 <!-- FILE: examples/role-resources/triggerbinding-roles/role.yaml -->
+
 ```YAML
 kind: Role
 apiVersion: rbac.authorization.k8s.io/v1
@@ -26,7 +27,6 @@ rules:
   verbs: ["create"]
 ```
 
-
 Note that currently, JSON is the only accepted MIME type for events.
 
 When an `EventListener` is successfully created, a service is created that
@@ -115,6 +115,7 @@ To be an Event Interceptor, a Kubernetes object should:
   the body, it can simply return the body that it received.
 
 <!-- FILE: examples/eventlisteners/eventlistener-interceptor.yaml -->
+
 ```YAML
 ---
 apiVersion: tekton.dev/v1alpha1
@@ -145,7 +146,6 @@ spec:
         name: pipeline-template
 ```
 
-
 ### GitHub Interceptors
 
 GitHub interceptors contain logic to validate and filter webhooks that come from
@@ -167,6 +167,7 @@ The body/header of the incoming request will be preserved in this interceptor's
 response.
 
 <!-- FILE: examples/eventlisteners/github-eventlistener-interceptor.yaml -->
+
 ```YAML
 ---
 apiVersion: tekton.dev/v1alpha1
@@ -190,7 +191,6 @@ spec:
         name: pipeline-template
 ```
 
-
 ### GitLab Interceptors
 
 GitLab interceptors contain logic to validate and filter requests that come from
@@ -213,6 +213,7 @@ The body/header of the incoming request will be preserved in this interceptor's
 response.
 
 <!-- FILE: examples/eventlisteners/gitlab-eventlistener-interceptor.yaml -->
+
 ```YAML
 ---
 apiVersion: tekton.dev/v1alpha1
@@ -236,7 +237,6 @@ spec:
         name: pipeline-template
 ```
 
-
 ### CEL Interceptors
 
 CEL interceptors parse expressions to filter requests based on JSON bodies and
@@ -254,6 +254,7 @@ The body/header of the incoming request will be preserved in this interceptor's
 response.
 
 <!-- FILE: examples/eventlisteners/cel-eventlistener-interceptor.yaml -->
+
 ```YAML
 apiVersion: tekton.dev/v1alpha1
 kind: EventListener
@@ -283,13 +284,13 @@ spec:
         name: pipeline-template
 ```
 
-
 If no filter is provided, then the overlays will be applied to the body,
 
 With a filter, the `expression` must return a `true` value, otherwise the
 request will be filtered out.
 
 <!-- FILE: examples/eventlisteners/cel-eventlistener-no-filter.yaml -->
+
 ```YAML
 apiVersion: tekton.dev/v1alpha1
 kind: EventListener
@@ -309,4 +310,3 @@ spec:
       template:
         name: pipeline-template
 ```
-

docs/triggerbindings.md

@@ -6,6 +6,7 @@ parameters. The separation of `TriggerBinding`s from `TriggerTemplate`s was
 deliberate to encourage reuse between them.
 
 <!-- FILE: examples/triggerbindings/triggerbinding.yaml -->
+
 ```YAML
 apiVersion: tekton.dev/v1alpha1
 kind: TriggerBinding
@@ -21,7 +22,6 @@ spec:
     value: $(header.Content-Type)
 ```
 
-
 `TriggerBinding`s are connected to `TriggerTemplate`s within an
 [`EventListener`](eventlisteners.md), which is where the pod is actually
 instantiated that "listens" for the respective events.

docs/triggertemplates.md

@@ -5,6 +5,7 @@ A `TriggerTemplate` is a resource that can template resources.
 **anywhere** within the resource template.
 
 <!-- FILE: examples/triggertemplates/triggertemplate.yaml -->
+
 ```YAML
 apiVersion: tekton.dev/v1alpha1
 kind: TriggerTemplate
@@ -46,7 +47,6 @@ spec:
             value: $(params.gitrepositoryurl)
 ```
 
-
 Similar to
 [Pipelines](https://github.com/tektoncd/pipeline/blob/master/docs/pipelines.md),`TriggerTemplate`s
 do not do any actual work, but instead act as the blueprint for what resources