# Bad Examples: formal-public

1. > In today's competitive esports landscape, it is important that local scenes embrace opportunities for international growth.

   Fails because it sounds like an article template.

2. > Improved Harvester operational resilience by implementing a stricter execution timeout policy for synchronization workloads.

   Fails because it hides the actual thing: jobs got stuck for 60 minutes, now they time out after 10.

3. > Enhanced game discovery by normalizing multilingual filter behaviour.

   Fails because it is release-note sludge. Say what the user can do now.

4. > While there are understandable concerns from community members, it is important to approach this topic with nuance and empathy.

   Fails because it adds a fake moderation layer before making the point.

5. > This journey reminded me that sometimes the best solutions come from curiosity and persistence.

   Fails because it is a motivational ending Harry would normally delete.