Doc: Spell "command-line option" with a dash
GCC documentation now consistently uses "command-line option" with a dash and standardizes on "option" over "flag" or "switch."
This commit standardizes terminology across various GCC documentation files by consistently spelling “command-line option” with a hyphen. Additionally, it unifies the usage of terms, preferring “option” over “flag” or “switch” to refer to command-line arguments. These changes improve the readability and consistency of the documentation, making it easier for users to understand and navigate the compiler’s features and settings.
In Details
This documentation update primarily involves lexical and grammatical consistency across numerous Texinfo files within GCC, including cpp.texi, gcc.texi, and tm.texi.in. The change enforces a hyphenated "command-line option" and standardizes on "option" as the preferred term, de-emphasizing "flag" or "switch." While not impacting compiler internals, such standardization improves the usability of the documentation for both internal contributors and external users, reducing ambiguity in technical discourse.
For Context
This update focuses on improving the written documentation for GCC, the GNU Compiler Collection. When you use GCC, you often provide 'command-line options' to tell it how to compile your code (e.g., -O2 for optimization). Historically, the documentation might have used various terms like 'flag' or 'switch' interchangeably with 'option.' This commit standardizes two things: first, it ensures that 'command-line option' is always written with a hyphen, and second, it makes sure that 'option' is the consistent term used throughout the documentation, avoiding 'flag' or 'switch.' This kind of consistency makes the documentation easier to read and understand, so users can find information about compiler settings more quickly and without confusion.