From 985262c5e665733d9509a69288d5bed87232f4c1 Mon Sep 17 00:00:00 2001 From: fmarino-ipzs <77629526+fmarino-ipzs@users.noreply.github.com> Date: Mon, 24 Jul 2023 11:51:06 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Giuseppe De Marco --- docs/en/pid-eaa-data-model.rst | 8 ++++---- docs/en/pid-eaa-issuance.rst | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/en/pid-eaa-data-model.rst b/docs/en/pid-eaa-data-model.rst index 6baf141ed..e999c5d60 100644 --- a/docs/en/pid-eaa-data-model.rst +++ b/docs/en/pid-eaa-data-model.rst @@ -206,7 +206,7 @@ The ``claims`` parameter contains the User attributes with the following mandato -PID Non-normative examples +PID Non-normative Examples -------------------------- In the following, the non-normative example of a PID. @@ -416,7 +416,7 @@ In the following, we provide a non-normative example of (Q)EAA in JSON. } } -The corresponding SD-JWT for the preivous data is represented as follow, as decoded JSON for both header and payload. +The corresponding SD-JWT for the previous data is represented as follow, as decoded JSON for both header and payload. .. code-block:: JSON @@ -472,7 +472,7 @@ The corresponding SD-JWT for the preivous data is represented as follow, as deco "_sd_alg": "sha-256" } -In the following the disclosure list is given +In the following the disclosure list is given: Claim **evidence**: @@ -529,7 +529,7 @@ Claim **tax_id_code**: - Contents: ``["AJx-095VPrpTtN4QMOqROA", "tax_id_code",`` ``"TINIT-XXXXXXXXXXXXXXXX"]`` -The combined format for the PID issuance is given by +The combined format for the PID issuance is represented below: .. code-block:: diff --git a/docs/en/pid-eaa-issuance.rst b/docs/en/pid-eaa-issuance.rst index 7ff72ce85..9cfca1822 100644 --- a/docs/en/pid-eaa-issuance.rst +++ b/docs/en/pid-eaa-issuance.rst @@ -50,7 +50,7 @@ High-Level (Q)EAA flow The :numref:`fig_High-Level-Flow-ITWallet-QEAA-Issuance` shows a general architecture and highlights the main operations involved in the issuance of a (Q)EAA, following the assumptions listed below: - - the User has a valid PID stored in its own Wallet Instance; + - the User has a valid PID stored in their own Wallet Instance; - the (Q)EAA requires a high security implementation profile. .. _fig_High-Level-Flow-ITWallet-QEAA-Issuance: