Update contributing guide

Author: vdusek

CONTRIBUTING.md

@@ -11,6 +11,24 @@ We use [uv](https://docs.astral.sh/uv/) for project management. Install it and s
 We use [Poe the Poet](https://poethepoet.natn.io/) as a task runner, similar to npm scripts in `package.json`.
 All tasks are defined in `pyproject.toml` under `[tool.poe.tasks]` and can be run with `uv run poe <task>`.
 
+### Available tasks
+
+| Task | Description |
+| ---- | ----------- |
+| `install-dev` | Install dependencies and pre-commit hooks |
+| `check-code` | Run lint, type-check, and unit-tests |
+| `lint` | Run linter |
+| `format` | Fix lint issues and format code |
+| `type-check` | Run type checker |
+| `unit-tests` | Run unit tests |
+| `unit-tests-cov` | Run unit tests with coverage |
+| `integration-tests` | Run integration tests |
+| `integration-tests-cov` | Run integration tests with coverage |
+| `build-docs` | Build documentation website |
+| `run-docs` | Run documentation locally |
+| `build` | Build package |
+| `clean` | Remove build artifacts |
+
 ## Dependencies
 
 To install this package and its development dependencies, run:
@@ -59,8 +77,6 @@ uv run poe type-check
 
 ### Unit tests
 
-We employ pytest as our testing framework, equipped with various plugins. Check pyproject.toml for configuration details and installed plugins.
-
 We use [pytest](https://docs.pytest.org/) as a testing framework with many plugins. Check `pyproject.toml` for configuration details and installed plugins.
 
 To run unit tests:
@@ -77,20 +93,26 @@ uv run poe unit-tests-cov
 
 ## Integration tests
 
-We have integration tests which build and run Actors using the Python SDK on the Apify Platform. To run these tests,
-you need to set the `APIFY_TEST_USER_API_TOKEN` environment variable to the API token of the Apify user you want to
-use for the tests, and then start them with `uv run poe integration-tests`.
+We have integration tests which build and run Actors using the Python SDK on the Apify platform.
+
+Prerequisites:
 
-If you want to run the integration tests on a different environment than the main Apify Platform, you need to set
-the `APIFY_INTEGRATION_TESTS_API_URL` environment variable to the right URL to the Apify API you want to use.
+- Set `APIFY_TEST_USER_API_TOKEN` to your Apify API token
+- Optionally set `APIFY_INTEGRATION_TESTS_API_URL` to use a different Apify API environment
+
+To run integration tests:
+
+```sh
+uv run poe integration-tests
+```
 
 ## Documentation
 
 We adhere to the [Google docstring format](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html) for documenting our codebase. Every user-facing class or method is documented. Documentation standards are enforced using [Ruff](https://docs.astral.sh/ruff/).
 
 Our API documentation is generated from these docstrings using [pydoc-markdown](https://pypi.org/project/pydoc-markdown/) with additional post-processing. Markdown files in the `docs/` folder complement the autogenerated content. Final documentation is rendered using [Docusaurus](https://docusaurus.io/) and published to GitHub Pages.
 
-To run the documentation locally:
+To run the documentation locally (requires Node.js):
 
 ```sh
 uv run poe run-docs
@@ -118,14 +140,14 @@ name = "apify"
 version = "x.z.y"
 ```
 
-4. Generate the distribution archives for the package:
+4. Build the package:
 
-```shell
-uv build
+```sh
+uv run poe build
 ```
 
-5. Set up the PyPI API token for authentication and upload the package to PyPI:
+5. Upload to PyPI:
 
-```shell
+```sh
 uv publish --token YOUR_API_TOKEN
 ```

docs/02_concepts/12_pay_per_event.mdx

@@ -43,7 +43,7 @@ When you plan to start using the pay-per-event pricing model for an Actor that i
 
 It is encouraged to test your monetization code on your machine before releasing it to the public. To tell your Actor that it should work in pay-per-event mode, pass it the `ACTOR_TEST_PAY_PER_EVENT` environment variable:
 
-```shell
+```sh
 ACTOR_TEST_PAY_PER_EVENT=true python -m youractor
 ```