Update links to avoid redirects. (#5614)

docs/concepts/overview/what-is-kubernetes.md

@@ -121,7 +121,7 @@ The name **Kubernetes** originates from Greek, meaning *helmsman* or *pilot*, an
 {% endcapture %}
 
 {% capture whatsnext %}
-*   Ready to [Get Started](/docs/getting-started-guides/)?
+*   Ready to [Get Started](/docs/home/)?
 *   For more details, see the [Kubernetes Documentation](/docs/home/).
 {% endcapture %}
 {% include templates/concept.md %}

docs/concepts/overview/working-with-objects/annotations.md

@@ -55,7 +55,7 @@ and the like.
 {% endcapture %}
 
 {% capture whatsnext %}
-Learn more about [Labels and Selectors](/docs/user-guide/labels/).
+Learn more about [Labels and Selectors](/docs/concepts/overview/working-with-objects/labels/).
 {% endcapture %}
 
 {% include templates/concept.md %}

docs/concepts/overview/working-with-objects/labels.md

@@ -130,7 +130,7 @@ $ kubectl get pods -l 'environment,environment notin (frontend)'
 
 ### Set references in API objects
 
-Some Kubernetes objects, such as [`services`](/docs/user-guide/services) and [`replicationcontrollers`](/docs/user-guide/replication-controller), also use label selectors to specify sets of other resources, such as [pods](/docs/user-guide/pods).
+Some Kubernetes objects, such as [`services`](/docs/concepts/services-networking/service/) and [`replicationcontrollers`](/docs/user-guide/replication-controller), also use label selectors to specify sets of other resources, such as [pods](/docs/user-guide/pods).
 
 #### Service and ReplicationController
 
@@ -170,4 +170,4 @@ selector:
 #### Selecting sets of nodes
 
 One use case for selecting over labels is to constrain the set of nodes onto which a pod can schedule.
-See the documentation on [node selection](/docs/user-guide/node-selection) for more information.
+See the documentation on [node selection](/docs/concepts/configuration/assign-pod-node/) for more information.

docs/concepts/overview/working-with-objects/namespaces.md

@@ -72,7 +72,7 @@ $ kubectl config view | grep namespace:
 
 ## Namespaces and DNS
 
-When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns).
+When you create a [Service](/docs/concepts/services-networking/service/), it creates a corresponding [DNS entry](/docs/admin/dns).
 This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
 that if a container just uses `<service-name>`, it will resolve to the service which
 is local to a namespace.  This is useful for using the same configuration across