diff --git a/website/docs/add-secure-apps/flows-stages/stages/index.md b/website/docs/add-secure-apps/flows-stages/stages/index.md
index 2491b3542e..1ac0e09d86 100644
--- a/website/docs/add-secure-apps/flows-stages/stages/index.md
+++ b/website/docs/add-secure-apps/flows-stages/stages/index.md
@@ -65,7 +65,8 @@ To bind a stage to a flow (which adds the stage as a "step" in the flow), follow
 2. In the Admin interface, navigate to **Flows and Stages > Flows**.
 3. In the list of flows, click the name of the flow to which you want to bind one or more stages.
 4. On the Flow page, click the **Stage Bindings** tab at the top.
-5. Here, you can either create a new stage and bind it to the flow with **New Stage**, or select an existing stage and bind it to the flow with **Bind Existing Stage**.
+5. Click **Create or bind...**.
+6. Here, you can choose to either bind an existing stage to the flow with **Existing Stage** or create a new stage and bind it to the flow with **Bind New Stage**.
 
 ### Control access to a stage
 
@@ -83,14 +84,11 @@ To bind a user or a group to a stage binding for a specific flow, follow these s
 1. Log in as an admin to authentik, and go to the Admin interface.
 2. In the Admin interface, navigate to **Flows and Stages > Flows**.
 3. In the list of flows, click the name of the flow to which you want to bind one or more stages.
-4. On the Flow page, click the **Stage Bindings** tab at the top.
-5. Locate the stage binding to which you want to bind a user or group, and then **click the caret (>) to expand the stage binding details.**
-
-![](./edit_stage_binding.png)
-
-6. In the expanded area, click **Bind existing policy/group/user**.
-7. In the **Create Binding** box, select either the tab for **Group** or **User**.
+4. On that Flow's detail page, click the **Stage Bindings** tab at the top.
+5. In the list, locate the stage binding to which you want to bind a user or group, and then **click the caret (>) to expand the stage binding details.**
+6. In the expanded area, click **Create or bind...**.
+7. Under **Bind Existing**, select either **Bind a user** or **Bind a group**.
 8. In the drop-down list, select the group or user.
-9. Optionally, configure additional settings for the binding, and then click **Create Stage Binding** to create the binding and close the box.
+9. Optionally, configure additional settings for the binding, and then click **Create** to create the binding and close the box.
 
 Learn more about the different types of [bindings](../../bindings-overview/index.md) in authentik and [working with them](../../bindings-overview/work-with-bindings.md).
diff --git a/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx b/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx
index a162d58a93..379ffd6d2a 100644
--- a/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx
+++ b/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx
@@ -65,10 +65,11 @@ Now you'll need to create the LDAP authentication flow and bind the previously c
     - Provide a **Name**, **Title** and **Slug** for the flow (e.g. `ldap-authentication-flow`).
     - Set **Designation** to `Authentication`.
 3. Click **Create**.
-4. Click the name of the newly created flow, open the **Stage Bindings** tab, and click **Bind existing stage**.
-5. Select the previously created LDAP Identification Stage (e.g.`ldap-identification-stage`), set the order to `10`, and click **Create**.
-6. Click **Bind existing stage**.
-7. Select the previously created LDAP User Login Stage (e.g.`ldap-authentication-login-stage`), set the order to `30`, and click **Create**.
+4. Click the name of the newly created flow, open the **Stage Bindings** tab, and click **Create or bind...**
+5. Select **Existing stage**.
+6. Select the previously created LDAP Identification Stage (e.g.`ldap-identification-stage`), set the order to `10`, and click **Create**.
+7. Repeat above steps: click **Create or bind...** and then select **Existing stage**.
+8. Select the previously created LDAP User Login Stage (e.g.`ldap-authentication-login-stage`), set the order to `30`, and click **Create**.
 
 ## Create an LDAP application and provider
 
diff --git a/website/docs/add-secure-apps/providers/single-logout/index.md b/website/docs/add-secure-apps/providers/single-logout/index.md
index 65c2fb0548..3607204afc 100644
--- a/website/docs/add-secure-apps/providers/single-logout/index.md
+++ b/website/docs/add-secure-apps/providers/single-logout/index.md
@@ -82,9 +82,9 @@ By default, when a user logs out from an application (RP-initiated logout), only
 2. Navigate to **Flows and Stages** > **Flows**.
 3. Click `default-provider-invalidation-flow` to open the flow.
 4. Click the **Stage Bindings** tab.
-5. Click **Bind Existing Stage**.
-6. In the **Stage** dropdown, select `default-invalidation-logout`.
-7. Click **Create**.
+5. Click **Create or bind...** and select **Existing stage**.
+6. In the **Stage** field, select `default-invalidation-logout` from the drop-down list.
+7. Configure any other settings, and then click **Create**.
 
 After this change, when users log out from any application, they will be logged out of authentik and all other connected applications.