Fixed broken links and formatting errors (#874)

website/content/en/pre-docs/AWS/constraints.md

@@ -62,6 +62,7 @@ Select subnets by an arbitrary AWS tag key/value pair:
 ```
   subnetSelector:
     MySubnetTag: value
+```
 
 Select subnets using wildcards:
 ```

website/content/en/pre-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](/docs/tasks/provisioner-task.md) task for provisioner examples. 
+See [Provisioner API](/docs/provisioner-crd/) 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.
@@ -67,7 +67,7 @@ Karpenter handles all clean-up work needed to properly delete the node.
 * **Empty nodes**: When the last workload pod running on a Karpenter-managed node is gone, the node is annotated with an emptiness timestamp.
 Once that "node empty" time-to-live (`ttlSecondsAfterEmpty`) is reached, finalization is triggered.
 
-For more details on how Karpenter deletes nodes, see [Deleting nodes with Karpenter](/docs/tasks/delete-nodes.md) for details.
+For more details on how Karpenter deletes nodes, see [Deleting nodes with Karpenter](../tasks/deprov-nodes.md) for details.
 
 ### Upgrading nodes
 
@@ -161,4 +161,4 @@ Kubernetes SIG scalability recommends against these features and Karpenter doesn
 Instead, the Karpenter project recommends `topologySpreadConstraints` to reduce blast radius and `nodeSelectors` and `taints` to implement colocation.
 {{% /alert %}}
 
-For more on how, as a developer, you can add constraints to your pod deployment, see [Running pods](/docs/tasks/running-pods.md) for details.
+For more on how, as a developer, you can add constraints to your pod deployment, see [Running pods](../tasks/running-pods.md) for details.

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

@@ -1,6 +1,6 @@
 ---
-title: "Deprovision nodes"
-linkTitle: "Deprovision nodes"
+title: "Deprovisioning nodes"
+linkTitle: "Deprovisioning nodes"
 weight: 20
 ---
 

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

@@ -1,10 +1,10 @@
 ---
-title: "Provisioning"
-linkTitle: "Provisioning"
+title: "Provisioning nodes"
+linkTitle: "Provisioning nodes"
 weight: 5
 ---
 
-When you first installed Karpenter, you set up a default [Provisioner](../getting-started/#provisioner).
+When you first installed Karpenter, you set up a default Provisioner.
 The Provisioner sets constraints on the nodes that can be created by Karpenter and the pods that can run on those nodes.
 The Provisioner can be set to do things like:
 
@@ -23,14 +23,15 @@ Here are things you should know about Provisioners:
 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 Provisioner API values
+  * [Provisioner API](../provisioner-crd) for descriptions of Provisioner API values
   * [Provisioning Configuration](../AWS/constraints) for cloud-specific settings
 
-1. Apply the new or modified Provisioner to the cluster.
+2. Apply the new or modified Provisioner to the cluster.
 
 The following examples illustrate different aspects of Provisioners.
-Refer to [Running pods](../tasks/running-pods) to see how the same features are used in Pod specs to determine where pods run.
+Refer to [Running pods](running-pods) to see how the same features are used in Pod specs to determine where pods run.
 
 ## Example: Requirements
 

website/content/en/pre-docs/tasks/running-pods.md

@@ -60,7 +60,7 @@ Its limits are set to 256MiB of memory and 1 CPU.
 Instance type selection math only uses `requests`, but `limits` may be configured to enable resource oversubscription.
 
 
-See [Managing Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) for details on resource types supported by Kubernetes, [Specify a memory request and a memory limit](https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#specify-a-memory-request-and-a-memory-limit) for examples of memory requests, and [Specifying Values to Control AWS Provisioning](/docs/cloud-providers/aws/aws-spec-fields) for a list of supported resources.
+See [Managing Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) for details on resource types supported by Kubernetes, [Specify a memory request and a memory limit](https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#specify-a-memory-request-and-a-memory-limit) for examples of memory requests, and [Provisioning COnfiguration](../aws/constraints) for a list of supported resources.
 
 ## Selecting nodes (`nodeSelector` and `nodeAffinity`)