Merge pull request #3506 from jihoon-seo/250516_Update_descriptions_for_semantic_line_breaks

Author: Okabe-Junya

content/en/contribute/_index.md

@@ -51,7 +51,7 @@ Before beginning your Glossary contributor journey, be sure to complete the foll
 
 ## Best practices {#best-practices}
 
-To facilitate the reviewing process, please use [semantic line breaks](https://sembr.org/) (e.g., one line per sentence).
+To facilitate the reviewing process, please use [semantic line breaks](https://sembr.org).
 We recommend checking out this [markdown cheat sheet](https://www.markdownguide.org/cheat-sheet/) 
 to correctly format Markdown text in GitHub (e.g., hyperlink, bold, italic).
 And when naming .md files, please use lowercase letters and hyphens instead of spaces to separate words and avoid parenthesis.

content/en/style-guide/_index.md

@@ -128,7 +128,7 @@ The definitions for **technology** and **concept** categories contain a quick su
 
 Note that **properties** don't require separate sections. A definition will suffice. 
 
-Please use **semantic line breaks** (one sentence per line) to ease review. 
+Please use [**semantic line breaks**](https://sembr.org) to ease review. 
 
 #### Quality is paramount