1 files changed, 0 insertions, 35 deletions
diff --git a/docs/content/usage/multi-factor-authentication.en-us.md b/docs/content/usage/multi-factor-authentication.en-us.md
deleted file mode 100644
index 30323f6de5..0000000000
--- a/docs/content/usage/multi-factor-authentication.en-us.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-date: "2023-08-22T14:21:00+08:00"
-title: "Multi-factor Authentication (MFA)"
-slug: "multi-factor-authentication"
-weight: 15
-toc: false
-draft: false
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Multi-factor Authentication (MFA)"
-    weight: 15
-    identifier: "multi-factor-authentication"
----
-
-# Multi-factor Authentication (MFA)
-
-Multi-factor Authentication (also referred to as MFA or 2FA) enhances security by requiring a time-sensitive set of credentials in addition to a password.
-If a password were later to be compromised, logging into Gitea will not be possible without the additional credentials and the account would remain secure.
-Gitea supports both TOTP (Time-based One-Time Password) tokens and FIDO-based hardware keys using the Webauthn API.
-
-MFA can be configured within the "Security" tab of the user settings page.
-
-## MFA Considerations
-
-Enabling MFA on a user does affect how the Git HTTP protocol can be used with the Git CLI.
-This interface does not support MFA, and trying to use a password normally will no longer be possible whilst MFA is enabled.
-If SSH is not an option for Git operations, an access token can be generated within the "Applications" tab of the user settings page.
-This access token can be used as if it were a password in order to allow the Git CLI to function over HTTP.
-
-> **Warning** - By its very nature, an access token sidesteps the security benefits of MFA.
-> It must be kept secure and should only be used as a last resort.
-
-The Gitea API supports providing the relevant TOTP password in the `X-Gitea-OTP` header, as described in [API Usage](development/api-usage.md).
-This should be used instead of an access token where possible.