aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/gpu
diff options
context:
space:
mode:
authorCharles Han <hanchunchao@inspur.com>2025-02-13 15:08:37 +0800
committerAlex Deucher <alexander.deucher@amd.com>2025-04-07 15:18:35 -0400
commitaa52eb6d1672cd75507d235a9f6e1b93fb5d3bb4 (patch)
treea228895dfd9d4150ac5c35a396c7f9dbf907ac60 /Documentation/gpu
parent74f0ff369f8a4f44082a71049a15d7da2e73ff7c (diff)
downloadnet-aa52eb6d1672cd75507d235a9f6e1b93fb5d3bb4.tar.gz
Documentation: Remove repeated word in docs
Remove the repeated word "the" in docs. Signed-off-by: Charles Han <hanchunchao@inspur.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'Documentation/gpu')
-rw-r--r--Documentation/gpu/amdgpu/display/dc-debug.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/gpu/amdgpu/display/dc-debug.rst b/Documentation/gpu/amdgpu/display/dc-debug.rst
index 013f63b271f357..605dca21f4aedd 100644
--- a/Documentation/gpu/amdgpu/display/dc-debug.rst
+++ b/Documentation/gpu/amdgpu/display/dc-debug.rst
@@ -154,7 +154,7 @@ of the display parameters, but the userspace might also cause this issue. One
way to identify the source of the problem is to take a screenshot or make a
desktop video capture when the problem happens; after checking the
screenshot/video recording, if you don't see any of the artifacts, it means
-that the issue is likely on the the driver side. If you can still see the
+that the issue is likely on the driver side. If you can still see the
problem in the data collected, it is an issue that probably happened during
rendering, and the display code just got the framebuffer already corrupted.