From 4d2c9324be3979ecbc3d97d0d029b19e91c67c87 Mon Sep 17 00:00:00 2001
From: Chris Carini <6374067+ChrisCarini@users.noreply.github.com>
Date: Sun, 25 Apr 2021 12:39:28 -0700
Subject: [PATCH] Fixing spelling: `clint` -> `client` (#14323)

---
 docs/src/pages/docs/frequently-asked-questions-page.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/pages/docs/frequently-asked-questions-page.mdx b/docs/src/pages/docs/frequently-asked-questions-page.mdx
index e9c35246f6..5b4ab72fb3 100644
--- a/docs/src/pages/docs/frequently-asked-questions-page.mdx
+++ b/docs/src/pages/docs/frequently-asked-questions-page.mdx
@@ -66,7 +66,7 @@ If you are seeing timeouts (504 Gateway Time-out) when loading dashboard or expl
 probably behind gateway or proxy server (such as Nginx). If it did not receive a timely response
 from Superset server (which is processing long queries), these web servers will send 504 status code
 to clients directly. Superset has a client-side timeout limit to address this issue. If query didn’t
-come back within clint-side timeout (60 seconds by default), Superset will display warning message
+come back within client-side timeout (60 seconds by default), Superset will display warning message
 to avoid gateway timeout message. If you have a longer gateway timeout limit, you can change the
 timeout settings in **superset_config.py**: