Update contributing guide

Author: vdusek

CONTRIBUTING.md

@@ -11,6 +11,23 @@ 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 |
+| `e2e-templates-tests` | Run end-to-end template tests |
+| `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:
@@ -51,7 +68,7 @@ uv run poe format
 
 Type checking is handled by [ty](https://docs.astral.sh/ty/), verifying code against type annotations. Configuration settings can be found in `pyproject.toml`.
 
-To run type-check:
+To run type checking:
 
 ```sh
 uv run poe type-check
@@ -75,10 +92,10 @@ uv run poe unit-tests-cov
 
 ## End-to-end tests
 
-Pre-requisites for running end-to-end tests:
- - [apify-cli](https://docs.apify.com/cli/docs/installation) correctly installed
- - `apify-cli` available in `PATH` environment variable
- - Your [apify token](https://docs.apify.com/platform/integrations/api#api-token) is available in `APIFY_TEST_USER_API_TOKEN` environment variable
+Prerequisites:
+
+- [apify-cli](https://docs.apify.com/cli/docs/installation) installed and available in `PATH`
+- Set `APIFY_TEST_USER_API_TOKEN` to your [Apify API token](https://docs.apify.com/platform/integrations/api#api-token)
 
 To run end-to-end tests:
 
@@ -90,7 +107,7 @@ uv run poe e2e-templates-tests
 
 We follow the [Google docstring format](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html) for code documentation. All user-facing classes and functions must be 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 custom post-processing. Additional content is provided through markdown files in the `docs/` directory. The final documentation is rendered using [Docusaurus](https://docusaurus.io/) and published to GitHub pages.
+Our API documentation is generated from these docstrings using [pydoc-markdown](https://pypi.org/project/pydoc-markdown/) with custom post-processing. Additional content is provided through markdown files in the `docs/` directory. The final documentation is rendered using [Docusaurus](https://docusaurus.io/) and published to GitHub Pages.
 
 To run the documentation locally, ensure you have `Node.js` 20+ installed, then run:
 
@@ -120,14 +137,14 @@ name = "crawlee"
 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
 ```