From d766295ad0f4e2716207941dfc7023a379bcfed9 Mon Sep 17 00:00:00 2001
From: rl885 <51694715+rl885@users.noreply.github.com>
Date: Wed, 31 Jul 2024 14:59:17 +0200
Subject: [PATCH] Update explanation.md

typo
---
 _vendors-content/samsung/explanation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_vendors-content/samsung/explanation.md b/_vendors-content/samsung/explanation.md
index 3e5cfbf4..c8b2053b 100644
--- a/_vendors-content/samsung/explanation.md
+++ b/_vendors-content/samsung/explanation.md
@@ -10,7 +10,7 @@ See details <a href="https://issuetracker.google.com/issues/179644471">here</a>
 
 UPDATE 07/2024: <a href="https://android-developers.googleblog.com/2023/05/improving-consistency-of-background-work-on-android.html">Samsung officially promised to drop the non-standard optimizations</a>:<br>
 "To strengthen the Android platform, our collaboration with Google has resulted in a unified policy that we expect will create a more consistent and reliable user experience for Galaxy users. Since One UI 6.0, foreground services of apps targeting Android 14 will be guaranteed to work as intended so long as they are developed according to Android's new foreground service API policy.”<br>
-If anyone has information about this or experience with Android 14 on Samsung phones, please, let us know any feedback on this.
+If anyone has information about this or experience with Android 14 on Samsung phones, please, let us know any feedback on this.<br>
 <br>
 
 UPDATE 04/2021: Is Samsung now killing even foreground services? Could this be real, or is it a chimera?<br>