diff --git a/docs/advanced/api/test-case.md b/docs/advanced/api/test-case.md
index 7453da2eaf60..f1d2c82695c9 100644
--- a/docs/advanced/api/test-case.md
+++ b/docs/advanced/api/test-case.md
@@ -61,7 +61,7 @@ The ID looks like this:
```
::: tip
-You can generate file hash with `generateFileHash` function from `vitest/node` which is available since Vitest 2.2:
+You can generate file hash with `generateFileHash` function from `vitest/node` which is available since Vitest 3:
```ts
import { generateFileHash } from 'vitest/node'
diff --git a/docs/advanced/api/test-project.md b/docs/advanced/api/test-project.md
index 5211827b6299..23856316d312 100644
--- a/docs/advanced/api/test-project.md
+++ b/docs/advanced/api/test-project.md
@@ -2,9 +2,9 @@
title: TestProject
---
-# TestProject 2.2.0 {#testproject}
+# TestProject 3.0.0 {#testproject}
-- **Alias**: `WorkspaceProject` before 2.2.0
+- **Alias**: `WorkspaceProject` before 3.0.0
::: warning
This guide describes the advanced Node.js API. If you just want to create a workspace, follow the ["Workspace"](/guide/workspace) guide.
diff --git a/docs/advanced/api/test-suite.md b/docs/advanced/api/test-suite.md
index 614c197d26c7..6e33f5d8c10f 100644
--- a/docs/advanced/api/test-suite.md
+++ b/docs/advanced/api/test-suite.md
@@ -62,7 +62,7 @@ The ID looks like this:
```
::: tip
-You can generate file hash with `generateFileHash` function from `vitest/node` which is available since Vitest 2.2:
+You can generate file hash with `generateFileHash` function from `vitest/node` which is available since Vitest 3:
```ts
import { generateFileHash } from 'vitest/node'
diff --git a/docs/advanced/api/vitest.md b/docs/advanced/api/vitest.md
index 8dfab0843b31..892780bc7b30 100644
--- a/docs/advanced/api/vitest.md
+++ b/docs/advanced/api/vitest.md
@@ -164,7 +164,7 @@ This method constructs new [test specifications](/advanced/api/test-specificatio
This method automatically caches all test specifications. When you call [`getModuleSpecifications`](#getmodulespecifications) next time, it will return the same specifications unless [`clearSpecificationsCache`](#clearspecificationscache) was called before that.
::: warning
-As of Vitest 2.2.0, it's possible to have multiple test specifications with the same module ID (file path) if `poolMatchGlob` has several pools or if `typecheck` is enabled. This possibility will be removed in Vitest 3.
+As of Vitest 3, it's possible to have multiple test specifications with the same module ID (file path) if `poolMatchGlob` has several pools or if `typecheck` is enabled. This possibility will be removed in Vitest 4.
:::
```ts
@@ -190,7 +190,7 @@ Returns a list of test specifications related to the module ID. The ID should al
This method can return already cached specifications based on the `moduleId` and `pool`. But note that [`project.createSpecification`](/advanced/api/test-project#createspecification) always returns a new instance and it's not cached automatically. However, specifications are automatically cached when [`runTestSpecifications`](#runtestspecifications) is called.
::: warning
-As of Vitest 2.2.0, this method uses a cache to check if the file is a test. To make sure that the cache is not empty, call [`globTestSpecifications`](#globtestspecifications) at least once.
+As of Vitest 3, this method uses a cache to check if the file is a test. To make sure that the cache is not empty, call [`globTestSpecifications`](#globtestspecifications) at least once.
:::
## clearSpecificationsCache
diff --git a/docs/guide/cli.md b/docs/guide/cli.md
index 789935c04760..062ddcd27d1c 100644
--- a/docs/guide/cli.md
+++ b/docs/guide/cli.md
@@ -19,7 +19,7 @@ vitest foobar
Will run only the test file that contains `foobar` in their paths. This filter only checks inclusion and doesn't support regexp or glob patterns (unless your terminal processes it before Vitest receives the filter).
-Since Vitest 2.2, you can also specify the test by filename and line number:
+Since Vitest 3, you can also specify the test by filename and line number:
```bash
$ vitest basic/foo.test.ts:10