diff --git a/doc.zih.tu-dresden.de/docs/contrib/content_rules.md b/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
index 1758dc25c928df014ba88d565fb64e4134c5877a..e1f1eef2eb65372ae72ef5a1c4377c56697e7a7e 100644
--- a/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
+++ b/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
@@ -66,7 +66,7 @@ or via [Email](mailto:hpcsupport@zih.tu-dresden.de).
 * Use active over passive voice
     * Write with confidence. This confidence should be reflected in the documentation so that
       the readers trust and follow it.
-    * Example: `We recommend something` instead of `Something is recommended.`
+    * Example: "We recommend something" instead of "Something is recommended."
 * Capitalize headings, e.g. *Exclusive Reservation of Hardware*
 * Give keywords in link texts, e.g. [Code Blocks](#code-blocks-and-syntax-highlighting) is more
   descriptive than [this subsection](#code-blocks-and-syntax-highlighting)