From 35a4934a85da71a8cb736b7a4914b3f3e1416f3d Mon Sep 17 00:00:00 2001 From: David Deyo Date: Fri, 2 Nov 2018 13:30:58 -0700 Subject: [PATCH] Update release-notes.md --- ee/ucp/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ee/ucp/release-notes.md b/ee/ucp/release-notes.md index 12c2d61770..068507c848 100644 --- a/ee/ucp/release-notes.md +++ b/ee/ucp/release-notes.md @@ -77,7 +77,7 @@ There are several backward-incompatible changes in the Kubernetes API that may a ## Known issues * There are important changes to the upgrade process that, if not correctly followed, can impact the availability of applications running on the Swarm during uprades. These constraints impact any upgrades coming from any Docker Engine version before 18.09 to version 18.09 or greater. For more information about about upgrading Docker Enterprise to version 2.1, see [Upgrade Docker](../upgrade) -* In the UCP web interface, LDAP settings disappear after submitting them. However, the sattings are properly saved. (#15503) +* In the UCP web interface, LDAP settings disappear after submitting them. However, the settings are properly saved. (#15503) * You must use the ID of the user, organization, or team if you manually create a **ClusterRoleBinding** or **RoleBinding** for `User` or `Group` subjects. (#14935) * For the `User` subject Kind, the `Name` field contains the ID of the user.