[commanding] some less scary text fixes

1 files changed, 17 insertions, 4 deletions

diff --git a/commanding/commanding.tex b/commanding/commanding.tex
index 3d93a06..6a24d5f 100644
--- a/commanding/commanding.tex
+++ b/commanding/commanding.tex
@@ -64,6 +64,15 @@ Generally speaking, your job as a commander consists of the following parts, whi
 
 Depending on the team/community that you run wurms with, there can be some other organizational tasks such as keeping track of runs in a spreadsheet, or giving/receiving feedback with other commanders.
 
+It might sound or look like commanding is hard, complicated or even scary, but it is not.
+While it can be a bit rough sometimes, it is generally fun, easy and can be very rewarding!
+To prevent new commanders from getting overwhelmed, at TTT we have the \enquote{trainee system}, where new commanders get help from other commanders or mentors.
+They don't have to run alone, they can choose to only run with someone watching over them, and they can decide for themselves when they want to get started.
+
+Additionally, all the commanders do it because they enjoy doing the event.
+No one is forced to do it, no one gets paid for doing it and no one should feel bad when doing it.
+As such, having fun while commanding the event is important, and even if a run goes bad or fails, it is more than fine.
+
 
 \section{General (Squad) Mechanics}
 
@@ -580,16 +589,16 @@ The truth however is that there are more things that a commander has to take car
 
 For starters, you usually have to deal with eggs and husks, either by having an egg blocker and/or husk handlers.
 If you have them, you have to take care that they don't get attacked or even downed by the wurm's attacks or veteran wurms standing around.
-It is your job to keep them alive!
+A commander should watch out for their special roles and keep them alive!
 Depending on the blocker, you might also need to handle some unexpected eggs and the AoE spits, which will not always be blocked.
 This can make a run a bit more chaotic, especially on Amber, where husks can disrupt the zerg while stacking up.
 
 Depending on the amount of people that you have with you, or the amount of new people, you might have issues getting burn phases on e.g. Cobalt due to bad keg running.
-It is your job to coordinate the squad and make sure you don't descend into chaos with all the explosion timers!
+A commander should coordinate the squad and make sure that they don't descend into chaos with all the explosion timers!
 
 Additionally, not all people might listen due to various reasons.
 They might not know better, they might not understand English that well, they might not be in your squad, they might just try and get an achievement, or in the worst case, they might be intentionally trolling.
-It is your job to be aware of what is going on in the arena (e.g. people killing the Abomination or filling blue), and to be prepared to handle it!
+A commander should be aware of what is going on in the arena (e.g. people killing the Abomination or filling blue), and be prepared to handle it!
 
 As such, the qualities of a good commander are not in how well they can recite the dry run by heart.
 A good commander is someone who can make the right decisions even in tough and unexpected situations, who can stay calm under pressure and who can lead their squad to victory even when some things don't go according to plan.
@@ -601,14 +610,18 @@ This is why at TTT we have feedback from other commanders and the trainee passpo
 \textbf{Always keep in mind that smooth seas don't make good sailors.}
 
 
-\subsection{Failure}
+\section{Dealing With Failures}
 
 Sometimes, despite our efforts, the event fails.
 Be it due to a bug in the game, or due to human error, low participation or bad damage, it doesn't matter, it happens.
 The important part is that we don't take it too serious.
+After all, we are doing this for fun, and it is important to remind ourselves of that fact.
 Some people can get really worked up over a failed in-game event, even one that spawns six times a day and can be spawned even more often by guilds, but we should try to not let it affect us.
+It is not like failing the event will have any big negative impact, in fact, us not being there would probably lead to even more failures.
 
 If the event failed because of a wrong decision made by a commander, they can learn from that for the future, but should otherwise not beat themselvse up over it or keep blaming a single person for it.
 While succeeding the event is our goal, it is also important to not forget that we are here because we \emph{enjoy} doing it, and because it is fun to do.
 
+Always remember the real humans and emotions that are behind each screen name, and put those into perspective to the outcome of a virtual in-game event.
+
 \end{document}