From e81fdd515345f2644da2439be8725522775050a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ha=CC=8Akan=20Sidenvall?= <hakan.sidenvall@unity3d.com>
Date: Wed, 11 Dec 2024 15:13:22 +0100
Subject: [PATCH] Switched to anchor link

---
 .../InputSystem/Plugins/EnhancedTouch/Touch.cs                  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Packages/com.unity.inputsystem/InputSystem/Plugins/EnhancedTouch/Touch.cs b/Packages/com.unity.inputsystem/InputSystem/Plugins/EnhancedTouch/Touch.cs
index 2d7c3c86d2..c28ebe48c3 100644
--- a/Packages/com.unity.inputsystem/InputSystem/Plugins/EnhancedTouch/Touch.cs
+++ b/Packages/com.unity.inputsystem/InputSystem/Plugins/EnhancedTouch/Touch.cs
@@ -341,7 +341,7 @@ public TouchHistory history
         /// case <see cref="phase"/> will be <see cref="TouchPhase.Ended"/> instead of <see cref="TouchPhase.Moved"/>).
         ///
         /// Note that the touches reported by this API do <em>not</em> necessarily have to match the contents of
-        /// <see href="https://docs.unity3d.com/ScriptReference/Input-touches.html">UnityEngine.Input.touches</see>.
+        /// <a href="https://docs.unity3d.com/ScriptReference/Input-touches.html">UnityEngine.Input.touches</a>.
         /// The reason for this is that the <c>UnityEngine.Input</c> API and the Input System API flush their input
         /// queues at different points in time and may thus have a different view on available input. In particular,
         /// the Input System event queue is flushed <em>later</em> in the frame than inputs for <c>UnityEngine.Input</c>