[Openid-specs-ab] Issue #1824: OpenID4VCI: typos in draft 11, from Section 1 to Section 6 (openid/connect)

[Takahiko Kawasaki]

New issue 1824: OpenID4VCI: typos in draft 11, from Section 1 to Section 6
https://bitbucket.org/openid/connect/issues/1824/openid4vci-typos-in-draft-11-from-section

Takahiko Kawasaki:

### 1. Introduction, the 2nd paragraph

e.g trough cryptographic → e.g. through cryptographic

// Change “e.g” to “e.g.” and “trough” to “through”.

### 2. Terminology, Biometrics-based holder Binding

Biometrics-based holder Binding → Biometrics-based Holder Binding

// Capitalize “h” of “holder”.

### 3.3. Core Concepts, the 6th bullet

at each extention point → at each extension point

// Replace the second “t” in “extention” with “s”.

### 3.3. Core Concepts, the 7th bullet

turn into a verifiable Credential → turn into a Verifiable Credential

// Capitalize “v” of “verifiable”.

### 3.4. Authorization Code Flow, the 2nd paragraph

the diagram and does not → the diagram does not

// Remove “and”.

### 3.4. Authorization Code Flow, the 3rd paragraph

\(1\) The wallet uses → \(1\) The Wallet uses

// Capitalize “w” of “wallet”.

### 3.4. Authorization Code Flow, the 6th paragraph

steps \(2\) and \(3\) happens → steps \(2\) and \(3\) happen

// Remove “s” from “happens”.

### 3.5. Pre-Authorized Code Flow, the 1st paragraph

Access Toke is than used → Access Token is then used

// Change “Toke” to “Token” and “than” to “then”.

### 3.5. Pre-Authorized Code Flow, the 5th paragraph

\(1\) the Credential Issuer → \(1\) The Credential Issuer

// Capitalize “t” of “the”.

### 3.5. Pre-Authorized Code Flow, the 8th paragraph

Pre-Authorized Code obtained in step \(1\) → Pre-Authorized Code obtained in step \(2\)

// Change “\(1\)” to “\(2\)”.

sends a PIN, it has → sends a PIN it has

// Remove “,”.

with the request, → with the request.

// Change “,” to “.”.

### 3.5. Pre-Authorized Code Flow, the 11th paragraph

a channel different that the issuance Flow → a channel different than the issuance Flow

// Change “that” to “than”.

### 4.1.1. Credential Offer Parameters, the bullet for `pre-authorized_code`

MUST be include → MUST be included

// Change “include” to “included”.

### 4.1.3. Sending Credential Offer by Reference Using `credential_offer_uri` Parameter, the 1st example

`GET /credential_offer.jwt HTTP/1.1` → `GET /credential_offer HTTP/1.1`

// Remove “.jwt” from the path or replace it with “.json”. The specification requires responses be JSON \(not JWT\).

### 4.1.3. Sending Credential Offer by Reference Using `credential_offer_uri` Parameter, the 2nd example

`...credential-offer.jwt` → `...credential-offer`

// Remove “.jwt” from the path or replace it with “.json”. The specification requires responses be JSON \(not JWT\).

### 4.1.3. Sending Credential Offer by Reference Using `credential_offer_uri` Prameter, the 3rd example

`HTTP/1.1 201 OK` → `HTTP/1.1 200 OK`

// Change “201” to “200”.

### 5.1.3. Additional Request Parameters, the bullet for `issuer_state`

\(see \(Section 4.1\) → \(see Section 4.1\)

// Remove “\(“ before Section.

### 5.1.4. Pushed Authorization Request, the example

Remove the indentation of the message body.

### 5.2. Successful Authorization Response, the example

Remove the indentation of the `Location` header.

### 6.1. Token Request, two examples

Remove the indentation of the message body.

### 6.2. Successful Token Response, the example

Remove the indentation of the message body.