improve prompt

Author: renejeglinsky

.github/workflows/ai-review.yml

@@ -32,3 +32,5 @@ jobs:
             - Ensure that the tone is appropriate for technical documentation, maintaining a professional and informative style.
             - Verify that the structure of the document is logical and that headings and subheadings are used effectively.
             - Check for consistency in terminology and style throughout the document.
+            - Use active voice instead of passive voice
+            - Use present tense and **avoid future tense**!

.github/workflows/assets/editor.md

@@ -41,11 +41,11 @@ There are a couple of aspects that are easy to consider when writing w/o digging
 
   This sound easier than it is, but if you can put it in simpler words, it gets automatically clearer and more helpful.
 
+- Use present tense and **avoid future tense**!
 - Avoid emoticons and emojis.
 - Do NOT remove TODO markers at all.
 - Do NOT remove tip, warning or danger notes indicated by `... tip` or similar constructs.
 
-- Use present and avoid future tense!
 
 The documentation should follow the here described style guidance so that it keeps a consistent external and internal appearance: