Updated URL's on eventlisteners.md

docs/eventlisteners.md

@@ -70,7 +70,7 @@ An `EventListener` definition consists of the following fields:
 [kubernetes-overview]:
   https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#required-fields
 
-See our [Tekton Triggers examples](https://github.com/tektoncd/triggers/tree/master/examples) for ready-to-use example `EventListener` definitions.
+See our [Tekton Triggers examples](https://github.com/tektoncd/triggers/tree/main/examples) for ready-to-use example `EventListener` definitions.
 
 ## Specifying the Kubernetes service account
 
@@ -375,7 +375,7 @@ type EventListenerStatus struct {
 }
 ```
 
-**Note:** The CRD must follow the [WithPod{}](https://github.com/knative/pkg/blob/master/apis/duck/v1/podspec_types.go#L41) spec. 
+**Note:** The CRD must follow the [WithPod{}](https://github.com/knative/pkg/blob/main/apis/duck/v1/podspec_types.go#L41) spec. 
 
 Below is an example `resources:` field definition specifying a `CustomResource` object using a [Knative Service](https://knative.dev/docs/):
 
@@ -574,7 +574,7 @@ These fields are included in `EventListener` responses, but will be removed in a
 
 Tekton Triggers supports both HTTP and TLS-based HTTPS connections. To configure your `EventListener` for TLS,
 add the `TLS_CERT` and `TLS_KEY` reserved environment variables using the `secretKeyRef` variable type, then
-specify a `secret` containing the `cert` and `key` files. See [TEP-0027](https://github.com/tektoncd/community/blob/master/teps/0027-https-connection-to-triggers-eventlistener.md)
+specify a `secret` containing the `cert` and `key` files. See [TEP-0027](https://github.com/tektoncd/community/blob/main/teps/0027-https-connection-to-triggers-eventlistener.md)
 and our [TLS configuration example](../examples/v1beta1/eventlistener-tls-connection/README.md) for more information.
 
 ## Obtaining the status of deployed `EventListeners`
@@ -699,11 +699,11 @@ Below is a high-level walkthrough through the deployment of an `EventListener` u
 
 1. Instantiate the example `EventListener` on your cluster:
    ```bash
-   kubectl create -f https://github.com/tektoncd/triggers/tree/master/examples/github
+   kubectl create -f https://github.com/tektoncd/triggers/tree/main/examples/v1beta1/github
    ```
 
    Tekton Triggers creates a new `Deployment` and `Service` for the `EventListener`. using the `EventListener` definition,
-   [`metadata.labels`](https://github.com/tektoncd/triggers/blob/master/docs/eventlisteners.md#labels), and pre-existing values
+   [`metadata.labels`](https://github.com/tektoncd/triggers/blob/main/docs/eventlisteners.md#labels), and pre-existing values
    such as container `Image`, `Name`, and `Port`. Tekton Triggers uses the `EventListener` name prefixed with `el-` to name the
    `Deployment` and `Service` when instantiating them. For example, if the `EventListener` name is `foo`, the `Deployment` and
    `Service` names are named `el-foo`.
@@ -728,7 +728,7 @@ Below is a high-level walkthrough through the deployment of an `EventListener` u
    github-listener-interceptor   http://el-github-listener-interceptor.ptest.svc.cluster.local:8080   True        MinimumReplicasAvailable
    ```
 
-   See our [GitHub `EventListener` example](https://github.com/tektoncd/triggers/blob/master/examples/github/README.md) to try instantiating an `EventListener` locally.
+   See our [GitHub `EventListener` example](https://github.com/tektoncd/triggers/blob/main/examples/v1beta1/github/README.md) to try instantiating an `EventListener` locally.
 
 ## Deploying `EventListeners` in multi-tenant scenarios