From eca26e664bd3b35bb44a45b701d04bd5457888d3 Mon Sep 17 00:00:00 2001
From: Cameron Gutman <aicommander@gmail.com>
Date: Fri, 29 Dec 2023 21:18:47 -0600
Subject: [PATCH] Make wording about fatal errors a little less strong

Some "fatal" errors might be expected for some esoteric configurations.
---
 src_assets/common/assets/web/index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src_assets/common/assets/web/index.html b/src_assets/common/assets/web/index.html
index 3efd27f1..5cff0873 100644
--- a/src_assets/common/assets/web/index.html
+++ b/src_assets/common/assets/web/index.html
@@ -13,8 +13,8 @@
     <div class="alert alert-danger" v-if="fancyLogs.find(x => x.level === 'Fatal')">
       <div style="line-height: 32px;">
         <i class="fas fa-circle-exclamation" style="font-size: 32px;margin-right: 0.25em;"></i>
-        <b>Attention!</b> Sunshine detected these errors during startup. These errors <b>MUST</b> be fixed before using
-        Sunshine.<br>
+        <b>Attention!</b> Sunshine detected these errors during startup. We <b>STRONGLY RECOMMEND</b> fixing them
+        before streaming.<br>
       </div>
       <ul>
         <li v-for="v in fancyLogs.filter(x => x.level === 'Fatal')">{{v.value}}</li>