From ea305b8ce5d3c576f8818477657b99b4aa6e9a4b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tr=C3=A8sAbhi?= <43380238+tresabhi@users.noreply.github.com>
Date: Mon, 1 Jul 2024 19:14:54 -0500
Subject: [PATCH] fix: emoji

---
 docs/technical/wss.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/technical/wss.md b/docs/technical/wss.md
index f963f3388..f10d92dbc 100644
--- a/docs/technical/wss.md
+++ b/docs/technical/wss.md
@@ -71,7 +71,7 @@ Corelation analysis must be performed on a per-tank basis. If the goal is to eva
 The Wargaming API provides many pieces of statistics on a per-tank basis (as listed below). These values cumulate over time as the player plays more games; hence, all of these values must be normalized by dividing each metric by `all.battles`. I will go through and list which of the statistics need to be included as standard scores and why/why not. Omitted statistics must not be included and are obvious why they aren't used.
 
 - ✔️ `battle_life_time`: Normalization of this value results in the average time spent alive in seconds. Good players strive to stay alive for as long as possible and must be rewarded while people who "yolo" at the beginning of the game will be penalized.
-- $\xmapsto{asd}$ `all.battles`: Dividing this by itself will result in 1. Corelation analysis will always fail due to division by 0.
+- ❌ `all.battles`: Dividing this by itself will result in 1. Corelation analysis will always fail due to division by 0.
 - ✔️ `all.capture_points`: Capturing points almost always have a negative corelation coefficient; hence, its inclusion is vital to punish players who waste time capturing points.
 - ✔️ `all.damage_dealt`
 - ✔️ `all.damage_received`