docs: fix stale ReleaseType output reference in no-release behavior

Author: MariusStorhaug

README.md

@@ -626,7 +626,7 @@ When a pull request does not contain changes to important files:
 
 1. A comment is automatically added to the PR listing the configured patterns and explaining why build/test stages are
    skipped
-2. The `ReleaseType` output is set to `None`
+2. `Settings.Module.ReleaseType` is set to `None` (and `Settings.Module.CreateRelease` is `false`)
 3. Build, test, and publish stages are skipped
 4. The PR can still be merged for non-release changes (documentation updates, CI improvements, etc.)