A narrow text column can develop awkward gaps or overflow when a long word refuses to fit. Automatic hyphenation can help, but the browser needs more than a small width. It needs to know the language of the text and have appropriate support for breaking words in that language.
MDN’s hyphens reference explains the none, manual and auto values. In HTML, the lang attribute supplies the language context. Automatic results can vary between browsers and available language resources.
A small starting example
<article lang="en">
<p class="reading-text">A paragraph of English text...</p>
</article>
.reading-text {
hyphens: auto;
}
This is an illustrative pattern, not a complete typography system. Use the actual language of the content, including language changes within a multilingual page where needed. Setting English on a German paragraph simply to make a style rule work gives the browser the wrong information.
Test words and non-words separately
Hyphenation concerns word-breaking opportunities. A long URL, identifier or tracking string is a different case and may need an overflow strategy such as an appropriate overflow-wrap rule. Avoid using aggressive breaks everywhere just because one unusual string overflows.
Make a test paragraph containing ordinary prose, a long word, a link and an inline code fragment. View it at the smallest supported width and with enlarged text. Check the last line of a paragraph as well as the most crowded line.
For a content-editor review, ask whether the result remains easy to read rather than counting how many lines fit. Excessive consecutive hyphens can make a column tiring even when nothing technically overflows. A slightly wider measure or different type size may be the better design decision.
Keep intentional hyphens distinct from optional break opportunities. An editor should not insert ordinary hyphens into a word solely to fix one screen width, because those characters remain when the layout changes. Let the text keep its spelling while the layout handles its available space.

