diff --git a/docs/help/faq.md b/docs/help/faq.md
index d0718218..e13ecb41 100644
--- a/docs/help/faq.md
+++ b/docs/help/faq.md
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
 Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
 
 You could manually find the config file (app.ini) by checking Gitea's startup logs
-or reading the Gitea Web's Site Administrator -> Confugiraton Summary.
+or reading the Gitea Web's Site Administrator -> Configuration Summary.
 
 If you are using some isolated enviroments like container (docker),
 the path you see usually is not what it is in the host's filesystem.
diff --git a/versioned_docs/version-1.22/help/faq.md b/versioned_docs/version-1.22/help/faq.md
index ca66a084..2c91faa5 100644
--- a/versioned_docs/version-1.22/help/faq.md
+++ b/versioned_docs/version-1.22/help/faq.md
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
 Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
 
 You could manually find the config file (app.ini) by checking Gitea's startup logs
-or reading the Gitea Web's Site Administrator -> Confugiraton Summary.
+or reading the Gitea Web's Site Administrator -> Configuration Summary.
 
 If you are using some isolated enviroments like container (docker),
 the path you see usually is not what it is in the host's filesystem.
diff --git a/versioned_docs/version-1.23/help/faq.md b/versioned_docs/version-1.23/help/faq.md
index 76017b45..187b124b 100644
--- a/versioned_docs/version-1.23/help/faq.md
+++ b/versioned_docs/version-1.23/help/faq.md
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
 Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
 
 You could manually find the config file (app.ini) by checking Gitea's startup logs
-or reading the Gitea Web's Site Administrator -> Confugiraton Summary.
+or reading the Gitea Web's Site Administrator -> Configuration Summary.
 
 If you are using some isolated enviroments like container (docker),
 the path you see usually is not what it is in the host's filesystem.
diff --git a/versioned_docs/version-1.24/help/faq.md b/versioned_docs/version-1.24/help/faq.md
index d0718218..e13ecb41 100644
--- a/versioned_docs/version-1.24/help/faq.md
+++ b/versioned_docs/version-1.24/help/faq.md
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
 Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
 
 You could manually find the config file (app.ini) by checking Gitea's startup logs
-or reading the Gitea Web's Site Administrator -> Confugiraton Summary.
+or reading the Gitea Web's Site Administrator -> Configuration Summary.
 
 If you are using some isolated enviroments like container (docker),
 the path you see usually is not what it is in the host's filesystem.
diff --git a/versioned_docs/version-1.25/help/faq.md b/versioned_docs/version-1.25/help/faq.md
index d0718218..e13ecb41 100644
--- a/versioned_docs/version-1.25/help/faq.md
+++ b/versioned_docs/version-1.25/help/faq.md
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
 Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
 
 You could manually find the config file (app.ini) by checking Gitea's startup logs
-or reading the Gitea Web's Site Administrator -> Confugiraton Summary.
+or reading the Gitea Web's Site Administrator -> Configuration Summary.
 
 If you are using some isolated enviroments like container (docker),
 the path you see usually is not what it is in the host's filesystem.
diff --git a/versioned_docs/version-1.26/help/faq.md b/versioned_docs/version-1.26/help/faq.md
index d0718218..e13ecb41 100644
--- a/versioned_docs/version-1.26/help/faq.md
+++ b/versioned_docs/version-1.26/help/faq.md
@@ -33,7 +33,7 @@ then the config file (app.ini) should exists in the "custom/conf" directory of y
 Some package vendors might use "/etc/gitea" to store the config file, while some others don't.
 
 You could manually find the config file (app.ini) by checking Gitea's startup logs
-or reading the Gitea Web's Site Administrator -> Confugiraton Summary.
+or reading the Gitea Web's Site Administrator -> Configuration Summary.
 
 If you are using some isolated enviroments like container (docker),
 the path you see usually is not what it is in the host's filesystem.