docs: fix faker import + clarify codeceptjs internal-api intro

- data.md: faker is a named export; restore `import { faker }`
  and update the install hint from the legacy `faker` package
  to `@faker-js/faker`.
- internal-api.md: lead with the named-import form and demote
  the `codeceptjs` global to a footnote (it only exists when
  `noGlobals: false`).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: DavertMik

docs/data.md

@@ -258,13 +258,13 @@ Just define how many items of any kind you need and the data factory helper will
 
 To make this work some preparations are required.
 
-At first, you need data generation libraries which are [Rosie](https://github.com/rosiejs/rosie) and [Faker](https://www.npmjs.com/package/faker). Faker can generate random names, emails, texts, and Rosie uses them
+At first, you need data generation libraries which are [Rosie](https://github.com/rosiejs/rosie) and [Faker](https://fakerjs.dev). Faker can generate random names, emails, texts, and Rosie uses them
 to generate objects using factories.
 
 Install rosie and faker to create a first factory:
 
-```js
-npm i rosie faker --save-dev
+```sh
+npm i rosie @faker-js/faker --save-dev
 ```
 
 Then create a module which will export a factory for an entity.
@@ -290,7 +290,7 @@ See the example providing a factory for User generation:
 ```js
 // factories/post.js
 import { Factory } from 'rosie'
-import faker from '@faker-js/faker'
+import { faker } from '@faker-js/faker'
 
 export default new Factory().attr('name', () => faker.person.findName()).attr('email', () => faker.internet.email())
 ```
@@ -342,7 +342,7 @@ See the example providing a factory for User generation:
 ```js
 // factories/post.js
 import { Factory } from 'rosie'
-import faker from '@faker-js/faker'
+import { faker } from '@faker-js/faker'
 
 export default new Factory((buildObj) => {
   return {

docs/internal-api.md

@@ -8,15 +8,14 @@ title: Internal API
 In this guide we will overview the internal API of CodeceptJS.
 This knowledge is required for customization, writing plugins, etc.
 
-CodeceptJS provides an API which can be loaded via `import codeceptjs, { recorder, event, output } from 'codeceptjs'` when CodeceptJS is installed locally. Otherwise, you can load codeceptjs API via global `codeceptjs` object:
+CodeceptJS exposes its internal API as named exports of the `codeceptjs` package. Import only what you need:
 
 ```js
-// via module
-import { recorder, event, output } from 'codeceptjs';
-// or using global object
-const { recorder, event, output } = codeceptjs;
+import { recorder, event, output, container, config } from 'codeceptjs'
 ```
 
+> Older code may have relied on a global `codeceptjs` object (`const { recorder } = codeceptjs`). That global only exists under `noGlobals: false` (the deprecated 3.x default) — prefer named imports.
+
 These internal objects are available:
 
 * [`codecept`](https://github.com/Codeception/CodeceptJS/blob/master/lib/codecept.js): test runner class