docs: use pnpm and new commands to check the code base (#8667)

Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,6 @@
 # HEADS UP: BIG RESTRUCTURING UNDERWAY
 
-The Svelte repo is currently in the process of heavy restructuring for Svelte 4. After that, work on Svelte 5 will likely change a lot on the compiler aswell. For that reason, please don't open PRs that are large in scope, touch more than a couple of files etc. In other words, bug fixes are fine, but feature PRs will likely not be merged.
+The Svelte repo is currently in the process of heavy restructuring for Svelte 4. After that, work on Svelte 5 will likely change a lot in the compiler as well. For that reason, please don't open PRs that are large in scope, touch more than a couple of files, etc. In other words, bug fixes are fine, but feature PRs will likely not be merged.
 
 ### Before submitting the PR, please make sure you do the following
 - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
@@ -8,5 +8,5 @@ The Svelte repo is currently in the process of heavy restructuring for Svelte 4.
 - [ ] This message body should clearly illustrate what problems it solves.
 - [ ] Ideally, include a test that fails without this PR but passes with it.
 
-### Tests
--  [ ] Run the tests with `npm test` and lint the project with `npm run lint`
+### Tests and linting
+-  [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint`