From 1e0473e44f5e21558d75b0121bd935bb50825c26 Mon Sep 17 00:00:00 2001
From: Sintendo <3380580+Sintendo@users.noreply.github.com>
Date: Sat, 17 Jan 2026 19:02:37 +0100
Subject: Fix various typos and spelling mistakes

---
 Source/Core/VideoCommon/UberShaderVertex.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'Source/Core/VideoCommon/UberShaderVertex.cpp')

diff --git a/Source/Core/VideoCommon/UberShaderVertex.cpp b/Source/Core/VideoCommon/UberShaderVertex.cpp
index a6c0502dfe..0eee69fb56 100644
--- a/Source/Core/VideoCommon/UberShaderVertex.cpp
+++ b/Source/Core/VideoCommon/UberShaderVertex.cpp
@@ -438,7 +438,7 @@ float3 load_input_float3_rawtex(uint vtx_offset, uint attr_offset) {{
   // There are two different ways to do this, when the depth range is oversized, we process
   // the depth range in the vertex shader, if not we let the host driver handle it.
   //
-  // Adjust z for the depth range. We're using an equation which incorperates a depth inversion,
+  // Adjust z for the depth range. We're using an equation which incorporates a depth inversion,
   // so we can map the console -1..0 range to the 0..1 range used in the depth buffer.
   // We have to handle the depth range in the vertex shader instead of after the perspective
   // divide, because some games will use a depth range larger than what is allowed by the
@@ -450,7 +450,7 @@ float3 load_input_float3_rawtex(uint vtx_offset, uint attr_offset) {{
   if (!host_config.backend_clip_control)
   {
     // If the graphics API doesn't support a depth range of 0..1, then we need to map z to
-    // the -1..1 range. Unfortunately we have to use a substraction, which is a lossy floating-point
+    // the -1..1 range. Unfortunately we have to use a subtraction, which is a lossy floating-point
     // operation that can introduce a round-trip error.
     out.Write("o.pos.z = o.pos.z * 2.0 - o.pos.w;\n");
   }
-- 
cgit v1.2.3