From 5502d29b6604bb162f84e1d7146644b6724343b1 Mon Sep 17 00:00:00 2001
From: KiwiTaco <122469357+kiwitaco@users.noreply.github.com>
Date: Wed, 10 Jun 2026 13:23:40 -0400
Subject: [PATCH] Update writing-policy.md

Removing Warning Achievement recommendation.
---
 docs/guidelines/content/writing-policy.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/docs/guidelines/content/writing-policy.md b/docs/guidelines/content/writing-policy.md
index cfc0f128..a734e6dd 100644
--- a/docs/guidelines/content/writing-policy.md
+++ b/docs/guidelines/content/writing-policy.md
@@ -178,8 +178,6 @@ As an international community, we don’t expect every developer to write with p
 
 Consistency is also preferred in the use of common words to describe an achievement. For finishing a level or boss for example, the most common words used are “beat”, “finish”, “clear”, “defeat” as well as a few others. Please only use one of them when working with multiple achievements that have the same theme - if the achievement description for finishing level 1 says “Defeat the boss of level 1”, the achievement description for level 2 shouldn’t say “Beat the boss of level 2” unless there is a good reason to use the different word. Stick to using the same words to describe the same things within a group of similar achievements.
 
-If a challenge condition, such as “on Normal difficulty or higher” or “no cheats”, applies to almost every achievement in the set, it is recommended to note this condition through a zero-point achievement (usually awarded at the start of the game), a forum post, or comments rather than repeating “on Normal difficulty or higher” in the description of every achievement.
-
 ---
 
 ### The Description Itself