docs: reduce clause-gluing dashes in the SDK docs prose

vdusek · vdusek · commit 35be39485e05 · 2026-06-08T13:44:20.000+02:00
diff --git a/docs/02_concepts/03_storages.mdx b/docs/02_concepts/03_storages.mdx
@@ -183,10 +183,10 @@ To check if all the requests in the queue are handled, you can use the <ApiLink
 
 ## Storage clients
 
-Behind the scenes, the SDK uses storage clients to communicate with the storage backend. The appropriate client is selected automatically based on the runtime environment — on the Apify platform, data is persisted via the Apify API, while local runs use the filesystem. For most use cases, you don't need to think about storage clients at all. To learn about the available implementations, how to switch between a single and shared request queue, or how to configure a custom client, see the [Storage clients](./storage-clients) page. For a deeper look at how storage clients work internally, see the [Crawlee storage clients guide](https://crawlee.dev/python/docs/guides/storage-clients).
+Behind the scenes, the SDK uses storage clients to communicate with the storage backend. The appropriate client is selected automatically based on the runtime environment. On the Apify platform, data is persisted via the Apify API, while local runs use the filesystem. For most use cases, you don't need to think about storage clients at all. To learn about the available implementations, how to switch between a single and shared request queue, or how to configure a custom client, see the [Storage clients](./storage-clients) page. For a deeper look at how storage clients work internally, see the [Crawlee storage clients guide](https://crawlee.dev/python/docs/guides/storage-clients).
 
 ## Conclusion
 
-This page has covered the three storage types — datasets, key-value stores, and request queues — how they are emulated on the local filesystem, how to open named and unnamed storages, and how to read from and write to each through the `Actor` shortcuts and the storage classes.
+This page has covered the three storage types (datasets, key-value stores, and request queues): how they are emulated on the local filesystem, how to open named and unnamed storages, and how to read from and write to each through the `Actor` shortcuts and the storage classes.
 
 For comprehensive information about storage on the Apify platform, see the [storage documentation](https://docs.apify.com/platform/storage), including the pages on [datasets](https://docs.apify.com/platform/storage/dataset), [key-value stores](https://docs.apify.com/platform/storage/key-value-store), and [request queues](https://docs.apify.com/platform/storage/request-queue).
diff --git a/docs/02_concepts/04_actor_events.mdx b/docs/02_concepts/04_actor_events.mdx
@@ -14,7 +14,7 @@ During its runtime, the Actor receives Actor events sent by the Apify platform o
 
 ## Event types
 
-A listener can optionally receive a single argument — a Pydantic model with the event's data. The table below lists the events, the type of that data object, and when each event is emitted.
+A listener can optionally receive a single argument, a Pydantic model with the event's data. The table below lists the events, the type of that data object, and when each event is emitted.
 
 <table>
     <thead>
@@ -105,6 +105,6 @@ You can optionally specify a `key` (the key-value store key under which the stat
 
 ## Conclusion
 
-This page has described the events emitted during a run — `SYSTEM_INFO`, `MIGRATING`, `ABORTING`, `PERSIST_STATE`, and `EXIT` — how to handle them with <ApiLink to="class/Actor#on">`Actor.on`</ApiLink>, and how to persist state automatically with <ApiLink to="class/Actor#use_state">`Actor.use_state`</ApiLink>.
+This page has described the events emitted during a run (`SYSTEM_INFO`, `MIGRATING`, `ABORTING`, `PERSIST_STATE`, and `EXIT`): how to handle them with <ApiLink to="class/Actor#on">`Actor.on`</ApiLink>, and how to persist state automatically with <ApiLink to="class/Actor#use_state">`Actor.use_state`</ApiLink>.
 
 For more details on platform events and state persistence, see the [system events](https://docs.apify.com/platform/actors/development/programming-interface/system-events) and [state persistence](https://docs.apify.com/platform/actors/development/state-persistence) documentation on the Apify platform.
diff --git a/docs/02_concepts/05_proxy_management.mdx b/docs/02_concepts/05_proxy_management.mdx
@@ -106,7 +106,7 @@ You can then use that input to create the proxy configuration:
 
 ## Using the generated proxy URLs
 
-`ProxyConfiguration` only generates proxy URLs — it does not make requests itself. Pass a generated URL to whichever HTTP client your Actor uses to route requests through the proxy.
+`ProxyConfiguration` only generates proxy URLs. It does not make requests itself. Pass a generated URL to whichever HTTP client your Actor uses to route requests through the proxy.
 
 ### HTTPX
 
@@ -124,6 +124,6 @@ pip install httpx
 
 ## Conclusion
 
-This page has explained how to manage proxies with the <ApiLink to="class/ProxyConfiguration">`ProxyConfiguration`</ApiLink> class — using Apify Proxy or your own servers, keeping sessions sticky across requests, configuring tiered proxy rotation, and feeding proxy settings from Actor input.
+This page has explained how to manage proxies with the <ApiLink to="class/ProxyConfiguration">`ProxyConfiguration`</ApiLink> class: using Apify Proxy or your own servers, keeping sessions sticky across requests, configuring tiered proxy rotation, and feeding proxy settings from Actor input.
 
 For full details on proxy configuration options, see the <ApiLink to="class/ProxyConfiguration">`ProxyConfiguration`</ApiLink> API reference and the [Apify Proxy documentation](https://docs.apify.com/proxy).
diff --git a/docs/02_concepts/06_interacting_with_other_actors.mdx b/docs/02_concepts/06_interacting_with_other_actors.mdx
@@ -65,6 +65,6 @@ When you set `gracefully=True`, the platform sends `ABORTING` and `PERSIST_STATE
 
 ## Conclusion
 
-This page has shown how to interact with other Actors from your code — starting a run with <ApiLink to="class/Actor#start">`Actor.start`</ApiLink>, waiting for it to finish with <ApiLink to="class/Actor#call">`Actor.call`</ApiLink> or <ApiLink to="class/Actor#call_task">`Actor.call_task`</ApiLink>, transforming a run with <ApiLink to="class/Actor#metamorph">`Actor.metamorph`</ApiLink>, and stopping one with <ApiLink to="class/Actor#abort">`Actor.abort`</ApiLink>.
+This page has shown how to interact with other Actors from your code: starting a run with <ApiLink to="class/Actor#start">`Actor.start`</ApiLink>, waiting for it to finish with <ApiLink to="class/Actor#call">`Actor.call`</ApiLink> or <ApiLink to="class/Actor#call_task">`Actor.call_task`</ApiLink>, transforming a run with <ApiLink to="class/Actor#metamorph">`Actor.metamorph`</ApiLink>, and stopping one with <ApiLink to="class/Actor#abort">`Actor.abort`</ApiLink>.
 
 For the full list of methods for interacting with other Actors, see the <ApiLink to="class/Actor">`Actor`</ApiLink> API reference. For more details on running Actors and Actor tasks on the platform, see the [Actors](https://docs.apify.com/platform/actors) and [Actor tasks](https://docs.apify.com/platform/actors/tasks) documentation.
diff --git a/docs/02_concepts/08_access_apify_api.mdx b/docs/02_concepts/08_access_apify_api.mdx
@@ -12,7 +12,7 @@ import ActorNewClientExample from '!!raw-loader!roa-loader!./code/08_actor_new_c
 
 The Apify SDK provides a built-in instance of the [Apify API Client](https://docs.apify.com/api/client/python) for accessing Apify platform features beyond what the SDK covers directly.
 
-The SDK wraps the most common operations — opening storages, reading input, charging, and starting other Actors — in convenient high-level methods. When you need something it does not expose directly, such as managing schedules, listing your Actors and runs, working with builds or webhook dispatches, or reading another run's dataset, you can reach the full [Apify API](https://docs.apify.com/api/v2) through the client. It provides a dedicated sub-client for each API resource — among them `dataset`, `key_value_store`, `request_queue`, `run`, `actor`, `task`, `schedule`, `webhook`, and `user` — and each operation returns plain Python data structures.
+The SDK wraps the most common operations (opening storages, reading input, charging, and starting other Actors) in convenient high-level methods. When you need something it does not expose directly, such as managing schedules, listing your Actors and runs, working with builds or webhook dispatches, or reading another run's dataset, you can reach the full [Apify API](https://docs.apify.com/api/v2) through the client. It provides a dedicated sub-client for each API resource (among them `dataset`, `key_value_store`, `request_queue`, `run`, `actor`, `task`, `schedule`, `webhook`, and `user`), and each operation returns plain Python data structures.
 
 ## Actor client
 
@@ -24,20 +24,20 @@ For example, to get the details of your user, you can use this snippet:
     {ActorClientExample}
 </RunnableCodeBlock>
 
-You select a resource with the matching method — for example `Actor.apify_client.dataset('<dataset_id>')` for a dataset or `Actor.apify_client.run('<run_id>')` for an Actor run — and then call the operation you need on the returned sub-client.
+You select a resource with the matching method (for example, `Actor.apify_client.dataset('<dataset_id>')` for a dataset or `Actor.apify_client.run('<run_id>')` for an Actor run), and then call the operation you need on the returned sub-client.
 
 ## Actor new client
 
-If you want to create a completely new instance of the client — for example, to use a different user's token or change the client configuration — you can use the <ApiLink to="class/Actor#new_client">`Actor.new_client`</ApiLink> method. It accepts an optional `token` and `api_url`, along with retry and timeout settings (`max_retries`, `min_delay_between_retries`, `timeout`), and returns a fresh `ApifyClientAsync`:
+If you want to create a completely new instance of the client (for example, to use a different user's token or change the client configuration), you can use the <ApiLink to="class/Actor#new_client">`Actor.new_client`</ApiLink> method. It accepts an optional `token` and `api_url`, along with retry and timeout settings (`max_retries`, `min_delay_between_retries`, `timeout`), and returns a fresh `ApifyClientAsync`:
 
 <RunnableCodeBlock className="language-python" language="python">
     {ActorNewClientExample}
 </RunnableCodeBlock>
 
-This is useful when the Actor's own token is not the right one — for instance, when acting on behalf of another user — or when you want different retry and timeout behavior than the shared `Actor.apify_client` instance.
+This is useful when the Actor's own token is not the right one, for instance when acting on behalf of another user, or when you want different retry and timeout behavior than the shared `Actor.apify_client` instance.
 
 ## Conclusion
 
-This page has shown how to reach the Apify API directly — through the built-in client exposed by <ApiLink to="class/Actor#apify_client">`Actor.apify_client`</ApiLink>, or a freshly configured one created with <ApiLink to="class/Actor#new_client">`Actor.new_client`</ApiLink> — for platform features the SDK does not wrap directly.
+This page has shown how to reach the Apify API directly for platform features the SDK does not wrap. You can use the built-in client exposed by <ApiLink to="class/Actor#apify_client">`Actor.apify_client`</ApiLink>, or a freshly configured one created with <ApiLink to="class/Actor#new_client">`Actor.new_client`</ApiLink>.
 
 For the full API client documentation, see the [Apify API Client for Python](https://docs.apify.com/api/client/python).
diff --git a/docs/02_concepts/09_logging.mdx b/docs/02_concepts/09_logging.mdx
@@ -20,7 +20,7 @@ When you create an Actor from an Apify-provided template, either in Apify Consol
 
 ## Manual configuration
 
-If you are not using an Apify template — or you want to override what it sets up — you can configure the log level and the log formatting yourself.
+If you are not using an Apify template, or you want to override what it sets up, you can configure the log level and the log formatting yourself.
 
 ### Configuring the log level
 
@@ -119,4 +119,4 @@ You can further decide whether you want to redirect just new logs of the ongoing
 
 ## Conclusion
 
-This page has covered how the SDK logs through the `apify` logger — setting the log level, formatting output with <ApiLink to="class/ActorLogFormatter">`ActorLogFormatter`</ApiLink>, using the logger at each level, and redirecting logs from other Actor runs back into the parent run. For more on the underlying logging machinery, see Python's standard [`logging`](https://docs.python.org/3/library/logging.html) module documentation.
+This page has covered how the SDK logs through the `apify` logger: setting the log level, formatting output with <ApiLink to="class/ActorLogFormatter">`ActorLogFormatter`</ApiLink>, using the logger at each level, and redirecting logs from other Actor runs back into the parent run. For more on the underlying logging machinery, see Python's standard [`logging`](https://docs.python.org/3/library/logging.html) module documentation.
diff --git a/docs/02_concepts/10_configuration.mdx b/docs/02_concepts/10_configuration.mdx
@@ -27,7 +27,7 @@ This will cause the Actor to persist its state every 10 seconds:
 
 ## Configuring via environment variables
 
-All configuration options can also be set via environment variables. Most options are read from an environment variable named after the option in uppercase; many options accept several aliases — commonly with an `APIFY_`, `ACTOR_`, or `CRAWLEE_` prefix. See the <ApiLink to="class/Configuration">`Configuration`</ApiLink> API reference for the full list of configuration options.
+All configuration options can also be set via environment variables. Most options are read from an environment variable named after the option in uppercase; many options accept several aliases, commonly with an `APIFY_`, `ACTOR_`, or `CRAWLEE_` prefix. See the <ApiLink to="class/Configuration">`Configuration`</ApiLink> API reference for the full list of configuration options.
 
 For example, this Actor run will keep the contents of its local storages instead of purging them on start:
 
@@ -48,7 +48,7 @@ The table below lists a few options you are most likely to set yourself. When ru
 | `log_level` | `APIFY_LOG_LEVEL` | `'INFO'` | Minimum severity of log messages that are printed. |
 | `headless` | `APIFY_HEADLESS` | `True` | Whether to run browsers in headless mode. |
 | `storage_dir` | `APIFY_LOCAL_STORAGE_DIR` | `'./storage'` | Directory holding local storages when running outside the platform. |
-| `is_at_home` | `APIFY_IS_AT_HOME` | `False` | Set by the platform — `True` when the Actor runs on Apify. |
+| `is_at_home` | `APIFY_IS_AT_HOME` | `False` | Set by the platform. `True` when the Actor runs on Apify. |
 
 ## Reading the runtime environment
 
diff --git a/docs/02_concepts/11_pay_per_event.mdx b/docs/02_concepts/11_pay_per_event.mdx
@@ -79,6 +79,6 @@ Because pricing configuration is stored by the Apify platform, all events will h
 
 ## Conclusion
 
-This page has covered the pay-per-event pricing model — charging for events with <ApiLink to="class/Actor#charge">`Actor.charge`</ApiLink>, respecting the charge limit so your Actor stops once the budget is exhausted, querying the <ApiLink to="class/ChargingManager">`ChargingManager`</ApiLink>, handling the transition from another pricing model, and testing charging locally.
+This page has covered the pay-per-event pricing model: charging for events with <ApiLink to="class/Actor#charge">`Actor.charge`</ApiLink>, respecting the charge limit so your Actor stops once the budget is exhausted, querying the <ApiLink to="class/ChargingManager">`ChargingManager`</ApiLink>, handling the transition from another pricing model, and testing charging locally.
 
 For comprehensive details on pay-per-event pricing and Actor monetization, see the [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) and [monetization](https://docs.apify.com/platform/actors/publishing/monetize) documentation on the Apify platform.
diff --git a/docs/02_concepts/12_storage_clients.mdx b/docs/02_concepts/12_storage_clients.mdx
