From 18c12201a3e6227fdfcf03bb568a8ba3c1d6dd1c Mon Sep 17 00:00:00 2001
From: Michael Kuckuk <8076094+LBBO@users.noreply.github.com>
Date: Wed, 26 Jul 2023 11:54:39 +0200
Subject: [PATCH] refactor: run formatter

---
 docs/hydra/login-consent-flow.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/hydra/login-consent-flow.md b/docs/hydra/login-consent-flow.md
index fbcf2b888..57633c971 100644
--- a/docs/hydra/login-consent-flow.md
+++ b/docs/hydra/login-consent-flow.md
@@ -29,9 +29,9 @@ The flow itself works as follows:
 4. The user's user agent follows the redirect and lands back at Ory OAuth2 & OpenID Connect. Next, Ory OAuth2 & OpenID Connect
    redirects the user's user agent to the Consent Provider, hosted at - for example -
    `http://consent-service/consent?consent_challenge=4567...`
-5. The Consent Provider shows a user interface which asks the user if they would like to grant the OAuth 2.0 Client the
-   requested permissions ("OAuth 2.0 Scope"). You've probably seen this screen around, which is usually something similar to:
-   _"Would you like to grant Facebook Image Backup access to all your private and public images?"_.
+5. The Consent Provider shows a user interface which asks the user if they would like to grant the OAuth 2.0 Client the requested
+   permissions ("OAuth 2.0 Scope"). You've probably seen this screen around, which is usually something similar to: _"Would you
+   like to grant Facebook Image Backup access to all your private and public images?"_.
 6. The Consent Provider makes another REST request to Ory OAuth2 & OpenID Connect to let it know which permissions the user
    authorized, and if the user authorized the request at all. The user can usually choose to not grant an application any access
    to his/her personal data. In the response of that REST request, a redirect URL is included along the lines of