From f9451dfaf89bbab83e6ec19fc7e3954c83ec4f13 Mon Sep 17 00:00:00 2001
From: prasadpatil49 <51715670+prasadpatil49@users.noreply.github.com>
Date: Thu, 10 Nov 2022 16:05:02 +0530
Subject: [PATCH] docfix for ssh_args FAQ (#79308)

---
 docs/docsite/rst/reference_appendices/faq.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docsite/rst/reference_appendices/faq.rst b/docs/docsite/rst/reference_appendices/faq.rst
index 79772d963ce..cb490edd696 100644
--- a/docs/docsite/rst/reference_appendices/faq.rst
+++ b/docs/docsite/rst/reference_appendices/faq.rst
@@ -138,7 +138,7 @@ or globally by setting ``ssh_args`` in ``ansible.cfg``.
 How do I get Ansible to notice a dead target in a timely manner?
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
-You can add ``-o ServerAliveInterval=NumberOfSeconds`` in ``ssh_args`` from ``ansible.cfg``. Without this option,
+You can add ``-o ServerAliveInterval=NumberOfSeconds`` with the ``ssh_args`` parameter in `SSH connection plugin <https://docs.ansible.com/ansible-core/devel/collections/ansible/builtin/ssh_connection.html#parameter-ssh_args>`_. Without this option,
 SSH and therefore Ansible will wait until the TCP connection times out. Another solution is to add ``ServerAliveInterval``
 into your global SSH configuration. A good value for ``ServerAliveInterval`` is up to you to decide; keep in mind that
 ``ServerAliveCountMax=3`` is the SSH default so any value you set will be tripled before terminating the SSH session.