From 3b9f5ac77b61dd8a0c2788bb19450087fdc526b6 Mon Sep 17 00:00:00 2001 From: Desmond Silveira Date: Sat, 23 Jul 2022 09:40:07 -0700 Subject: [PATCH] "Well-Know" should be "Well-Known" --- .../ROOT/pages/features/authentication/password-storage.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/features/authentication/password-storage.adoc b/docs/modules/ROOT/pages/features/authentication/password-storage.adoc index a3a934e067..8b48504f44 100644 --- a/docs/modules/ROOT/pages/features/authentication/password-storage.adoc +++ b/docs/modules/ROOT/pages/features/authentication/password-storage.adoc @@ -499,7 +499,7 @@ XML Configuration requires the `NoOpPasswordEncoder` bean name to be `passwordEn Most applications that allow a user to specify a password also require a feature for updating that password. -https://w3c.github.io/webappsec-change-password-url/[A Well-Know URL for Changing Passwords] indicates a mechanism by which password managers can discover the password update endpoint for a given application. +https://w3c.github.io/webappsec-change-password-url/[A Well-Known URL for Changing Passwords] indicates a mechanism by which password managers can discover the password update endpoint for a given application. You can configure Spring Security to provide this discovery endpoint. For example, if the change password endpoint in your application is `/change-password`, then you can configure Spring Security like so: