From 399094aedc425ac9c68e221b8607b9746a2bdb68 Mon Sep 17 00:00:00 2001
From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Date: Mon, 27 Oct 2025 22:46:39 +0200
Subject: [PATCH] Follow the style guide in the style guide (#16466)

<!--
Thank you for contributing to uv! To help us out with reviewing, please
consider the following:

- Does this pull request include a summary of the change? (See below.)
- Does this pull request include a descriptive title?
- Does this pull request include references to any relevant issues?
-->

## Summary

<!-- What's the purpose of the change? What does it do, and why? -->

> 4. Hyphenate compound words, e.g., use "platform-specific" not
"platform specific".

Applies to "command line arguments" -> "command-line arguments".
---
 STYLE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/STYLE.md b/STYLE.md
index e777b71fd..e0fe5d5d4 100644
--- a/STYLE.md
+++ b/STYLE.md
@@ -16,7 +16,7 @@ documentation_.
 1. If a message ends with a single relevant value, precede it with a colon, e.g.,
    `This is the value: value`. If the value is a literal, wrap it in backticks.
 1. Markdown files should be wrapped at 100 characters.
-1. Use a space, not an equals sign, for command line arguments with a value, e.g.
+1. Use a space, not an equals sign, for command-line arguments with a value, e.g.
    `--resolution lowest`, not `--resolution=lowest`.
 
 ## Styling uv