diff --git a/versioned_docs/version-2.6/pages-for-subheaders/authentication-config.md b/versioned_docs/version-2.6/pages-for-subheaders/authentication-config.md
index c1787591568..d28bfae8edb 100644
--- a/versioned_docs/version-2.6/pages-for-subheaders/authentication-config.md
+++ b/versioned_docs/version-2.6/pages-for-subheaders/authentication-config.md
@@ -26,7 +26,6 @@ The Rancher authentication proxy integrates with the following external authenti
 | [Google OAuth](../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-google-oauth.md)            |
 | [Shibboleth](configure-shibboleth-saml.md)           |
 
-<br/>
 However, Rancher also provides [local authentication](../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/create-local-users.md).
 
 In most cases, you should use an external authentication service over local authentication, as external authentication allows user management from a central location. However, you may want a few local authentication users for managing Rancher under rare circumstances, such as if your external authentication provider is unavailable or undergoing maintenance.