Docs and strings

.github/workflows/release.yaml

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: "The version to tag, without the leading 'v'. If omitted, will initiate a dry-run, skips any upload steps."
+        description: "The version to tag, without the leading 'v'. If omitted, will initiate a dry run skipping uploading artifact."
         type: string
       sha:
         description: "Optionally, the full sha of the commit to be released"
@@ -403,7 +403,7 @@ jobs:
       - linux-cross
       - musllinux
       - musllinux-cross
-    # If you don't set an input it's a practice run
+    # If you don't set an input it's a dry run skipping uploading artifact
     if: ${{ inputs.tag }}
     environment:
       name: release

RELEASING.md

@@ -6,8 +6,8 @@ This is a guide how to create a new ruff release
 1. Update [BREAKING_CHANGES.md](BREAKING_CHANGES.md)
 1. Create a PR with the version and BREAKING_CHANGES.md updated
 1. Merge the PR
-1. Run the release workflow with the version number (without starting `v`) as input. Make sure main has your
-   merged PR as last commit
+1. Run the release workflow with the version number (without starting `v`) as input. Make sure
+   main has your merged PR as last commit
 1. The release workflow will do the following:
    1. Build all the assets. If this fails (even though we tested in step 4), we haven’t tagged or
       uploaded anything, you can restart after pushing a fix