Fix broken links.

_redirects

@@ -23,6 +23,7 @@ TEMPORARY
 /docs/tasks/administer-cluster/certificate-rotation/     /docs/admin/kubelet-tls-bootstrapping/ 301
 /docs/tasks/administer-cluster/running-cloud-controller.md     /docs/tasks/administer-cluster/running-cloud-controller/ 301
 /docs/concepts/workloads/controllers/statefulset.md     /docs/concepts/workloads/controllers/statefulset/ 301
+/docs/concepts/workloads/controllers/deployment.md     /docs/concepts/workloads/controllers/deployment/ 301    
 
 #############
 

docs/concepts/cluster-administration/federation.md

@@ -93,7 +93,7 @@ The following guides explain some of the resources in detail:
 * [Events](/docs/tasks/administer-federation/events/)
 * [Hpa](/docs/tasks/administer-federation/hpa/)
 * [Ingress](/docs/tasks/administer-federation/ingress/)
-* [Jobs](docs/tasks/administer-federation/job/)
+* [Jobs](/docs/tasks/administer-federation/job/)
 * [Namespaces](/docs/tasks/administer-federation/namespaces/)
 * [ReplicaSets](/docs/tasks/administer-federation/replicaset/)
 * [Secrets](/docs/tasks/administer-federation/secret/)

docs/concepts/configuration/pod-priority-preemption.md

@@ -236,9 +236,4 @@ and cross Node preemption will not be considered a blocker for Beta or GA.
 
 {% endcapture %}
 
-{% capture whatsnext %}
-* Learn more about [this](...).
-* See this [related task](...).
-{% endcapture %}
-
 {% include templates/concept.md %}

docs/tasks/administer-federation/hpa.md

@@ -65,7 +65,7 @@ cluster.
 
 Once a federated HPA is created, the federation control plane partitions and
 creates the HPA in all underlying Kubernetes clusters. As of Kubernetes V1.7,
-[cluster selectors](docs/tasks/administer-federation/cluster/#clusterselector-annotation)
+[cluster selectors](/docs/tasks/administer-federation/cluster/#clusterselector-annotation)
 can also be used to restrict any federated object, including the HPAs in a subset
 of clusters.
 
@@ -120,7 +120,7 @@ You can delete a federated HPA as you would delete a Kubernetes
 HPA; however, for a federated HPA, you must send the request to
 the federation API server instead of sending it to a specific Kubernetes cluster.
 It should also be noted that for the federated resource to be deleted from
-all underlying clusters, [cascading deletion](docs/concepts/cluster-administration/federation/#cascading-deletion)
+all underlying clusters, [cascading deletion](/docs/concepts/cluster-administration/federation/#cascading-deletion)
 should be used.
 
 For example, you can do that using `kubectl` by running:
@@ -139,7 +139,7 @@ and `kubectl autoscale` work on federation. Given this fact, the mechanism speci
 [horizontal pod autoscaler walkthrough](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough)
 will also work when used with federation.
 Care however will need to be taken that when
-[generating load on a target deployment](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#step-three-increase-load),
+[generating load on a target deployment](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#step-three-increase-load),
 it should be done against a specific federated cluster (or multiple clusters) not the federation.
 
 ## Conclusion