Fixed links (gardener#4413)

Author: n-boshnakov

CONTRIBUTING.md

@@ -1 +1 @@
-Please refer to the [Gardener contributor guide](https://gardener.cloud/documentation/contribute/).
+Please refer to the [Gardener contributor guide](https://gardener.cloud/docs/contribute/).

README.md

@@ -10,7 +10,7 @@
 
 Gardener implements the automated management and operation of [Kubernetes](https://kubernetes.io/) clusters as a service and provides a fully validated extensibility framework that can be adjusted to any programmatic cloud or infrastructure provider.
 
-Gardener is 100% Kubernets-native and exposes its own Cluster API to create homogeneous clusters on all supported infrastructures. This API differs from [SIG Cluster Lifecycle](https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle)'s [Cluster API](https://github.com/kubernetes-sigs/cluster-api#cluster-api) that only harmonizes how to get to clusters, while [Gardener's Cluster API](https://gardener.cloud/documentation/references/core/#core.gardener.cloud/v1beta1.Shoot) goes one step further and also harmonizes the make-up of the clusters themselves. That means, Gardener gives you homogeneous clusters with exactly the same bill of material, configuration and behavior on all supported infrastructures, which you can see further down below in the section on our K8s Conformance Test Coverage.
+Gardener is 100% Kubernets-native and exposes its own Cluster API to create homogeneous clusters on all supported infrastructures. This API differs from [SIG Cluster Lifecycle](https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle)'s [Cluster API](https://github.com/kubernetes-sigs/cluster-api#cluster-api) that only harmonizes how to get to clusters, while [Gardener's Cluster API](https://gardener.cloud/docs/references/core/#core.gardener.cloud/v1beta1.Shoot) goes one step further and also harmonizes the make-up of the clusters themselves. That means, Gardener gives you homogeneous clusters with exactly the same bill of material, configuration and behavior on all supported infrastructures, which you can see further down below in the section on our K8s Conformance Test Coverage.
 
 In 2020, SIG Cluster Lifecycle's Cluster API made a huge step forward with [`v1alpha3`](https://kubernetes.io/blog/2020/04/21/cluster-api-v1alpha3-delivers-new-features-and-an-improved-user-experience/) and the newly added support for declarative control plane management. This made it possible to integrate managed services like GKE or Gardener. We would be more than happy, if the community would be interested, to contribute a Gardener control plane provider. For more information on the relation between Gardener API and SIG Cluster Lifecycle's Cluster API, please see [here](docs/concepts/cluster-api.md).
 

docs/proposals/README.md

@@ -19,7 +19,7 @@ We encourage you to take a look at already merged [GEPs]( https://github.com/gar
 ## Before creating a GEP
 
 Before starting your work and creating a GEP, please take some time to familiarize yourself with our
-general [Gardener Contribution Guidelines](https://gardener.cloud/documentation/contribute/).
+general [Gardener Contribution Guidelines](https://gardener.cloud/docs/contribute/).
 
 It is recommended to discuss and outline the motivation of your prospective GEP as a draft with the community before you take the investment of creating the actual GEP. This early briefing supports the understanding for the broad community and leads to a fast feedback for your proposal from the respective experts in the community.
 An appropriate format for this may be the regular [Gardener community meeting](https://github.com/gardener/documentation/blob/master/CONTRIBUTING.md#weekly-meeting).
@@ -38,7 +38,7 @@ the enhancement.
 
 Apart from general metadata, the GEP should name at least one "main reviewer".
 You can find a main reviewer for your GEP either when discussing the proposal in the community meeting, by asking in our
-[Slack Channel](https://gardener.cloud/documentation/contribute/#slack-channel) or at latest during the GEP PR review.
+[Slack Channel](https://gardener.cloud/docs/contribute/#slack-channel) or at latest during the GEP PR review.
 New GEPs should only be accepted once at least one main reviewer is nominated/assigned. 
 
 The main reviewers are charged with the following tasks:

docs/usage/shoot_status.md

@@ -1,10 +1,10 @@
 # Shoot Status
 
-This document provides an overview of the [ShootStatus](https://gardener.cloud/documentation/references/core/#core.gardener.cloud/v1beta1.ShootStatus).
+This document provides an overview of the [ShootStatus](https://gardener.cloud/docs/references/core/#core.gardener.cloud/v1beta1.ShootStatus).
 
 ## Conditions
 
-The Shoot status consists of a set of conditions. A [Condition](https://gardener.cloud/documentation/references/core/#core.gardener.cloud/v1beta1.Condition) has the following fields:
+The Shoot status consists of a set of conditions. A [Condition](https://gardener.cloud/docs/references/core/#core.gardener.cloud/v1beta1.Condition) has the following fields:
 
 | Field name           | Description                                                                                                        |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------ |
@@ -89,7 +89,7 @@ The Shoot status holds information about the last operation that is performed on
 
 ### Last Errors
 
-The Shoot status also contains information about the last occurred error(s) (if any) during an operation. A [LastError](https://gardener.cloud/documentation/references/core/#core.gardener.cloud/v1beta1.LastError) consists of identifier of the task returned error, human-readable message of the error and error codes (if any) associated with the error.
+The Shoot status also contains information about the last occurred error(s) (if any) during an operation. A [LastError](https://gardener.cloud/docs/references/core/#core.gardener.cloud/v1beta1.LastError) consists of identifier of the task returned error, human-readable message of the error and error codes (if any) associated with the error.
 
 ### Error Codes