feat: rewrite “Validate your changes” grouping by source type rather …

…than check type

src/routes/documentation/contributing/local-development.mdx

@@ -164,46 +164,55 @@ The following checks are all run on pull requests automatically.
 
 You can also perform them locally.
 
-## Formatting
+### Rust
 
-For the typescript part you can run:
+Ensure that all code follows the style guidelines:
 
 ```sh
-pnpm run format:check && pnpm run -w repo:root:format:check
+cargo fmt
 ```
 
-For the rust codebase run:
+Check that no linting errors/warnings are present:
 
 ```sh
-cargo fmt
+cargo clippy -- -D warnings
 ```
 
-### Linting
-
-For the typescript part you can run:
+Tests:
 
 ```sh
-pnpm run lint
+cargo test
 ```
 
-For the rust codebase run:
+### Typescript
+
+TypeScript checks are composed of the following:
+
+- `build`
+- `format`
+- `lint`
+- `typecheck`
+- `test`
+
+You can run them singularly using `pnpm run CHECK` or by using the `check-all` script:
 
 ```sh
-cargo clippy -- -D warnings
+pnpm run check-all
 ```
 
-### Tests
+### E2E Tests
 
-For the typescript part you can run:
+To execute end-to-end tests, we are using [playwright](https://playwright.dev).
+To install the required browsers, run:
 
 ```sh
-pnpm run test
+pnpm exec playwright install
 ```
 
-For the rust codebase run:
+Then, you can run the tests with:
 
 ```sh
-cargo test
+pnpm run test:e2e
 ```
 
 import NavigationButtons from '../../../components/NavigationButtons'

src/routes/documentation/contributing/pull-requests.mdx

@@ -34,7 +34,7 @@ you can check the [official documentation](https://docs.github.com/en/pull-reque
     - If you are adding a new feature, describe the intended use case that the feature fulfills.
 
   - Ensure your code is valid by running the test on you local machine.
-    Refer to ["Validate your changes" section](/documentation/contributing/local-development)
+    Refer to ["Validate your changes" section](/documentation/contributing/local-development#validate-your-changes)
 
 - Please **don't**: