enhancement on the 3. Scope section and its sub-sections

A scope in a document typically is for to define the aspects covered by the document.
Although, there are some imperatives in the section 3. Scope (e.g., requiring the implementers to be compliant to the requirements of the flows and support at least either SD-JWT VC or ISO mdocs), and it would be easier for the readers to properly implement having such texts in the later sections that describe requirements and recommendations per each flow.

Besides, the latter half of the section 3 (describing the profiles of OID4VCI, IETF SD-JWT VC, and either remote or in-person can be used for OID4VP), 3.1 Assumptions, and 3.3 Standards Requirements are informative texts which are not defining the aspects covered by the document. It may be better to move such parts to either introduction or later sections.

By the way, is "offline use-cases, e.g. over BLE" written in the end of the 3.4. Out of Scope section meaning proximity?

Start by reading section 3, including 3.1 Assumptions, 3.3 Standards Requirements, and 3.4 Out of Scope, in the document. Review which passages define scope versus requirements or informative context, then reorganize them as proposed and clarify whether “offline use-cases, e.g. over BLE” means proximity use cases.