From 5ae593bc00b4d03ef962ae690fa17997de4b4e12 Mon Sep 17 00:00:00 2001
From: Nils K <24257556+septatrix@users.noreply.github.com>
Date: Mon, 12 Dec 2022 12:33:32 +0200
Subject: [PATCH] website/docs: Fix typo in ldap source documentation (#4197)

Signed-off-by: Nils K <24257556+septatrix@users.noreply.github.com>

Signed-off-by: Nils K <24257556+septatrix@users.noreply.github.com>
---
 website/integrations/sources/ldap/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/integrations/sources/ldap/index.md b/website/integrations/sources/ldap/index.md
index 629ff18e3..846064d9a 100644
--- a/website/integrations/sources/ldap/index.md
+++ b/website/integrations/sources/ldap/index.md
@@ -40,4 +40,4 @@ LDAP property mappings can be used to convert the raw LDAP response into an auth
 
 By default, authentik ships with some pre-configured mappings for the most common LDAP setups.
 
-You can assign the value of a mapping to any user attribute, or save it as a custom attribute by prefixing the object field with `attribute.` Keep in mind though, data types from the LDAP server will be carried over. This means that with some implementations, where fields ar stored as array in LDAP, they will be saved as array in authentik. To prevent this, use the built-in `list_flatten` function.
+You can assign the value of a mapping to any user attribute, or save it as a custom attribute by prefixing the object field with `attribute.` Keep in mind though, data types from the LDAP server will be carried over. This means that with some implementations, where fields are stored as array in LDAP, they will be saved as array in authentik. To prevent this, use the built-in `list_flatten` function.