Merge pull request #99 from coreydaley/2023_08_14_fix_documentation

Fix broken build links

content/en/blog/posts/2021-08-02-adding-gatekeeper.md/index.md

@@ -10,7 +10,7 @@ resources:
 ---
 
 
-[Gatekeeper](https://github.com/open-policy-agent/gatekeeper) is a customizable [admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#what-are-admission-webhooks) for Kubernetes, which allows you to configure [policy](https://www.openpolicyagent.org/docs/latest/policy-language/) over what resources can be created in the cluster. In particular, we can use Gatekeeper to add policy to Shipwright [`Build`](/docs/api/build/)s. In this example, you can see how you can use a policy to control what source repositories Shipwright is allowed to build, so that you can have more control over what code executes inside your cluster.
+[Gatekeeper](https://github.com/open-policy-agent/gatekeeper) is a customizable [admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#what-are-admission-webhooks) for Kubernetes, which allows you to configure [policy](https://www.openpolicyagent.org/docs/latest/policy-language/) over what resources can be created in the cluster. In particular, we can use Gatekeeper to add policy to Shipwright [`Build`](/docs/build/)s. In this example, you can see how you can use a policy to control what source repositories Shipwright is allowed to build, so that you can have more control over what code executes inside your cluster.
 
 [![Gatekeeper](opa.png)](https://github.com/securekubernetes/securekubernetes/blob/master/docs/img/opa.png)
 

content/en/docs/_index.md

@@ -45,10 +45,10 @@ Shipwright's Build API consists of four core
 [CustomResourceDefinitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions)
 (CRDs):
 
-1. [`Build`](/docs/api/build/) - defines what to build, and where the application should be delivered.
-1. [`BuildStrategy` and `ClusterBuildStrategy`](/docs/api/buildstrategies/) - defines how to build an application for an image
+1. [`Build`](/docs/build/) - defines what to build, and where the application should be delivered.
+1. [`BuildStrategy` and `ClusterBuildStrategy`](/docs/build/buildstrategies/) - defines how to build an application for an image
    building tool.
-1. [`BuildRun`](/docs/api/buildrun/) - invokes the build.
+1. [`BuildRun`](/docs/build/buildrun/) - invokes the build.
    You create a `BuildRun` to tell Shipwright to start building your application.
 
 ### Build
@@ -127,7 +127,7 @@ spec:
 
 Each `BuildRun` object invokes a build on your cluster. You can think of these as a Kubernetes
 `Jobs` or Tekton `TaskRuns` - they represent a workload on your cluster, ultimately resulting in a
-running `Pod`. See [`BuildRun`](/docs/api/buildrun/) for more details.
+running `Pod`. See [`BuildRun`](/docs/build/buildrun/) for more details.
 
 ## Further reading