From 5f00b23f78b562319093d10f07c80850219ba0ad Mon Sep 17 00:00:00 2001
From: perrze <54007667+perrze@users.noreply.github.com>
Date: Fri, 19 Jul 2024 13:20:07 +0200
Subject: [PATCH] website/docs: fix typo in flows docs (#10550)

fix: the instead of to

Signed-off-by: perrze <54007667+perrze@users.noreply.github.com>
---
 website/docs/flow/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/flow/index.md b/website/docs/flow/index.md
index 140b5a69a4..8b8f1dd610 100644
--- a/website/docs/flow/index.md
+++ b/website/docs/flow/index.md
@@ -12,7 +12,7 @@ For example, a standard login flow would consist of the following stages:
 
 Upon flow execution, a plan containing all stages is generated. This means that all attached policies are evaluated upon execution. This behaviour can be altered by enabling the **Evaluate when stage is run** option on the binding.
 
-The determine which flow should be used, authentik will first check which default authentication flow is configured in the active [**Brand**](../core/brands.md). If no default is configured there, the policies in all flows with the matching designation are checked, and the first flow with matching policies sorted by `slug` will be used.
+To determine which flow should be used, authentik will first check which default authentication flow is configured in the active [**Brand**](../core/brands.md). If no default is configured there, the policies in all flows with the matching designation are checked, and the first flow with matching policies sorted by `slug` will be used.
 
 ## Permissions