Deployed 0ac2637 to 1.4.0 with MkDocs 1.6.1 and mike 2.1.3

Author: github-actions[bot]

1.4.0/discussion-topics/f-digital-credential-api/index.html

@@ -401,20 +401,26 @@
 
 <h1 id="arf-discussion-topics">ARF Discussion topics</h1>
 <h2 id="introduction">Introduction</h2>
-<p>The Architecture and Reference Framework (ARF) is in development. To complete the ARF, the commission concluded 21 open items – called topics – need to be addressed and discussed up to end of 2025. This ARF roadmap project provides and overview on these topics, including a planning when they are addressed.</p>
+<p>The Architecture and Reference Framework (ARF) is in development. To complete
+the ARF, the commission concluded 21 open items – called topics – need to be
+addressed and discussed up to end of 2025. This ARF roadmap project provides and
+overview on these topics, including a planning when they are addressed.</p>
 <h2 id="focus-of-the-arf-is-to-establishing-high-level-requirements">Focus of the ARF is to establishing high level requirements</h2>
 <p>The purpose of the ARF is to establish high level requirements for the EUDI Wallet ecosystem, to create uniform conditions for the implementation of the legislative act. The ARF also defines the technical specifications, standards and procedures that the Commission shall reference or develop for the purpose of implementing the eIDAS Regulation.</p>
 <h2 id="process">Process</h2>
-<p>The process of establishing high level requirements has 5 steps:
-1. The discussion paper on the topic is published on GitHub.
-2. The discussion paper on the topic contains a number of questions: each question will have a separate response thread in the <a href="https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/discussions">discussion area of GitHub</a>.
-3. After three weeks the discussion on the topic will be closed. The Commission will not publish any answers to responses on GitHub, but your input will be considered.
-4. The Commission will publish a new ARF version on GitHub about seven weeks after publication of the discussion paper, containing an update on the topic.<br />
-5. The published ARF version can be commented on GitHub. </p>
+<p>The process of establishing high level requirements has 5 steps:</p>
+<ol>
+<li>The discussion paper on the topic is published on GitHub.</li>
+<li>The discussion paper on the topic contains a number of questions: each question will have a separate response thread in the <a href="https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/discussions">discussion area of GitHub</a>.</li>
+<li>After three weeks the discussion on the topic will be closed. The Commission will not publish any answers to responses on GitHub, but your input will be considered.</li>
+<li>The Commission will publish a new ARF version on GitHub about seven weeks after publication of the discussion paper, containing an update on the topic.  </li>
+<li>The published ARF version can be commented on GitHub.</li>
+</ol>
 <h2 id="topics">Topics</h2>
 <ul>
 <li>A - <a href="a-privacy-risks-and-mitigations/">Privacy risks and mitigation</a></li>
 <li>B - <a href="b-re-issuance-and-batch-issuance-of-pids-and-attestations/">Re-issuance and batch issuance of PIDs and Attestations</a></li>
+<li>F - <a href="f-digital-credential-api/">Digital Credential API (former known as browser API)</a></li>
 </ul>