[DOCS] Updates links to user APIs

Author: lcawl

docs/en/stack/security/authentication/built-in-users.asciidoc

@@ -27,7 +27,7 @@ Although they share the same API, the built-in users are separate and distinct
 from users managed by the <<native-realm, native realm>>. Disabling the native
 realm will not have any effect on the built-in users. The built-in users can
 be disabled individually, using the
-{ref}/security-api-users.html[user management API].
+{ref}/security-api-disable-user.html[disable users API].
 
 [float]
 [[bootstrap-elastic-passwords]]

docs/en/stack/security/authentication/native-realm.asciidoc

@@ -24,7 +24,7 @@ See {ref}/security-settings.html#ref-native-settings[Native realm settings].
 *Management / Security / Users* page. 
 
 Alternatively, you can manage users through the `user` API. For more 
-information and examples, see {ref}/security-api-users.html[User management APIs].
+information and examples, see {ref}/security-api.html#security-user-apis[user management APIs].
 
 [[migrating-from-file]]
 NOTE: To migrate file-based users to the `native` realm, use the

docs/en/stack/security/authentication/realms.asciidoc

@@ -10,8 +10,8 @@ _native_::
 An internal realm where users are stored in a dedicated {es} index.
 This realm supports an authentication token in the form of username and password,
 and is available by default when no realms are explicitly configured. The users
-are managed via the {ref}/security-api-users.html[User Management API]. See
-<<native-realm>>.
+are managed via the {ref}/security-api.html#security-user-apis[user management APIs]. 
+See <<native-realm>>.
 
 _ldap_::
 A realm that uses an external LDAP server to authenticate the