diff --git a/docs/src/main/asciidoc/cassandra.adoc b/docs/src/main/asciidoc/cassandra.adoc
index 7a564da5d5203..bac46e7bb7e85 100644
--- a/docs/src/main/asciidoc/cassandra.adoc
+++ b/docs/src/main/asciidoc/cassandra.adoc
@@ -624,12 +624,10 @@ framework you plan to use.
 
 === Enabling Metrics with Micrometer
 
-Micrometer is the recommended metrics framework in Quarkus applications since Quarkus 1.9.
+Micrometer is the recommended metrics framework in Quarkus applications.
 
 To enable Micrometer metrics in your application, you need to add the following to your pom.xml.
 
-For Quarkus 1.11+:
-
 [source,xml]
 ----
 <dependency>
@@ -642,24 +640,6 @@ For Quarkus 1.11+:
 </dependency>
 ----
 
-For Quarkus < 1.11:
-
-[source,xml]
-----
-<dependency>
-  <groupId>com.datastax.oss</groupId>
-  <artifactId>java-driver-metrics-micrometer</artifactId>
-</dependency>
-<dependency>
-  <groupId>io.quarkus</groupId>
-  <artifactId>quarkus-micrometer</artifactId>
-</dependency>
-<dependency>
-  <groupId>io.micrometer</groupId>
-  <artifactId>micrometer-registry-prometheus</artifactId>
-</dependency>
-----
-
 This guide uses Micrometer, so the above dependencies are already included in this guide's pom.xml.
 
 === Enabling Metrics with MicroProfile Metrics
diff --git a/docs/src/main/asciidoc/reactive-sql-clients.adoc b/docs/src/main/asciidoc/reactive-sql-clients.adoc
index edcdc72ec8452..add2719590d56 100644
--- a/docs/src/main/asciidoc/reactive-sql-clients.adoc
+++ b/docs/src/main/asciidoc/reactive-sql-clients.adoc
@@ -197,13 +197,6 @@ client.query("DROP TABLE IF EXISTS fruits").execute()
     .await().indefinitely();
 ----
 
-[IMPORTANT]
-.Breaking Change in Quarkus 1.5
-====
-Vert.x 3.9, integrated in Quarkus 1.5, introduces a breaking change regarding the `query` methods.
-To retrieve the result you need to call `.execute()`.
-====
-
 NOTE: Wondering why we need block until the latest query is completed?
 This code is part of a `@PostConstruct` method and Quarkus invokes it synchronously.
 As a consequence, returning prematurely could lead to serving requests while the database is not ready yet.
diff --git a/docs/src/main/asciidoc/spring-data-jpa.adoc b/docs/src/main/asciidoc/spring-data-jpa.adoc
index cab25b0df1357..5c04e3681c369 100644
--- a/docs/src/main/asciidoc/spring-data-jpa.adoc
+++ b/docs/src/main/asciidoc/spring-data-jpa.adoc
@@ -606,8 +606,6 @@ is not used at all (since all the necessary plumbing is done at build time). Sim
 * Native and named queries when using `@Query`
 * https://github.com/spring-projects/spring-data-jpa/blob/main/src/main/asciidoc/jpa.adoc#entity-state-detection-strategies[Entity State-detection Strategies]
 via `EntityInformation`.
-** As of Quarkus 1.6.0, only "Version-Property and Id-Property inspection" is implemented (which should cover most cases).
-** As of Quarkus 1.7.0, `org.springframework.data.domain.Persistable` is also implemented.
 
 The Quarkus team is exploring various alternatives to bridging the gap between the JPA and Reactive worlds.
 
diff --git a/docs/src/main/asciidoc/writing-extensions.adoc b/docs/src/main/asciidoc/writing-extensions.adoc
index a2bce42b72645..a478062396b3c 100644
--- a/docs/src/main/asciidoc/writing-extensions.adoc
+++ b/docs/src/main/asciidoc/writing-extensions.adoc
@@ -940,8 +940,6 @@ to be 'Application Archives', and will therefore get indexed. This is done via t
 example the ArC extension registers `META-INF/beans.xml`, which means that all archives on the class path with a `beans.xml`
 file will be indexed.
 
-NOTE: `BuildStep.applicationArchiveMarkers()` is deprecated and will be removed at some point post Quarkus 1.1. Extensions are encouraged to use `io.quarkus.deployment.builditem.AdditionalApplicationArchiveMarkerBuildItem` instead.
-
 ==== Using Thread's Context Class Loader
 
 The build step will be run with a TCCL that can load user classes from the deployment in a transformer-safe way.