diff --git a/ee/ucp/admin/configure/enable-saml-authentication.md b/ee/ucp/admin/configure/enable-saml-authentication.md
index 85b620e40b..119f35b02a 100644
--- a/ee/ucp/admin/configure/enable-saml-authentication.md
+++ b/ee/ucp/admin/configure/enable-saml-authentication.md
@@ -82,9 +82,9 @@ To enable SAML authentication:
 
 ## Security considerations
 
-You can download a client bundle to access UCP. A client bundle is a group of certificates downloadable directly from UCP web interface that enables command line as well as API access to UCP. It lets you  authorize a remote Docker engine to a specific user account managed in Docker EE, absorbing all associated RBAC controls in the process. You can now execute docker swarm commands from your remote machine that take effect on the remote cluster. You can download the client bundle in the **Admin Settings** under **My Profile**.
+You can download a client bundle to access UCP. A client bundle is a group of certificates downloadable directly from UCP web interface that enables command line as well as API access to UCP. It lets you  authorize a remote Docker engine to access specific user account managed in Docker EE, absorbing all associated RBAC controls in the process. You can now execute docker swarm commands from your remote machine that take effect on the remote cluster. You can download the client bundle in the **Admin Settings** under **My Profile**.
 
-![Downloading UCP Client Profile] (../../images/client-bundle.png)
+![Downloading UCP Client Profile](../../images/client-bundle.png)
 
 To ensure that access from the client bundle is synced with the identity provider, we recommend the following steps. Otherwise, a previously-authorized user could get access to UCP through their existing client bundle.
 
diff --git a/ee/ucp/images/client-bundle.png b/ee/ucp/images/client-bundle.png
index 3d6a78a5eb..e4a419ada3 100644
Binary files a/ee/ucp/images/client-bundle.png and b/ee/ucp/images/client-bundle.png differ