docs: restore v2.5 docs snapshot and add missing v3.0 versioned docs (#808)

The v3.0.0 docs versioning run snapshotted docs using the pre-bump
version (`2.5.1`), which overwrote `version-2.5` with v3 content and
never created `version-3.0`. This PR restores the correct historical
`2.5` snapshot and adds a proper `3.0` snapshot from current docs.

- **Restore `2.5` to the last known good snapshot**
- Replaced `website/versioned_docs/version-2.5/` with the tree from
`5f7f7b1`.
- Restored `website/versioned_sidebars/version-2.5-sidebars.json` to
match that snapshot.
- Removes v3-only docs from `2.5` (e.g. `upgrading_to_v3.mdx`, custom
HTTP client/timeouts/typed-models concept pages).

- **Create a proper `3.0` versioned snapshot**
- Added `website/versioned_docs/version-3.0/` from current `docs/` + API
versioned output.
- Added `website/versioned_sidebars/version-3.0-sidebars.json` and
reformatted to 4-space indentation to match existing versioned sidebar
files.
- Ensures v3-only docs are present under `3.0` (including
`upgrading_to_v3.mdx` and new concepts docs), with the larger v3
`api-typedoc.json`.

- **Correct version registry ordering**
  - Updated `website/versions.json` to:
    ```json
    ["3.0", "2.5", "1.12", "0.6"]
    ```

- **Keep versioned snapshot clean**
- Removed root-gitignored carryovers from `version-3.0` (`.ruff_cache`,
`changelog.md`, `pyproject.toml`).

Author: Copilot

website/versioned_docs/version-2.5/01_introduction/code/03_input_async.py

@@ -12,5 +12,5 @@ async def main() -> None:
         'some': 'input',
     }
 
-    # Start an Actor and wait for it to finish.
+    # Start an Actor and waits for it to finish.
     call_result = await actor_client.call(run_input=run_input)

website/versioned_docs/version-2.5/01_introduction/code/03_input_sync.py

@@ -12,5 +12,5 @@ def main() -> None:
         'some': 'input',
     }
 
-    # Start an Actor and wait for it to finish.
+    # Start an Actor and waits for it to finish.
     call_result = actor_client.call(run_input=run_input)

website/versioned_docs/version-2.5/01_introduction/index.mdx

@@ -1,8 +1,9 @@
 ---
 id: introduction
 title: Overview
+sidebar_label: Overview
 slug: /
-description: The official Python library to access the Apify API, with automatic retries, async support, and comprehensive API coverage.
+description: "The official Python library to access the Apify API, with automatic retries, async support, and comprehensive API coverage."
 ---
 
 import Tabs from '@theme/Tabs';
@@ -23,7 +24,7 @@ The client simplifies interaction with the Apify platform by providing:
 
 ## Prerequisites
 
-`apify-client` requires Python 3.11 or higher. Python is available for download on the [official website](https://www.python.org/downloads/). Check your current Python version by running:
+`apify-client` requires Python 3.10 or higher. Python is available for download on the [official website](https://www.python.org/downloads/). Check your current Python version by running:
 
 ```bash
 python --version
@@ -39,7 +40,7 @@ pip install apify-client
 
 ## Quick example
 
-The following example shows how to run an Actor and retrieve its results:
+Here's an example showing how to run an Actor and retrieve its results:
 
 <Tabs>
     <TabItem value="AsyncExample" label="Async client" default>

website/versioned_docs/version-2.5/01_introduction/quick-start.mdx

@@ -1,7 +1,8 @@
 ---
 id: quick-start
 title: Quick start
-description: Get started with the Apify API client for Python by running an Actor and retrieving results from its dataset.
+sidebar_label: Quick start
+description: "Get started with the Apify API client for Python by running an Actor and retrieving results from its dataset."
 ---
 
 import Tabs from '@theme/Tabs';

website/versioned_docs/version-2.5/02_concepts/01_async_support.mdx

@@ -1,7 +1,6 @@
 ---
 id: asyncio-support
 title: Asyncio support
-description: Use the async client for non-blocking API calls with Python asyncio.
 ---
 
 import Tabs from '@theme/Tabs';
@@ -11,12 +10,10 @@ import ApiLink from '@theme/ApiLink';
 
 import AsyncSupportExample from '!!raw-loader!./code/01_async_support.py';
 
-The package provides an asynchronous version of the client, <ApiLink to="class/ApifyClientAsync">`ApifyClientAsync`</ApiLink>, which allows you to interact with the Apify API using Python's standard async/await syntax. This enables you to perform non-blocking operations, see the Python [asyncio documentation](https://docs.python.org/3/library/asyncio-task.html) for more information. This is useful for applications that need to perform multiple API operations concurrently or integrate with other async frameworks.
+The package provides an asynchronous version of the client, <ApiLink to="class/ApifyClientAsync">`ApifyClientAsync`</ApiLink>, which allows you to interact with the Apify API using Python's standard async/await syntax. This enables you to perform non-blocking operations, see the Python [asyncio documentation](https://docs.python.org/3/library/asyncio-task.html) for more information.
 
-The following example shows how to run an Actor asynchronously and stream its logs while it is running:
+The following example demonstrates how to run an Actor asynchronously and stream its logs while it is running:
 
 <CodeBlock className="language-python">
     {AsyncSupportExample}
 </CodeBlock>
-
-For the full async client API, see the <ApiLink to="class/ApifyClientAsync">`ApifyClientAsync`</ApiLink> reference.

website/versioned_docs/version-2.5/02_concepts/02_single_collection_clients.mdx

@@ -1,7 +1,6 @@
 ---
 id: single-and-collection-clients
 title: Single and collection clients
-description: Understand the two types of resource clients, single-resource and collection clients.
 ---
 
 import Tabs from '@theme/Tabs';
@@ -15,7 +14,7 @@ import CollectionSyncExample from '!!raw-loader!./code/02_collection_sync.py';
 import SingleAsyncExample from '!!raw-loader!./code/02_single_async.py';
 import SingleSyncExample from '!!raw-loader!./code/02_single_sync.py';
 
-The Apify client provides two types of resource clients: single-resource clients for managing an individual resource, and collection clients for listing or creating resources.
+The Apify client interface is designed to be consistent and intuitive across all of its components. When you call specific methods on the main client, you create specialized clients to manage individual API resources. There are two main types of clients:
 
 - <ApiLink to="class/ActorClient">`ActorClient`</ApiLink> - Manages a single resource.
 - <ApiLink to="class/ActorCollectionClient">`ActorCollectionClient`</ApiLink> - Manages a collection of resources.

website/versioned_docs/version-2.5/02_concepts/03_nested_clients.mdx

@@ -1,7 +1,6 @@
 ---
 id: nested-clients
 title: Nested clients
-description: Access related resources directly through nested client methods.
 ---
 
 import Tabs from '@theme/Tabs';
@@ -13,7 +12,7 @@ import ApiLink from '@theme/ApiLink';
 import NestedAsyncExample from '!!raw-loader!./code/03_nested_async.py';
 import NestedSyncExample from '!!raw-loader!./code/03_nested_sync.py';
 
-Nested clients let you access related resources directly from a parent resource client, without manually constructing new client instances.
+In some cases, the Apify client provides nested clients to simplify working with related collections. For example, you can easily manage the runs of a specific Actor without having to construct multiple endpoints or client instances manually.
 
 <Tabs>
     <TabItem value="AsyncExample" label="Async client" default>

website/versioned_docs/version-2.5/02_concepts/04_error_handling.mdx

@@ -1,7 +1,6 @@
 ---
 id: error-handling
 title: Error handling
-description: Handle API errors with the ApifyApiError exception and automatic data parsing.
 ---
 
 import Tabs from '@theme/Tabs';
@@ -14,22 +13,6 @@ import ErrorSyncExample from '!!raw-loader!./code/04_error_sync.py';
 
 When you use the Apify client, it automatically extracts all relevant data from the endpoint and returns it in the expected format. Date strings, for instance, are seamlessly converted to Python `datetime.datetime` objects. If an error occurs, the client raises an <ApiLink to="class/ApifyApiError">`ApifyApiError`</ApiLink>. This exception wraps the raw JSON errors returned by the API and provides additional context, making it easier to debug any issues that arise.
 
-## Error subclasses
-
-The Apify client provides dedicated error subclasses based on the HTTP status code of the failed response, so you can branch on error kind without inspecting `status_code` or `type`:
-
-| Status | Subclass |
-|---|---|
-| 400 | <ApiLink to="class/InvalidRequestError">`InvalidRequestError`</ApiLink> |
-| 401 | <ApiLink to="class/UnauthorizedError">`UnauthorizedError`</ApiLink> |
-| 403 | <ApiLink to="class/ForbiddenError">`ForbiddenError`</ApiLink> |
-| 404 | <ApiLink to="class/NotFoundError">`NotFoundError`</ApiLink> |
-| 409 | <ApiLink to="class/ConflictError">`ConflictError`</ApiLink> |
-| 429 | <ApiLink to="class/RateLimitError">`RateLimitError`</ApiLink> |
-| 5xx | <ApiLink to="class/ServerError">`ServerError`</ApiLink> |
-
-All subclasses inherit from <ApiLink to="class/ApifyApiError">`ApifyApiError`</ApiLink>, so an existing `except ApifyApiError` handler still catches every API error. Catch a specific subclass when you want to react differently to, for example, a missing resource or a rate-limit:
-
 <Tabs>
     <TabItem value="AsyncExample" label="Async client" default>
         <CodeBlock className="language-python">
@@ -42,5 +25,3 @@ All subclasses inherit from <ApiLink to="class/ApifyApiError">`ApifyApiError`</A
         </CodeBlock>
     </TabItem>
 </Tabs>
-
-For a complete list of error classes, see the <ApiLink to="class/ApifyApiError">`ApifyApiError`</ApiLink> reference.

website/versioned_docs/version-2.5/02_concepts/05_retries.mdx

@@ -1,7 +1,6 @@
 ---
 id: retries
 title: Retries
-description: Configure automatic retries with exponential backoff for failed requests.
 ---
 
 import Tabs from '@theme/Tabs';
@@ -13,23 +12,23 @@ import ApiLink from '@theme/ApiLink';
 import RetriesAsyncExample from '!!raw-loader!./code/05_retries_async.py';
 import RetriesSyncExample from '!!raw-loader!./code/05_retries_sync.py';
 
-The Apify client automatically retries requests that fail due to:
+When dealing with network communication, failures can occasionally occur. The Apify client automatically retries requests that fail due to:
 
 - Network errors
 - Internal errors in the Apify API (HTTP status codes 500 and above)
 - Rate limit errors (HTTP status code 429)
 
-By default, the client retries a failed request up to 4 times. The retry intervals use an exponential backoff strategy:
+By default, the client will retry a failed request up to 8 times. The retry intervals use an exponential backoff strategy:
 
 - The first retry occurs after approximately 500 milliseconds.
 - The second retry occurs after approximately 1,000 milliseconds, and so on.
 
 You can customize this behavior using the following options in the <ApiLink to="class/ApifyClient">`ApifyClient`</ApiLink> constructor:
 
 - `max_retries`: Defines the maximum number of retry attempts.
-- `min_delay_between_retries`: Sets the minimum delay between retries as a `timedelta`.
+- `min_delay_between_retries_millis`: Sets the minimum delay between retries (in milliseconds).
 
-Retries with exponential backoff help reduce the load on the server and increase the chances of a successful request.
+Retries with exponential backoff are a common strategy for handling network errors. They help to reduce the load on the server and increase the chances of a successful request.
 
 <Tabs>
     <TabItem value="AsyncExample" label="Async client" default>

website/versioned_docs/version-2.5/02_concepts/06_logging.mdx

@@ -1,7 +1,6 @@
 ---
 id: logging
 title: Logging
-description: Configure debug logging to inspect API requests and responses.
 ---
 
 import Tabs from '@theme/Tabs';