Rs rollingupdate

content/en/docs/concepts/workloads/controllers/replicaset.md

@@ -281,7 +281,7 @@ curl -X DELETE  'localhost:8080/apis/extensions/v1beta1/namespaces/default/repli
 Once the original is deleted, you can create a new ReplicaSet to replace it.  As long
 as the old and new `.spec.selector` are the same, then the new one will adopt the old Pods.
 However, it will not make any effort to make existing Pods match a new, different pod template.
-To update Pods to a new spec in a controlled way, use a [rolling update](#rolling-updates).
+To update Pods to a new spec in a controlled way, use a [Deployment](/docs/concepts/workloads/controllers/deployment/#creating-a-deployment), as ReplicaSets do not support a rolling update directly.
 
 ### Isolating Pods from a ReplicaSet
 

content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md

@@ -58,6 +58,10 @@ If you use a Docker credentials store, you won't see that `auth` entry but a `cr
 
 ## Create a Secret based on existing Docker credentials {#registry-secret-existing-credentials}
 
+{{< note >}}
+If you are using Kubernetes on Mac, you will need to provide credentials [via the command line](/#Create a Secret by providing credentials on the command line)
+{{< /note >}}
+
 A Kubernetes cluster uses the Secret of `docker-registry` type to authenticate with
 a container registry to pull a private image.