From b5a9b645f4f939c2bef74e2e0f64663199648e51 Mon Sep 17 00:00:00 2001
From: klmmr <35450576+klmmr@users.noreply.github.com>
Date: Sat, 22 Feb 2025 23:22:27 +0100
Subject: [PATCH] website/docs: fix typo (#13174)

The sentence is broken; fixing typo to clarify that a secure connection is established *before* an LDAP bind.

Signed-off-by: klmmr <35450576+klmmr@users.noreply.github.com>
---
 website/docs/add-secure-apps/providers/ldap/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/add-secure-apps/providers/ldap/index.md b/website/docs/add-secure-apps/providers/ldap/index.md
index a420a0fc6b..647455a8d9 100644
--- a/website/docs/add-secure-apps/providers/ldap/index.md
+++ b/website/docs/add-secure-apps/providers/ldap/index.md
@@ -64,7 +64,7 @@ Starting with 2023.3, periods and slashes in custom attributes will be sanitized
 
 You can also configure SSL for your LDAP Providers by selecting a certificate and a server name in the provider settings.
 
-Starting with authentik 2023.6, StartTLS is supported, and the provider will pick the correct certificate based on the configured _TLS Server name_ field. The certificate is not picked based on the Bind DN, as the StartTLS operation should happen be the bind request to ensure bind credentials are transmitted over TLS.
+Starting with authentik 2023.6, StartTLS is supported, and the provider will pick the correct certificate based on the configured _TLS Server name_ field. The certificate is not picked based on the Bind DN, as the StartTLS operation should happen before the bind request to ensure bind credentials are transmitted over TLS.
 
 This enables you to bind on port 636 using LDAPS.