diff --git a/docs/extensions/versioning_of_extensions.md b/docs/extensions/versioning_of_extensions.md
index 4a3f3582c4a..d227dfcdc57 100644
--- a/docs/extensions/versioning_of_extensions.md
+++ b/docs/extensions/versioning_of_extensions.md
@@ -75,4 +75,4 @@ UPDATE EXTENSIONS (httpfs, azure);
 
 ## Target DuckDB Version
 
-Currently, when extensions are compiled, they are tied to a specific version of DuckDB. What this means is that, for example, an extension binary compiled for v0.9.2 does not work for v0.10.3. In most cases, this will not cause any issues and is fully transparent; DuckDB will automatically ensure it installs the correct binary for its version. For extension developers, this means that they must ensure that new binaries are created whenever a new version of DuckDB is released. However, note that DuckDB provides an [extension template](https://github.com/duckdb/extension-template) that makes this fairly simple.
+Currently, when extensions are compiled, they are tied to a specific version of DuckDB. What this means is that, for example, an extension binary compiled for v0.10.3 does not work for v1.0.0. In most cases, this will not cause any issues and is fully transparent; DuckDB will automatically ensure it installs the correct binary for its version. For extension developers, this means that they must ensure that new binaries are created whenever a new version of DuckDB is released. However, note that DuckDB provides an [extension template](https://github.com/duckdb/extension-template) that makes this fairly simple.