Fix links (#866)

* Fix links

* Update installing-build-component.md

* Update builder-contract.md

docs/build/builder-contract.md

@@ -68,7 +68,7 @@ Builders should expect a Build to implement the following conventions:
 - `/builder/home`: This volume is exposed to steps via `$HOME`.
 
 - Credentials attached to the Build's service account may be exposed as Git or
-  Docker credentials as outlined [here](./auth/).
+  Docker credentials as outlined [here](auth/).
 
 ---
 

docs/build/builds.md

@@ -96,7 +96,7 @@ The `steps` field is required if the `template` field is not defined. You define
 one or more `steps` fields to define the body of a build.
 
 Each `steps` in a build must specify a `Builder`, or type of container image
-that adheres to the [Knative builder contract](./builder-contract/). For each
+that adheres to the [Knative builder contract](builder-contract/). For each
 of the `steps` fields, or container images that you define:
 
 - The `Builder`-type container images are run and evaluated in order, starting
@@ -105,16 +105,16 @@ of the `steps` fields, or container images that you define:
   detected.
 
 For details about how to ensure that you implement each step to align with the
-"builder contract", see the [`Builder`](./builder-contract/) reference topic.
+"builder contract", see the [`Builder`](builder-contract/) reference topic.
 
 #### Template
 
 The `template` field is a required if no `steps` are defined. Specifies a
-[`BuildTemplate`](./build-templates/) resource object, in which includes
+[`BuildTemplate`](build-templates/) resource object, in which includes
 repeatable or sharable build `steps`.
 
 For examples and more information about build templates, see the
-[`BuildTemplate`](./build-templates/) reference topic.
+[`BuildTemplate`](build-templates/) reference topic.
 
 #### Source
 
@@ -147,7 +147,7 @@ that is in the
 of the `Build` resource object.
 
 For examples and more information about specifying service accounts, see the
-[`ServiceAccount`](./auth/) reference topic.
+[`ServiceAccount`](auth/) reference topic.
 
 #### Volumes
 
@@ -155,11 +155,11 @@ Optional. Specifies one or more
 [volumes](https://kubernetes.io/docs/concepts/storage/volumes/) that you want to
 make available to your build, including all the build steps. Add volumes to
 complement the volumes that are implicitly
-[created during a build step](./builder-contract/).
+[created during a build step](builder-contract/).
 
 For example, use volumes to accomplish one of the following common tasks:
 
-- [Mount a Kubernetes secret](./auth/).
+- [Mount a Kubernetes secret](auth/).
 
 - Create an `emptyDir` volume to act as a cache for use across multiple build
   steps. Consider using a persistent volume for inter-build caching.

docs/build/installing-build-component.md

@@ -15,7 +15,7 @@ want, for example Knative serving is not required to create and run builds.
 
 You must have a component of Knative installed and running in your Kubernetes
 cluster. For complete installation instructions, including how to install the
-Knative Build component, see [Installing Knative](../install/).
+Knative Build component, see [Installing Knative](../../install/).
 
 ## Adding the Knative Build component
 
@@ -42,7 +42,7 @@ To add only the Knative Build component to an existing installation:
    time. Use CTRL + C to exit watch mode.
 
 You are now ready to create and run Knative Builds, see
-[Creating a simple Knative Build](../build/creating-builds/) to get started.
+[Creating a simple Knative Build](creating-builds/) to get started.
 
 ---