diff --git a/docs/src/main/asciidoc/lifecycle.adoc b/docs/src/main/asciidoc/lifecycle.adoc
index 0127ae8791abe..50f06c0f070f6 100644
--- a/docs/src/main/asciidoc/lifecycle.adoc
+++ b/docs/src/main/asciidoc/lifecycle.adoc
@@ -98,7 +98,7 @@ NOTE: The methods can access injected beans. Check the {quickstarts-blob-url}/li
 
 In the JVM mode, there is no real difference, except that `StartupEvent` is always fired *after* `@Initialized(ApplicationScoped.class)` and `ShutdownEvent` is fired *before* `@Destroyed(ApplicationScoped.class)`. 
 For a native executable build, however, `@Initialized(ApplicationScoped.class)` is fired as *part of the native build process*, whereas `StartupEvent` is fired when the native image is executed.
-See <<writing-extensions.adoc#bootstrap-three-phases,Three Phases of Bootstrap and Quarkus Philosophy>> for more details.
+See link:writing-extensions#bootstrap-three-phases[Three Phases of Bootstrap and Quarkus Philosophy] for more details.
 
 NOTE: In CDI applications, an event with qualifier `@Initialized(ApplicationScoped.class)` is fired when the application context is initialized. See https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#application_context[the spec, window="_blank"] for more info.
 
@@ -116,4 +116,4 @@ Quarkus has 3 different launch modes, `NORMAL` (i.e. production), `DEVELOPMENT`
 then the mode will be `DEVELOPMENT`, if you are running a JUnit test it will be `TEST`, otherwise it will be `NORMAL`.
 
 Your application can get the launch mode by injecting the `io.quarkus.runtime.LaunchMode` enum into a CDI bean,
-or by invoking the static method `io.quarkus.runtime.LaunchMode.current()`.
\ No newline at end of file
+or by invoking the static method `io.quarkus.runtime.LaunchMode.current()`.
diff --git a/docs/src/main/asciidoc/spring-security.adoc b/docs/src/main/asciidoc/spring-security.adoc
index 19c3aedba4060..f632ae19c9a0d 100644
--- a/docs/src/main/asciidoc/spring-security.adoc
+++ b/docs/src/main/asciidoc/spring-security.adoc
@@ -8,7 +8,7 @@ https://github.com/quarkusio/quarkus/tree/master/docs/src/main/asciidoc
 include::./attributes.adoc[]
 :extension-status: preview
 
-While users are encouraged to use <<security.adoc#standard-security-annotations,Java standard annotations for security authorizations>>, Quarkus provides a compatibility layer for Spring Security in the form of the `spring-security` extension.
+While users are encouraged to use link:security#standard-security-annotations[Java standard annotations for security authorizations], Quarkus provides a compatibility layer for Spring Security in the form of the `spring-security` extension.
 
 This guide explains how a Quarkus application can leverage the well known Spring Security annotations to define authorizations on RESTful services using roles.
 
@@ -51,7 +51,7 @@ cd spring-security-quickstart
 
 This command generates a Maven project with a REST endpoint and imports the `spring-web`, `spring-security` and `security-properties-file` extensions.
 
-For more information about `security-properties-file` you can check the guide of link:security-properties[quarkus-elytron-security-properties-file] extension.
+For more information about `security-properties-file`, you can check out the guide of the link:security-properties[quarkus-elytron-security-properties-file] extension.
 
 == GreetingController
 
@@ -141,7 +141,7 @@ public class GreetingController {
 ----
 
 The easiest way to setup users and roles for our example is to use the `security-properties-file` extension. This extension essentially allows users and roles to be defined in the main Quarkus configuration file - `application.properties`.
-For more information about this extension check link:security-properties.adoc[the associated guide].
+For more information about this extension check link:security-properties[the associated guide].
 An example configuration would be the following:
 
 [source,properties]