diff --git a/docs/content/2.guide/2.directory-structure/1.composables.md b/docs/content/2.guide/2.directory-structure/1.composables.md
index 43eb781288..f445cae21f 100644
--- a/docs/content/2.guide/2.directory-structure/1.composables.md
+++ b/docs/content/2.guide/2.directory-structure/1.composables.md
@@ -8,7 +8,7 @@ head.title: Composables Directory
 
 Nuxt 3 supports `composables/` directory to automatically import your Vue composables into your application using [auto-imports](/guide/concepts/auto-imports)!
 
-Under the hood, Nuxt auto generates the file `.nuxt/auto-imports.d.ts` to declare the types.
+Under the hood, Nuxt auto generates the file `.nuxt/imports.d.ts` to declare the types.
 
 Be aware that you have to run `nuxi prepare`, `nuxi dev` or `nuxi build` in order to let Nuxt generates the types. If you create a composable without having the dev server running, typescript will throw an error `Cannot find name 'useBar'.`
 
diff --git a/docs/content/migration/3.auto-imports.md b/docs/content/migration/3.auto-imports.md
index 4a8937322e..3d0812c747 100644
--- a/docs/content/migration/3.auto-imports.md
+++ b/docs/content/migration/3.auto-imports.md
@@ -18,5 +18,5 @@ In the rest of the migration documentation, you will notice that key Nuxt and Vu
 1. If you have been using `@nuxt/components` in Nuxt 2, you can remove `components: true` in your `nuxt.config`. If you had a more complex setup, then note that the component options have changed somewhat. See the [components documentation](/guide/directory-structure/components) for more information.
 
 ::alert{type=info}
-You can look at `.nuxt/types/components.d.ts` and `.nuxt/types/auto-imports.d.ts` to see how Nuxt has resolved your components and composable auto-imports.
+You can look at `.nuxt/types/components.d.ts` and `.nuxt/types/imports.d.ts` to see how Nuxt has resolved your components and composable auto-imports.
 ::