Renamed provisioner-crd doc to provisioner and fixed links (#950)

* Renamed provisioner-crd doc to provisioner and fixed links

* Fixed typo

* Fixed a few more broken links

* More small fixes

website/content/en/docs/AWS/launch-templates.md

@@ -219,7 +219,7 @@ aws cloudformation create-stack \
 ### Define LaunchTemplate for Provisioner
 
 The LaunchTemplate is ready to be used. Specify it by name in the [Provisioner
-CRD](../../provisioner-crd/). Karpenter will use this template when creating new instances.
+CRD](../../provisioner/). Karpenter will use this template when creating new instances.
 
 ```yaml
 apiVersion: karpenter.sh/v1alpha5

website/content/en/docs/concepts/_index.md

@@ -42,7 +42,7 @@ Here are some things to know about the Karpenter provisioner:
 * **Provisioner CR**: Karpenter defines a Custom Resource called a Provisioner to specify provisioning configuration.
 Each provisioner manages a distinct set of nodes, but pods can be scheduled to any provisioner that supports its scheduling constraints.
 A provisioner contains constraints that impact the nodes that can be provisioned and attributes of those nodes (such timers for removing nodes).
-See [Provisioner API](/docs/provisioner-crd/) for a description of settings and the [Provisioning](../tasks/provisioning-task) task for provisioner examples. 
+See [Provisioner API](/docs/provisioner/) for a description of settings and the [Provisioning](../tasks/provisioning-task) task for provisioner examples. 
 
 * **Well-known labels**: The provisioner can use well-known Kubernetes labels to allow pods to request only certain instance types, architectures, operating systems, or other attributes when creating nodes.
 See [Well-Known Labels, Annotations and Taints](https://kubernetes.io/docs/reference/labels-annotations-taints/) for details.

website/content/en/docs/getting-started/_index.md

@@ -182,7 +182,7 @@ resources like subnets and security groups using the cluster's name.
 The `ttlSecondsAfterEmpty` value configures Karpenter to terminate empty nodes.
 This behavior can be disabled by leaving the value undefined.
 
-Review the [provisioner CRD](/docs/provisioner-crd) for more information. For example,
+Review the [provisioner CRD](/docs/provisioner/) for more information. For example,
 `ttlSecondsUntilExpired` configures Karpenter to terminate nodes when a maximum age is reached.
 
 Note: This provisioner will create capacity as long as the sum of all created capacity is less than the specified limit.

website/content/en/docs/tasks/deprov-nodes.md

@@ -31,6 +31,6 @@ Karpenter will delete nodes (and the instance) that are considered empty of pods
 
 ## Expiry
 
-Nodes may be configured to expire. That is, a maximum lifetime in seconds starting with the node joining the cluster. Review the `ttlSecondsUntilExpired` field of the [provisioner API](../../provisioner-crd/).
+Nodes may be configured to expire. That is, a maximum lifetime in seconds starting with the node joining the cluster. Review the `ttlSecondsUntilExpired` field of the [provisioner API](../../provisioner/).
 
 Note that newly created nodes have a Kubernetes version matching the control plane. One use case for node expiry is to handle node upgrades. Old nodes (with a potentially outdated Kubernetes version) are deleted, and replaced with nodes on the current version. 

website/content/en/docs/tasks/provisioning-task.md

@@ -25,7 +25,7 @@ If you want to modify or add provisioners to Karpenter, do the following:
 1. Review the following Provisioner documents:
 
   * [Provisioner](../../getting-started/#provisioner) in the Getting Started guide for a sample default Provisioner
-  * [Provisioner API](../../provisioner-crd) for descriptions of Provisioner API values
+  * [Provisioner API](../../provisioner/) for descriptions of Provisioner API values
   * [Provisioning Configuration](../../AWS/provisioning) for cloud-specific settings
 
 2. Apply the new or modified Provisioner to the cluster.

website/content/en/v0.4.3-docs/cloud-providers/AWS/aws-spec-fields.md

@@ -4,7 +4,7 @@ linkTitle: "Spec Fields"
 weight: 10
 ---
 
-The [Provisioner CRD]({{< ref "docs/provisioner-crd.md" >}}) supports defining
+The [Provisioner CRD]({{< ref "../../provisioner-crd.md" >}}) supports defining
 node properties like instance type and zone. For certain well-known labels (documented below), Karpenter will provision
 nodes accordingly. For example, in response to a label of
 `topology.kubernetes.io/zone=us-east-1c`, Karpenter will provision nodes in

website/content/en/v0.4.3-docs/cloud-providers/AWS/launch-templates.md

@@ -219,7 +219,7 @@ aws cloudformation create-stack \
 ### Define LaunchTemplate for Provisioner
 
 The LaunchTemplate is ready to be used. Specify it by name in the [Provisioner
-CRD](../../../provisioner-crd). Karpenter will use this template when creating new instances.
+CRD](../../provisioner-crd). Karpenter will use this template when creating new instances.
 
 ```yaml
 apiVersion: karpenter.sh/v1alpha5

website/content/en/v0.4.3-docs/getting-started/_index.md

@@ -217,7 +217,7 @@ resources like subnets and security groups using the cluster's name.
 The `ttlSecondsAfterEmpty` value configures Karpenter to terminate empty nodes.
 This behavior can be disabled by leaving the value undefined.
 
-Review the [provisioner CRD](/docs/provisioner-crd) for more information. For example,
+Review the [provisioner CRD](../provisioner-crd) for more information. For example,
 `ttlSecondsUntilExpired` configures Karpenter to terminate nodes when a maximum age is reached.
 
 ```bash