diff --git a/README.md b/README.md
index 3c86e823..73935d4b 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ copy the WORKSPACE snippet into your `WORKSPACE` file.
 The `k8s_deploy` creates rules that produce the `.apply` and `.gitops` targets `k8s_deploy` is defined in [k8s.bzl](./skylib/k8s.bzl). `k8s_deploy` takes the files listed in the `manifests`, `patches`, and `configmaps_srcs` attributes and combines (**renders**) them into one  YAML file. This happens when you `bazel build` or `bazel run` a target created by the `k8s_deploy`. The file is created at `bazel-bin/path/to/package/name.yaml`. When you run a `.apply` target, it runs `kubectl apply` on this file. When you run a `.gitops` target, it copies this file to
 the appropriate location in the same os separate repository.
 
-For example, let's look at the [example's k8s_deploy](./e2e/helloworld/BUILD). We can peek at the file containing the rendered K8s manifests:
+For example, let's look at the [example's k8s_deploy](./e2e/helloworld/BUILD.bazel). We can peek at the file containing the rendered K8s manifests:
 ```bash
 cd e2e
 bazel run //helloworld:mynamespace.show
@@ -342,7 +342,7 @@ k8s_deploy(
 Many instances of `k8s_deploy` include an `objects` attribute that references other instances of
 `k8s_deploy`. When chained this way, running the `.apply` will also apply any dependencies as well.
 
-For example, to add dependency to the example [helloworld deployment](./examples/helloworld/BUILD):
+For example, to add dependency to the example [helloworld deployment](./e2e/helloworld/BUILD.bazel):
 ```starlark
 k8s_deploy(
     name = "mynamespace",