Skip to content

Crawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.

docs: fix typo `ini()` -> `init()`

Martin Adámek86ac35326547
diff --git a/docs/introduction/09-deployment.mdx b/docs/introduction/09-deployment.mdx
index 65f76c6ed..8f1713e9b 100644
--- a/docs/introduction/09-deployment.mdx
+++ b/docs/introduction/09-deployment.mdx
@@ -77,7 +77,7 @@ await Actor.exit();
The `Actor.init()` call will configure Crawlee to use the Apify API instead of its default memory storage interface. It also sets up few other things, like listening to the platform events via websockets. The `Actor.exit()` call then handles graceful shutdown - it will close the open handles created by the `Actor.init()` call, as without that, the Node.js process would be stuck.
-:::info Understanding `Actor.ini()` behavior with environment variables
+:::info Understanding `Actor.init()` behavior with environment variables
The `Actor.init()` call works conditionally based on the environment variables, namely based on the `APIFY_IS_AT_HOME` env var, which is set to `true` on the Apify Platform. This means that your project will remain working the same locally, but will use the Apify API when deployed to the Apify Platform.
diff --git a/website/versioned_docs/version-3.8/introduction/09-deployment.mdx b/website/versioned_docs/version-3.8/introduction/09-deployment.mdx
index 65f76c6ed..8f1713e9b 100644
--- a/website/versioned_docs/version-3.8/introduction/09-deployment.mdx
+++ b/website/versioned_docs/version-3.8/introduction/09-deployment.mdx
@@ -77,7 +77,7 @@ await Actor.exit();
The `Actor.init()` call will configure Crawlee to use the Apify API instead of its default memory storage interface. It also sets up few other things, like listening to the platform events via websockets. The `Actor.exit()` call then handles graceful shutdown - it will close the open handles created by the `Actor.init()` call, as without that, the Node.js process would be stuck.
-:::info Understanding `Actor.ini()` behavior with environment variables
+:::info Understanding `Actor.init()` behavior with environment variables
The `Actor.init()` call works conditionally based on the environment variables, namely based on the `APIFY_IS_AT_HOME` env var, which is set to `true` on the Apify Platform. This means that your project will remain working the same locally, but will use the Apify API when deployed to the Apify Platform.