Minor misc docs rewordings

Signed-off-by: cobalt <[email protected]>

Author: cobaltt7

.github/ISSUE_TEMPLATE/style_issue.md

@@ -29,6 +29,7 @@ def f():
 ```python
 def f(
     ):
+    "Make sure this code is blackened"""
     pass
 ```
 

AUTHORS.md

@@ -142,6 +142,7 @@ Multiple contributions by:
 - [Pablo Galindo](mailto:[email protected])
 - [Paul Ganssle](mailto:[email protected])
 - [Paul Meinhardt](mailto:[email protected])
+- [Paul S. Reid](mailto:[email protected])
 - [Peter Bengtsson](mailto:[email protected])
 - [Peter Grayson](mailto:[email protected])
 - [Peter Stensmyr](mailto:[email protected])

docs/contributing/the_basics.md

@@ -88,7 +88,7 @@ files in the `tests/data/cases` directory. These files consist of up to three pa
   If this is omitted, the test asserts that _Black_ will leave the input code unchanged.
 
 _Black_ has two pytest command-line options affecting test files in `tests/data/` that
-are split into an input part, and an output part, separated by a line with`# output`.
+are split into an input part, and an output part, separated by a line with `# output`.
 These can be passed to `pytest` through `tox`, or directly into pytest if not using
 `tox`.
 
@@ -128,11 +128,17 @@ does not need to go back and workout what to add to the `CHANGES.md` for each re
 
 ### Style Changes
 
+Please familiarize yourself with our [stability policy](labels/stability-policy).
+Therefore, most style changes must be added to the `--preview` style. Exceptions are
+fixing crashes or changes that would not affect an already-formatted file.
+
 If a change would affect the advertised code style, please modify the documentation (The
 _Black_ code style) to reflect that change. Patches that fix unintended bugs in
-formatting don't need to be mentioned separately though. If the change is implemented
-with the `--preview` flag, please include the change in the future style document
-instead and write the changelog entry under the dedicated "Preview style" heading.
+formatting don't need to be mentioned separately.
+
+If the change is implemented with the `--preview` flag, please include the change in the
+Future Style document instead and write the changelog entry under the dedicated "Preview
+style" heading.
 
 ### Docs Testing
 

docs/guides/introducing_black_to_your_project.md

@@ -45,7 +45,8 @@ $ git config blame.ignoreRevsFile .git-blame-ignore-revs
 
 **The one caveat is that some online Git-repositories do not yet support ignoring
 revisions using their native blame UI.** So blame information will be cluttered with a
-reformatting commit on those platforms.
-[GitHub supports `.git-blame-ignore-revs`](https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)
-by default in blame views however.
-[GitLab supports this since version 17.10](https://about.gitlab.com/releases/2025/03/20/gitlab-17-10-released/#ignore-specific-revisions-in-git-blame)
+reformatting commit on those platforms. However,
+[GitHub](https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)
+and
+[GitLab (since version 17.10)](https://about.gitlab.com/releases/2025/03/20/gitlab-17-10-released/#ignore-specific-revisions-in-git-blame)
+both support `.git-blame-ignore-revs` in blame views by default.