Reword Notes & UIDs concept

content/en/docs/concepts/overview/working-with-objects/names.md

@@ -9,11 +9,13 @@ weight: 20
 
 {{% capture overview %}}
 
-All objects in the Kubernetes REST API are unambiguously identified by a Name and a UID.
+Each object in your cluster has a [Name](#names) that is unique for that type of resource.
+Every Kubernetes object also has a [UID](#uids) that is unique across your whole cluster.
 
-For non-unique user-provided attributes, Kubernetes provides [labels](/docs/user-guide/labels) and [annotations](/docs/concepts/overview/working-with-objects/annotations/).
+For example, you can only have one Pod named “myapp-1234”, but you can have one Pod
+and one Deployment that are each named “myapp-1234”.
 
-See the [identifiers design doc](https://git.k8s.io/community/contributors/design-proposals/architecture/identifiers.md) for the precise syntax rules for Names and UIDs.
+For non-unique user-provided attributes, Kubernetes provides [labels](/docs/concepts/overview/working-with-objects/labels/) and [annotations](/docs/concepts/overview/working-with-objects/annotations/).
 
 {{% /capture %}}
 
@@ -46,3 +48,7 @@ spec:
 {{< glossary_definition term_id="uid" length="all" >}}
 
 {{% /capture %}}
+{{% capture whatsnext %}}
+* Read about [labels](/docs/concepts/overview/working-with-objects/labels/) in Kubernetes.
+* See the design document for [Identifiers and Names in Kubernetes](https://git.k8s.io/community/contributors/design-proposals/architecture/identifiers.md), to find background information.
+{{% /capture %}}