diff --git a/docs/docs/auth/authentication/webhook.mdx b/docs/docs/auth/authentication/webhook.mdx
index 541801cc61a..8e22cbbe997 100644
--- a/docs/docs/auth/authentication/webhook.mdx
+++ b/docs/docs/auth/authentication/webhook.mdx
@@ -136,6 +136,9 @@ this request. Unlike JWT auth mode, you do not have to pass `X-Hasura-Allowed-Ro
 variables. This is because the webhook is called for each request, allowing the auth service to easily switch the user
 role if needed.
 
+In the example below the `X-Hasura-Is-Owner` and `X-Hasura-Custom` are examples of custom session variables which
+will be available to your permission rules in Hasura Engine.
+
 ```http
 HTTP/1.1 200 OK
 Content-Type: application/json
diff --git a/docs/docs/resources/use-case/gql-backend.mdx b/docs/docs/resources/use-case/gql-backend.mdx
index de74deadc6a..0f1650bfa21 100644
--- a/docs/docs/resources/use-case/gql-backend.mdx
+++ b/docs/docs/resources/use-case/gql-backend.mdx
@@ -298,13 +298,18 @@ from `from session variable` mapping to `X-HASURA-USER-ID`.
 
 <Thumbnail src="/img/resources/hasura-as-gql-backend/insert-permission.png" alt="Cloud Dashboard" width="800px" />
 
-:::info Session variables are key-value pairs returned from the authentication service for each request. When a user
-makes a request, the session token maps to a `USER-ID`. This `USER-ID` can be used in permission to show that inserts
-into a table are only allowed if the `user_id` column has a value equal to that of `USER-ID`, the session variable. :::
+:::info Session variables are key-value pairs returned from the authentication service for each request
+
+When a user makes a request, the session token maps to a `USER-ID`. This `USER-ID` can be used in permission to show
+that inserts into a table are only allowed if the `user_id` column has a value equal to that of `USER-ID`, the session
+variable.
+
 Click on `Save Permissions`.
 
 Similarly you can setup `Select`, `Update` and `Delete`permissions and permissions for the `todos table`.
 
+:::
+
 ## Advanced topics
 
 Up until now, we have addressed the data-modeling and relationships part of constructing a backend. However, Hasura
diff --git a/docs/static/img/data-federation/data-federation_multi-protocol-federation-capabilities.png b/docs/static/img/data-federation/data-federation_multi-protocol-federation-capabilities.png
index 6eacce0d924..5e5b4a75072 100644
Binary files a/docs/static/img/data-federation/data-federation_multi-protocol-federation-capabilities.png and b/docs/static/img/data-federation/data-federation_multi-protocol-federation-capabilities.png differ