diff --git a/docs/custom-gateway.md b/docs/custom-gateway.md
index 129c10e0e4..68e0d8e5b4 100644
--- a/docs/custom-gateway.md
+++ b/docs/custom-gateway.md
@@ -77,7 +77,7 @@ type GatewayConfig struct {
 gatewayConfig.DispatchEvent(event []byte, src string) error
 ```
 
-For detailed implementation, check out [Core Gateways](https://github.com/argoproj/argo-events/tree/eventing/gateways/core)
+For detailed implementation, check out [Core Gateways](https://github.com/argoproj/argo-events/tree/master/gateways/core)
 
 ## gRPC gateway
 A gRPC gateway has 3 components, 
@@ -101,7 +101,7 @@ RunGateway(GatewayConfig) returns (stream Event)
 The gateway processor client opens a new connection for each gateway configuration and starts listening to
 events on a stream.
 
-For detailed implementation, check out [Calendar gRPC gateway](https://github.com/argoproj/argo-events/tree/eventing/gateways/grpc/calendar)
+For detailed implementation, check out [Calendar gRPC gateway](https://github.com/argoproj/argo-events/tree/master/gateways/grpc/calendar)
 
 * To run gRPC gateway, you need to provide `rpcPort` in gateway spec.
 
@@ -136,7 +136,7 @@ List of environment variables available to user code
 |  GATEWAY_HTTP_CONFIG_EVENT             | REST endpoint to send events to |
 
 
-For detailed implementation, check out [Calendar HTTP gateway](https://github.com/argoproj/argo-events/tree/eventing/gateways/rest/calendar)
+For detailed implementation, check out [Calendar HTTP gateway](https://github.com/argoproj/argo-events/tree/master/gateways/rest/calendar)
 
 ## Framework independent
 The fourth option is you provide gateway implementation from scratch: watch the configuration
@@ -154,4 +154,4 @@ List of environment variables available to user code
 |  GATEWAY_NAME             | Gateway name  |
 
 ### Gateway Examples
-* Example gateway definitions are available at [here](https://github.com/argoproj/argo-events/tree/eventing/examples/gateways)
\ No newline at end of file
+* Example gateway definitions are available at [here](https://github.com/argoproj/argo-events/tree/master/examples/gateways)
diff --git a/docs/gateway-guide.md b/docs/gateway-guide.md
index 3fcc093d80..fe7bb5ff05 100644
--- a/docs/gateway-guide.md
+++ b/docs/gateway-guide.md
@@ -210,4 +210,4 @@ Stream gateways contain a generic specification for messages received on a queue
 ```
 
 ### Examples
-Explore [Gateway Examples](https://github.com/argoproj/argo-events/tree/eventing/examples/gateways)
+Explore [Gateway Examples](https://github.com/argoproj/argo-events/tree/master/examples/gateways)
diff --git a/docs/sensor-guide.md b/docs/sensor-guide.md
index 325e497c78..b842533cdb 100644
--- a/docs/sensor-guide.md
+++ b/docs/sensor-guide.md
@@ -1,7 +1,7 @@
 ## Sensor Guide
 
 Sensors define a set of dependencies (inputs) and actions (outputs). The sensor's actions will only be triggered after it's dependencies have been resolved.
-[Sensor examples](https://github.com/argoproj/argo-events/tree/eventing/examples/sensors)
+[Sensor examples](https://github.com/argoproj/argo-events/tree/master/examples/sensors)
 
 
 ### Dependencies
@@ -83,4 +83,4 @@ filters:
             - path: bucket
               type: string
               value: argo-workflow-input
-```
\ No newline at end of file
+```