diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md
index e215b31716..b6421e71c2 100644
--- a/docs/admin/multiple-zones.md
+++ b/docs/admin/multiple-zones.md
@@ -51,7 +51,7 @@ admission controller automatically adds zone labels to them.  The scheduler (via
 `VolumeZonePredicate` predicate) will then ensure that pods that claim a
 given volume are only placed into the same zone as that volume, as volumes
 cannot be attached across zones.
- 
+
 ## Limitations
 
 There are some important limitations of the multizone support:
@@ -158,8 +158,7 @@ kubernetes-minion-wf8i   Ready                      2m        beta.kubernetes.io
 
 ### Volume affinity
 
-Create a volume (only PersistentVolumes are supported for zone
-affinity), using the new dynamic volume creation:
+Create a volume using the dynamic volume creation (only PersistentVolumes are supported for zone affinity):
 
 ```json
 kubectl create -f - <<EOF
@@ -186,10 +185,14 @@ kubectl create -f - <<EOF
 EOF
 ```
 
-The PV is also labeled with the zone & region it was created in.  For
-version 1.2, dynamic persistent volumes are always created in the zone
-of the cluster master (here us-central1-a / us-west-2a); this will
-be improved in a future version (issue [#23330](https://github.com/kubernetes/kubernetes/issues/23330).)
+**NOTE:** For version 1.3+ Kubernetes will distribute dynamic PV claims across
+the configured zones. For version 1.2, dynamic persistent volumes were
+always created in the zone of the cluster master
+(here us-central1-a / us-west-2a); that issue
+([#23330](https://github.com/kubernetes/kubernetes/issues/23330))
+was addressed in 1.3+.
+
+Now lets validate that Kubernetes automatically labeled the zone & region the PV was created in.
 
 ```shell
 > kubectl get pv --show-labels