docs: update name for post_logout_redirect_url

docs/docs/debugging.mdx

@@ -59,7 +59,7 @@ Sometimes, calling `/oauth2/sessions/logout` does not behave as expected, for
 example:
 
 - An error occurs.
-- You are being redirected directly to the post_logout_url instead of the logout
+- You are being redirected directly to the post_logout_redirect_uri instead of the logout
   UI.
 
 First of all, there are two types of logout requests - one is called "OP (OpenID

docs/docs/implement-consent.md

@@ -330,9 +330,9 @@ A logout request may be initiated by the OpenID Provider (OP - **you**) or by
 the Relying Party (RP - the OAuth2 Client):
 
 - The OP-initiated flow does not need an `id_token_hint`, and it may neither
-  define a `state` nor a `post_logout_url`.
+  define a `state` nor a `post_logout_redirect_uri`.
 - The RP-initiated flow needs an `id_token_hint` and may optionally define
-  `state` and `post_logout_url`.
+  `state` and `post_logout_redirect_uri`.
 
 Both requests follow the same pattern as user login and user consent. Before the
 logout is completed, the user is redirected to the **Logout UI** (similar to
@@ -359,7 +359,7 @@ Legend:
   `localhost`, `google.com`).**
 - `****`: The `post_logout_redirect` defaults to the configuration value of
   `urls.post_logout_redirect`. If it's an RP-initiated flow and a
-  `post_logout_url` was set and that URL is in the array of the OAuth2 Client's
+  `post_logout_redirect_uri` was set and that URL is in the array of the OAuth2 Client's
   `urls.post_logout_redirect`, the browser will be redirected there instead.
 
 ### Logout Flow

docs/versioned_docs/version-1.4/debugging.mdx

@@ -59,7 +59,7 @@ Sometimes, calling `/oauth2/sessions/logout` does not behave as expected, for
 example:
 
 - An error occurs.
-- You are being redirected directly to the post_logout_url instead of the logout
+- You are being redirected directly to the post_logout_redirect_uri instead of the logout
   UI.
 
 First of all, there are two types of logout requests - one is called "OP (OpenID

docs/versioned_docs/version-1.4/implement-consent.md

@@ -330,9 +330,9 @@ A logout request may be initiated by the OpenID Provider (OP - **you**) or by
 the Relying Party (RP - the OAuth2 Client):
 
 - The OP-initiated flow does not need an `id_token_hint`, and it may neither
-  define a `state` nor a `post_logout_url`.
+  define a `state` nor a `post_logout_redirect_uri`.
 - The RP-initiated flow needs an `id_token_hint` and may optionally define
-  `state` and `post_logout_url`.
+  `state` and `post_logout_redirect_uri`.
 
 Both requests follow the same pattern as user login and user consent. Before the
 logout is completed, the user is redirected to the **Logout UI** (similar to
@@ -359,7 +359,7 @@ Legend:
   `localhost`, `google.com`).**
 - `****`: The `post_logout_redirect` defaults to the configuration value of
   `urls.post_logout_redirect`. If it's an RP-initiated flow and a
-  `post_logout_url` was set and that URL is in the array of the OAuth2 Client's
+  `post_logout_redirect_uri` was set and that URL is in the array of the OAuth2 Client's
   `urls.post_logout_redirect`, the browser will be redirected there instead.
 
 ### Logout Flow

docs/versioned_docs/version-v1.4/debugging.mdx

@@ -59,7 +59,7 @@ Sometimes, calling `/oauth2/sessions/logout` does not behave as expected, for
 example:
 
 - An error occurs.
-- You are being redirected directly to the post_logout_url instead of the logout
+- You are being redirected directly to the post_logout_redirect_uri instead of the logout
   UI.
 
 First of all, there are two types of logout requests - one is called "OP (OpenID

docs/versioned_docs/version-v1.4/implement-consent.md

@@ -330,9 +330,9 @@ A logout request may be initiated by the OpenID Provider (OP - **you**) or by
 the Relying Party (RP - the OAuth2 Client):
 
 - The OP-initiated flow does not need an `id_token_hint`, and it may neither
-  define a `state` nor a `post_logout_url`.
+  define a `state` nor a `post_logout_redirect_uri`.
 - The RP-initiated flow needs an `id_token_hint` and may optionally define
-  `state` and `post_logout_url`.
+  `state` and `post_logout_redirect_uri`.
 
 Both requests follow the same pattern as user login and user consent. Before the
 logout is completed, the user is redirected to the **Logout UI** (similar to
@@ -359,7 +359,7 @@ Legend:
   `localhost`, `google.com`).**
 - `****`: The `post_logout_redirect` defaults to the configuration value of
   `urls.post_logout_redirect`. If it's an RP-initiated flow and a
-  `post_logout_url` was set and that URL is in the array of the OAuth2 Client's
+  `post_logout_redirect_uri` was set and that URL is in the array of the OAuth2 Client's
   `urls.post_logout_redirect`, the browser will be redirected there instead.
 
 ### Logout Flow

docs/versioned_docs/version-v1.5/debugging.mdx

@@ -59,7 +59,7 @@ Sometimes, calling `/oauth2/sessions/logout` does not behave as expected, for
 example:
 
 - An error occurs.
-- You are being redirected directly to the post_logout_url instead of the logout
+- You are being redirected directly to the post_logout_redirect_uri instead of the logout
   UI.
 
 First of all, there are two types of logout requests - one is called "OP (OpenID

docs/versioned_docs/version-v1.5/implement-consent.md

@@ -330,9 +330,9 @@ A logout request may be initiated by the OpenID Provider (OP - **you**) or by
 the Relying Party (RP - the OAuth2 Client):
 
 - The OP-initiated flow does not need an `id_token_hint`, and it may neither
-  define a `state` nor a `post_logout_url`.
+  define a `state` nor a `post_logout_redirect_uri`.
 - The RP-initiated flow needs an `id_token_hint` and may optionally define
-  `state` and `post_logout_url`.
+  `state` and `post_logout_redirect_uri`.
 
 Both requests follow the same pattern as user login and user consent. Before the
 logout is completed, the user is redirected to the **Logout UI** (similar to
@@ -359,7 +359,7 @@ Legend:
   `localhost`, `google.com`).**
 - `****`: The `post_logout_redirect` defaults to the configuration value of
   `urls.post_logout_redirect`. If it's an RP-initiated flow and a
-  `post_logout_url` was set and that URL is in the array of the OAuth2 Client's
+  `post_logout_redirect_uri` was set and that URL is in the array of the OAuth2 Client's
   `urls.post_logout_redirect`, the browser will be redirected there instead.
 
 ### Logout Flow