diff --git a/docs/src/main/asciidoc/security.adoc b/docs/src/main/asciidoc/security.adoc
index 76f91057c4b9f..6e6815d721c03 100644
--- a/docs/src/main/asciidoc/security.adoc
+++ b/docs/src/main/asciidoc/security.adoc
@@ -15,7 +15,7 @@ Quarkus Security is a framework that provides the architecture, multiple authent
 Before you start building security into your Quarkus applications, review the overview information to learn about the Quarkus Security architecture and the different authentication and authorization mechanisms that Quarkus supports.
 
 To get started with security in Quarkus, we recommend that you first combine the Quarkus built-in xref:security-basic-auth-concept.adoc[Basic HTTP authentication] with the JPA identity provider to enable role-based access control (RBAC). 
-Complete the steps in the ref:security-getting-started.adoc[Secure a Quarkus application with Basic authentication] tutorial.
+Complete the steps in the xref:security-getting-started.adoc[Secure a Quarkus application with Basic authentication] tutorial.
 After you have successfully secured your Quarkus application with basic HTTP authentication, you can increase the security further by adding more advanced authentication mechanisms, for example, OpenID Connect (OIDC) authentication.
 
 == Security architecture
@@ -439,4 +439,4 @@ You can adjust the expiry date if you need to.
 == Quarkus Security testing
 
 When testing Quarkus security, ensure that  your `IdentityProvider` is already set with usernames, passwords, and roles in `application.properties`.
-For more information about testing Quarkus Security, see xref:security-testing.adoc#configuring-user-information[Configuring user information]. 
\ No newline at end of file
+For more information about testing Quarkus Security, see xref:security-testing.adoc#configuring-user-information[Configuring user information].