Apply suggestions from code review

Author: JLekawa

.changeset/neat-numbers-knock.md

@@ -3,4 +3,4 @@
 "@redocly/openapi-core": minor
 ---
 
-Support `schemeName` in `x-security` at the workflow level (Arazzo). Added new lint rules: `arazzo/no-x-security-both-scheme-and-scheme-name` and `arazzo/x-security-scheme-name-link`. Updated core configs to include new rules.
+Added support for `schemeName` in `x-security` at the workflow level (Arazzo). Added new lint rules: `arazzo/no-x-security-both-scheme-and-scheme-name` and `arazzo/x-security-scheme-name-link`. Updated core configs to include new rules.

docs/@v2/rules/arazzo/no-x-security-both-scheme-and-scheme-name.md

@@ -8,7 +8,8 @@ Forbids using both `scheme` and `schemeName` in the same `x-security` item.
 
 ## Rationale
 
-A single `x-security` item must reference a security scheme in exactly one way: either by embedding the `scheme` object or by referencing it with `schemeName`. Having both is ambiguous and is rejected by the runtime.
+A single `x-security` item must reference a security scheme in exactly one way: either by embedding the `scheme` object or by referencing it with `schemeName`.
+Having both is ambiguous and is rejected by the runtime.
 
 ## Configuration
 

docs/@v2/rules/arazzo/x-security-scheme-name-link.md

@@ -1,14 +1,16 @@
 # x-security-scheme-name-link
 
-When multiple `sourceDescriptions` exist, `workflow.x-security.schemeName` must be a link to a specific source description (for example, `$sourceDescriptions.{name}.scheme`). If there is only one source description, a plain string is allowed.
+When multiple `sourceDescriptions` exist, `workflow.x-security.schemeName` must be a link to a specific source description (for example, `$sourceDescriptions.{name}.scheme`).
+If there is only one source description, a plain string is allowed.
 
 | Arazzo | Compatibility |
 | ------ | ------------- |
 | 1.x    | ✅            |
 
 ## Design principles
 
-With multiple source descriptions, using a plain `schemeName` is ambiguous. Requiring a link of the form `$sourceDescriptions.{name}.scheme` disambiguates which source description provides the security scheme.
+With multiple source descriptions, using a plain `schemeName` is ambiguous.
+Requiring a link of the form `$sourceDescriptions.{name}.scheme` disambiguates which source description provides the security scheme.
 
 ## Configuration