docs: remove Crawlee references from graceful shutdown docs

This is a pure SDK feature - the framing about "with/without Crawlee
crawlers" was incorrect and confusing.

https://claude.ai/code/session_017U4px7vy75ioiTaC5teCaV

Author: claude

docs/02_concepts/01_actor_lifecycle.mdx

@@ -159,13 +159,7 @@ When running on the Apify platform, your Actor may receive signals to shut down
 - A user aborts the Actor run with the "abort gracefully" option (`aborting` event) — the Actor should save its state and exit
 - The platform needs to migrate your Actor to a different server (`migrating` event) — the Actor should save its state and reboot so the run continues on a new worker
 
-### With Crawlee crawlers
-
-If you're using Crawlee crawlers (like `CheerioCrawler`, `PlaywrightCrawler`, etc.), graceful shutdown is handled automatically. The crawler listens for these events and stops accepting new requests while finishing the ones in progress.
-
-### Without Crawlee crawlers
-
-If your Actor doesn't use Crawlee crawlers but still needs to respond to platform shutdown signals, you can enable automatic graceful shutdown by passing `gracefulShutdown: true` to `Actor.init()`:
+You can enable automatic handling of these events by passing `gracefulShutdown: true` to `Actor.init()`:
 
 ```js
 import { Actor } from 'apify';
@@ -181,9 +175,11 @@ await Actor.exit();
 
 When `gracefulShutdown` is enabled:
 
-- On `aborting`, the SDK calls `Actor.exit()`, which waits for all event handlers to complete before exiting. You can register cleanup handlers via the `exit` event.
+- On `aborting`, the SDK calls `Actor.exit()`, which waits for all event handlers to complete before exiting.
 - On `migrating`, the SDK calls `Actor.reboot()`, which also waits for all event handlers to complete, then restarts the Actor on a new worker so the run can continue.
 
+You can register cleanup handlers via the `persistState` event to save state before shutdown:
+
 ```js
 import { Actor } from 'apify';