From 0ec9ec683224de401d7de41d861ebe561e17a20e Mon Sep 17 00:00:00 2001
From: Dmitri Zagidulin <dzagidulin@gmail.com>
Date: Tue, 28 Jul 2026 12:22:52 -0400
Subject: [PATCH] Restore json-card section formatting.

Signed-off-by: Dmitri Zagidulin <dzagidulin@gmail.com>
---
 index.html | 42 +++++++++++++++++++++---------------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/index.html b/index.html
index 43e3825..089232f 100644
--- a/index.html
+++ b/index.html
@@ -473,35 +473,35 @@ <h4>TemplateRenderMethod</h4>
         <section>
           <h3>The `json-card` Render Suite</h3>
           <p>
-            The `json-card` render suite uses JSON templates to transform a
-            [=verifiable credential=] into a standardized JSON card format. This format
-            enables wallets to display credentials in a responsive card layout with key
-            data highlighted and configurable additional fields. Wallets that implement
-            this method can render the standardized JSON output in their own card UI
-            designs, allowing credentials to be displayed even when a wallet doesn't
-            natively support a specific credential type.
+The `json-card` render suite uses JSON templates to transform a
+[=verifiable credential=] into a standardized JSON card format. This format
+enables wallets to display credentials in a responsive card layout with key
+data highlighted and configurable additional fields. Wallets that implement
+this method can render the standardized JSON output in their own card UI
+designs, allowing credentials to be displayed even when a wallet doesn't
+natively support a specific credential type.
           </p>
 
           <p>
-            The template is a JSON object that matches the `json-card` output structure.
-            String values in the template can be JSON pointer strings (as specified in
-            [[[RFC6901]]]) that reference fields in the [=verifiable credential=]. When
-            processing the template, JSON pointer strings are evaluated against the
-            credential data and replaced with the resolved values. The template MUST
-            conform to the JSON template schema defined below, and the resulting output
-            MUST conform to the `json-card` output schema. Compound data across multiple
-            fields is not supported; each field references a single JSON pointer.
+The template is a JSON object that matches the `json-card` output structure.
+String values in the template can be JSON pointer strings (as specified in
+[[[RFC6901]]]) that reference fields in the [=verifiable credential=]. When
+processing the template, JSON pointer strings are evaluated against the
+credential data and replaced with the resolved values. The template MUST
+conform to the JSON template schema defined below, and the resulting output
+MUST conform to the `json-card` output schema. Compound data across multiple
+fields is not supported; each field references a single JSON pointer.
           </p>
 
           <section>
             <h4>JSON Template Schema</h4>
             <p>
-              The template for a `json-card` render suite MUST be a JSON object that
-              conforms to the following structure. The template structure matches the
-              output structure, but string values can be either literal strings or JSON
-              pointer strings (starting with `/`) that reference fields in the
-              [=verifiable credential=]. The template SHOULD be validated against this
-              schema before processing.
+The template for a `json-card` render suite MUST be a JSON object that
+conforms to the following structure. The template structure matches the
+output structure, but string values can be either literal strings or JSON
+pointer strings (starting with `/`) that reference fields in the
+[=verifiable credential=]. The template SHOULD be validated against this
+schema before processing.
             </p>
 
             <table class="simple">