From 2ea12464be6fdf0566eb9af0368fcb751f70b83a Mon Sep 17 00:00:00 2001
From: nanahi <130121847+na-na-hi@users.noreply.github.com>
Date: Thu, 7 Mar 2024 01:06:00 -0500
Subject: [PATCH] DOCS/tech-overview.txt: add vo_gpu_next reference

vo_gpu_next also can pick a windowing system at runtime.
---
 DOCS/tech-overview.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/DOCS/tech-overview.txt b/DOCS/tech-overview.txt
index a24e0161da..33067a65a5 100644
--- a/DOCS/tech-overview.txt
+++ b/DOCS/tech-overview.txt
@@ -215,8 +215,8 @@ video/out/:
     Video output. They also create GUI windows and handle user input. In most
     cases, the windowing code is shared among VOs, like x11_common.c for X11 and
     w32_common.c for Windows. The VOs stand between frontend and windowing code.
-    vo_gpu can pick a windowing system at runtime, e.g. the same binary can
-    provide both X11 and Cocoa support on macOS.
+    vo_gpu and vo_gpu_next can pick a windowing system at runtime, e.g. the same
+    binary can provide both X11 and Cocoa support on macOS.
 
     VOs can be reconfigured at runtime. A vo_reconfig() call can change the video
     resolution and format, without destroying the window.