I think hyphenating only part of shortest round-trip behavior conveys the wrong idea

Author: Tyler Whitney

docs/standard-library/charconv-functions.md

@@ -13,7 +13,7 @@ The \<charconv> header includes the following non-member functions:
 |[to_chars](#to_chars) | Convert an integer or floating-point value to a sequence of **`char`**. |
 |[from_chars](#from_chars) | Convert a sequence of **`char`** to  an integer or floating-point value. |
 
-These conversion functions are tuned for performance, and also support shortest round-trip behavior. Shortest round-trip behavior means when a number is converted to chars, only enough precision is written out to enable recovering the original number when converting those chars back to a floating-point.
+These conversion functions are tuned for performance, and also support shortest-round-trip behavior. Shortest-round-trip behavior means when a number is converted to chars, only enough precision is written out to enable recovering the original number when converting those chars back to a floating-point.
 
 - When converting chars to a number, the numeric value doesn't need to be null-terminated. Likewise, when converting a number to chars, the result isn't null-terminated.
 - The conversion functions don't allocate memory. You own the buffer in all cases.
@@ -89,13 +89,13 @@ A [to_chars_result](to-chars-result-structure.md) containing the result of the c
 Functions taking a [chars_format](chars-format-class.md) parameter determine the conversion specifier as if they were using `printf()` as follows:
 The conversion specifier is `'f'` if `fmt` is `chars_format::fixed`, `'e'` if `fmt` is `chars_format::scientific`, `'a'` (without the leading `0x` in the result) if `fmt` is `chars_format::hex`, and `'g'` if `fmt` is `chars_format::general`. Specifying the shortest fixed notation may still result in lengthy output because it may be the shortest possible representation when the value is very large or very small.
 
-The following table describes the conversion behavior given different combinations of `fmt` and `precision` parameters. The term "shortest round trip" refers to writing the fewest number of digits necessary such that parsing that representation using the corresponding `from_chars` function will recover the value exactly.
+The following table describes the conversion behavior given different combinations of `fmt` and `precision` parameters. The term "shortest-round-trip behavior" refers to writing the fewest number of digits necessary such that parsing that representation using the corresponding `from_chars` function will recover the value exactly.
 
 | `fmt` and `precision` combination | Output |
 |--|--|
 |  Neither | Whichever of fixed or scientific notation is shorter, preferring fixed as a tiebreaker.</br>This behavior can't be simulated by any overload that takes the `fmt` parameter. |
-| `fmt` | The shortest round-trip behavior for the specified format, such as the shortest scientific format. |
-| `fmt` and `precision` | Uses the given precision, following `printf()` style, without  shortest round-trip behavior. |
+| `fmt` | The shortest-round-trip behavior for the specified format, such as the shortest scientific format. |
+| `fmt` and `precision` | Uses the given precision, following `printf()` style, without  shortest-round-trip behavior. |
 
 ### Return value