diff --git a/creating-a-kubernetes-cluster.md b/creating-a-kubernetes-cluster.md
index ebd6a2281..73a2bfb1a 100644
--- a/creating-a-kubernetes-cluster.md
+++ b/creating-a-kubernetes-cluster.md
@@ -242,7 +242,7 @@ For example, use these steps to allow Minikube to pull Knative Serving and Build
 from GCR as published in our development flow (`ko apply -f config/`).
 _This is only necessary if you are not using public Knative Serving and Build images._
 
-1.  Create a Kubernetes secret in the `knative-serving` and `build-system` namespace:
+1.  Create a Kubernetes secret in the `knative-serving` and `knative-build` namespace:
 
     ```shell
     export DOCKER_EMAIL=your.email@here.com
@@ -257,7 +257,7 @@ _This is only necessary if you are not using public Knative Serving and Build im
       --docker-username=_json_key \
       --docker-password="$(cat minikube-gcr-key.json)" \
       --docker-email=$DOCKER_EMAIL \
-      -n "build-system"
+      -n "knative-build"
     ```
 
     _The secret must be created in the same namespace as the pod or service
@@ -269,7 +269,7 @@ _This is only necessary if you are not using public Knative Serving and Build im
     ```shell
     kubectl patch serviceaccount "build-controller" \
       -p '{"imagePullSecrets": [{"name": "build-gcr"}]}' \
-      -n "build-system"
+      -n "knative-build"
     kubectl patch serviceaccount "controller" \
       -p '{"imagePullSecrets": [{"name": "knative-serving-gcr"}]}' \
       -n "knative-serving"
diff --git a/resources-overview.md b/resources-overview.md
index 965100ed5..c3e1f0fea 100644
--- a/resources-overview.md
+++ b/resources-overview.md
@@ -69,7 +69,7 @@ controller-5bfb798f96-2zjnf   1/1       Running   0          9m
 webhook-64c459569b-v5npx      1/1       Running   0          8m
 ```
 
-Similarly, you can run the same commands in the build-crd (`build-system`) and istio (`istio-system`) namespaces to view the running deployments. To view all namespaces, run `kubectl get namespaces`.
+Similarly, you can run the same commands in the build-crd (`knative-build`) and istio (`istio-system`) namespaces to view the running deployments. To view all namespaces, run `kubectl get namespaces`.
 
 ### Service Accounts and RBAC policies
 
diff --git a/spec/errors.md b/spec/errors.md
index 559bdc61f..be65a1062 100644
--- a/spec/errors.md
+++ b/spec/errors.md
@@ -158,7 +158,7 @@ Revision) should have a status field to link to the log output of the
 build.
 
 ```http
-GET /apis/build.dev/v1alpha1/namespaces/default/builds/build-1acub3
+GET /apis/build.knative.dev/v1alpha1/namespaces/default/builds/build-1acub3
 ```
 
 ```yaml
diff --git a/telemetry.md b/telemetry.md
index 78843d7cf..f17c86833 100644
--- a/telemetry.md
+++ b/telemetry.md
@@ -134,7 +134,7 @@ kubernetes.labels.build\-name: "test-build"
 Replace `test-build` with your build's name. The build name is specified in the `.yaml` file as follows:
 
 ```yaml
-apiVersion: build.dev/v1alpha1
+apiVersion: build.knative.dev/v1alpha1
 kind: Build
 metadata:
   name: test-build