Random tweaks

README.md

@@ -35,9 +35,9 @@ For information and to order the product go to:
 * [End-user initiated login: How It Works](./how-it-works/user-initiated-login-howitworks.md)
 * [Merchant initiated login: How It Works](./how-it-works/merchant-initiated-login-howitworks.md)
 
-Related flow:
+## Recommended flows
 
-* [Using Login and Recurring API together](https://developer.vippsmobilepay.com/docs/solutions/recurring-and-login)
+* [Subscriptions: Using Login and Recurring API together](https://developer.vippsmobilepay.com/docs/solutions/recurring-and-login)
 
 ## Plugins for Login
 

api-guide/app-integration.md

@@ -77,18 +77,24 @@ merchant-app://callback/?state=RFiQdrl_lvJUpVmTRSKmsZRGLM0G1N1qh0WebZ1gDNk&resum
 
 ```mermaid
 sequenceDiagram
+    participant merchantApp as Merchant app
+    participant merchantBackend as Merchant backend
+    participant vmBackend as Vipps MobilePay Backend
+    participant vmApp as Vipps/MobilePay app
+    participant merchantAppControlledBrowser as Merchant app controlled browser
+
     merchantApp ->> merchantBackend : Initiate login
     merchantBackend ->> merchantApp: 1: Authorize request
     merchantApp ->> merchantAppControlledBrowser : 2: Open authorize request url
-    merchantAppControlledBrowser -->> vippsApp : 3: User opens Vipps or MobilePay app in login client
-    vippsApp -->> vippsApp: User accepts the login
-    vippsApp -->> merchantApp : 4: Open app_callback_uri
+    merchantAppControlledBrowser -->> vmApp : 3: User opens Vipps or MobilePay app in login client
+    vmApp -->> vmApp: User accepts the login
+    vmApp -->> merchantApp : 4: Open app_callback_uri
     merchantApp ->> merchantAppControlledBrowser : 5: Either show the browser that is already open, <br/> or open a new browser at the resume_uri
     merchantAppControlledBrowser -->> merchantAppControlledBrowser: User consents
     merchantAppControlledBrowser -->> merchantApp : 6: Open redirect_uri, includes code and state
     merchantApp ->>merchantBackend : 7: Finish login (code, state)
-    merchantBackend ->> vippsBackend : 8: Get userinfo and auth token using code
-    vippsBackend -->> merchantBackend : Userinfo / Auth token
+    merchantBackend ->> vmBackend : 8: Get userinfo and auth token using code
+    vmBackend -->> merchantBackend : Userinfo / Auth token
     merchantBackend ->> merchantApp : Userinfo / Auth token
 ```
 

api-guide/browser-flow-integration.md

@@ -435,8 +435,8 @@ If a fatal error occurs where the user can not be redirected back to the merchan
 
 ## Call by call
 
-A very basic case, from a user clicks *Log in with Vipps* until the merchant receives login token
-and the user's information, is shown below:
+The following is a very basic case, starting with a user clicking *Log in with Vipps/MobilePay* until the merchant receives login token
+and the user's information:
 
 0. Before all this, the merchant has fetched the OpenID configuration from the well-known endpoint
    and cached it.

tools/login-api.postman_collection.json

@@ -1,7 +1,7 @@
 {
 	"info": {
 		"_postman_id": "0bfe1ba1-4fef-402f-9d85-32a75d444749",
-		"name": "vipps-login-api",
+		"name": "Vipps MobilePay Login API",
 		"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
 	},
 	"item": [