docs: update development docs (#62)

DEVELOPMENT.md

@@ -12,22 +12,11 @@ npm run package
 
 ## Releases
 
-1. Create a semver tag pointing to the commit you want to release. E.g. to create `v1.4.4` from tip-of-tree:
-```
-git checkout main
-git pull upstream main
-git tag v1.4.4
-git push upstream v1.4.4
-```
-1. Create Playwrgight PR with updated reference to the GitHub action (change `playwright-github-action@v1` to the newly created version `playwright-github-action@v1.4.4`) and make sure the tests are passing. Do not commit the change.
+1. Create a new release draft with text `Support for Playwright v1.XX` (put a proper PW version)
 1. Draft a new release on GitHub using the semver tag.
-1. Update the sliding tag (`v1`) to point to the new release commit. Note that existing users relying on the `v1` will get auto-updated.
-
-### Updating sliding tag
-
-Follow these steps to move the `v1` to a new version `v1.4.4`.
-
-```
-git tag -f v1 v1.4.4
-git push -f upstream v1
-```
+1. Update the sliding tag (`v1`) to point to the new release. Note that existing users relying on the `v1` will get auto-updated.
+    ```bash
+    # example: move the v1 to point to v1.4.4
+    git tag -f v1 v1.4.4
+    git push -f upstream v1
+    ```