The introduction of vivid.rst says that the framebuffer device is
available for testing capture and output overlays, and the feature
list mentions capture and output overlay support.

Commit ccaa9d50ca73 ("media: vivid: drop overlay support") removed
capture overlay support, and vivid now only implements output overlays.

Update both places to mention output overlays only.

Assisted-by: LLM
Signed-off-by: Hyeonjun Hong <hyeonjunhong330@gmail.com>
---
 Documentation/admin-guide/media/vivid.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/admin-guide/media/vivid.rst b/Documentation/admin-guide/media/vivid.rst
index 034ca7c77fb9..6741f25220fc 100644
--- a/Documentation/admin-guide/media/vivid.rst
+++ b/Documentation/admin-guide/media/vivid.rst
@@ -6,7 +6,7 @@ The Virtual Video Test Driver (vivid)
 This driver emulates video4linux hardware of various types: video capture, video
 output, vbi capture and output, metadata capture and output, radio receivers and
 transmitters, touch capture and a software defined radio receiver. In addition a
-simple framebuffer device is available for testing capture and output overlays.
+simple framebuffer device is available for testing output overlays.
 
 Up to 64 vivid instances can be created, each with up to 16 inputs and 16 outputs.
 
@@ -35,7 +35,7 @@ This document describes the features implemented by this driver:
 - Raw and Sliced VBI capture and output support
 - Radio receiver and transmitter support, including RDS support
 - Software defined radio (SDR) support
-- Capture and output overlay support
+- Output overlay support
 - Metadata capture and output support
 - Touch capture support
 
-- 
2.34.1