Remove the repeated word "the" in docs.

Signed-off-by: Charles Han <hanchunchao@inspur.com>
---
 Documentation/gpu/amdgpu/display/dc-debug.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/gpu/amdgpu/display/dc-debug.rst b/Documentation/gpu/amdgpu/display/dc-debug.rst
index 013f63b271f3..605dca21f4ae 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.
 
-- 
2.43.0

On Thu, Feb 13, 2025 at 2:08 AM Charles Han <hanchunchao@inspur.com> wrote:
>
> Remove the repeated word "the" in docs.
>
> Signed-off-by: Charles Han <hanchunchao@inspur.com>

Applied.  Thanks!

Alex

> ---
>  Documentation/gpu/amdgpu/display/dc-debug.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/amdgpu/display/dc-debug.rst b/Documentation/gpu/amdgpu/display/dc-debug.rst
> index 013f63b271f3..605dca21f4ae 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.
>
> --
> 2.43.0
>