Deploy to GitHub pages

italia · Mar 29, 2024 · 940e557 · 940e557
1 parent 7e9e15c
commit 940e557
Show file tree

Hide file tree

Showing 6 changed files with 3 additions and 3 deletions.
diff --git a/wallet-instance-lifecycle/en/.doctrees/environment.pickle b/wallet-instance-lifecycle/en/.doctrees/environment.pickle
diff --git a/wallet-instance-lifecycle/en/.doctrees/wallet-attestation.doctree b/wallet-instance-lifecycle/en/.doctrees/wallet-attestation.doctree
diff --git a/wallet-instance-lifecycle/en/_sources/wallet-attestation.rst.txt b/wallet-instance-lifecycle/en/_sources/wallet-attestation.rst.txt
@@ -493,7 +493,7 @@ The lifecycle of a Wallet Instance encompasses all the potential states it can c
    :target: https://www.plantuml.com/plantuml/uml/SoWkIImgAStDuOhMYbNGrRLJyCm32kNafAPOAMH2c5mAG00N1YloBqWjIYp9pCzBpB5IA4ijoaoh1Ab25WUh2qlCoKm1gW1HYIMf83KGCKnJClDmg799JKmkoIm3IW1DAaejoyzEHRSBfpfCbmEzQQLGceVaDOH6x4emxS9KWd0mfgH3QbuAC801
 
 
-A Wallet Instance can obtain a Wallet Attestation if it's in either `Installed`, `Operational` or `Valid` state; that implies that a `Deactivated` Wallet Instance cannot obtain a Wallet Attestation hence it cannot interact with other entities such as PID/(Q)EAA Providers and Relying Parties.
+A Wallet Instance SHOULD obtain a Wallet Attestation if it's in either `Installed`, `Operational` or `Valid` state; that implies that a `Deactivated` Wallet Instance cannot obtain a Wallet Attestation hence it cannot interact with other entities of the ecosystem, such as PID/(Q)EAA Providers and Relying Parties.
 
 States
 ~~~~~~~~~~~~~~~~~~

diff --git a/wallet-instance-lifecycle/en/searchindex.js b/wallet-instance-lifecycle/en/searchindex.js
diff --git a/wallet-instance-lifecycle/en/wallet-attestation.html b/wallet-instance-lifecycle/en/wallet-attestation.html
@@ -1526,7 +1526,7 @@ <h2>Wallet Instance Lifecycle<a class="headerlink" href="#wallet-instance-lifecy
 <figure class="align-default" id="id3">
 <a class="reference external image-reference" href="https://www.plantuml.com/plantuml/uml/SoWkIImgAStDuOhMYbNGrRLJyCm32kNafAPOAMH2c5mAG00N1YloBqWjIYp9pCzBpB5IA4ijoaoh1Ab25WUh2qlCoKm1gW1HYIMf83KGCKnJClDmg799JKmkoIm3IW1DAaejoyzEHRSBfpfCbmEzQQLGceVaDOH6x4emxS9KWd0mfgH3QbuAC801"><img alt="Illustration representing the Wallet Instance lifecycle, with the states explained below." src="../../images/wallet_instance_lifecycle.svg" /></a>
 </figure>
-<p>A Wallet Instance can obtain a Wallet Attestation if it's in either <cite>Installed</cite>, <cite>Operational</cite> or <cite>Valid</cite> state; that implies that a <cite>Deactivated</cite> Wallet Instance cannot obtain a Wallet Attestation hence it cannot interact with other entities such as PID/(Q)EAA Providers and Relying Parties.</p>
+<p>A Wallet Instance SHOULD obtain a Wallet Attestation if it's in either <cite>Installed</cite>, <cite>Operational</cite> or <cite>Valid</cite> state; that implies that a <cite>Deactivated</cite> Wallet Instance cannot obtain a Wallet Attestation hence it cannot interact with other entities of the ecosystem, such as PID/(Q)EAA Providers and Relying Parties.</p>
 <section id="states">
 <h3>States<a class="headerlink" href="#states" title="Permalink to this heading">¶</a></h3>
 <table class="docutils align-default">

diff --git a/wallet-instance-lifecycle/it/.doctrees/environment.pickle b/wallet-instance-lifecycle/it/.doctrees/environment.pickle