Deploy to GitHub pages

italia · May 16, 2024 · a44400f · a44400f
1 parent 889d24e
commit a44400f
Show file tree

Hide file tree

Showing 6 changed files with 5 additions and 5 deletions.
diff --git a/versione-corrente/en/.doctrees/environment.pickle b/versione-corrente/en/.doctrees/environment.pickle
diff --git a/versione-corrente/en/.doctrees/wallet-attestation.doctree b/versione-corrente/en/.doctrees/wallet-attestation.doctree
diff --git a/versione-corrente/en/_sources/wallet-attestation.rst.txt b/versione-corrente/en/_sources/wallet-attestation.rst.txt
@@ -27,10 +27,10 @@ The following requirements for the Wallet Attestation are met:
 - Private keys MUST be generated and stored in the WSCD using at least one of the approaches listed below:
 
   - **Local Internal WSCD**: in this approach, the WSCD relies entirely on the device's native cryptographic hardware, such as the Secure Enclave on iOS devices or the Hardware Backed Keystore or Strongbox on Android devices.
-  - **Local External WSCD**: the WSCD is an hardware external to the User's device, such as a smart card compliant with _GlobalPlatform_ and supporting _JavaCard_.
+  - **Local External WSCD**: the WSCD is an hardware external to the User's device, such as a smart card compliant with *GlobalPlatform* and supporting *JavaCard*.
   - **Remote WSCD**: Here, the WSCD utilizes a remote Hardware Security Module (HSM).
 
-  - **Local Hybrid WSCD**: the WSCD involves a pluggable internal hardware component within the User's device, such as an _eUICC_ that adheres to _GlobalPlatform_ standards and supports _JavaCard_.
+  - **Local Hybrid WSCD**: the WSCD involves a pluggable internal hardware component within the User's device, such as an *eUICC* that adheres to *GlobalPlatform* standards and supports *JavaCard*.
   - **Remote Hybrid WSCD**: the WSCD involves a local component mixed with a remote service.
 
 .. warning::

diff --git a/versione-corrente/en/searchindex.js b/versione-corrente/en/searchindex.js
diff --git a/versione-corrente/en/wallet-attestation.html b/versione-corrente/en/wallet-attestation.html
@@ -1094,9 +1094,9 @@ <h2>Requirements<a class="headerlink" href="#requirements" title="Permalink to t
 <li><p>Private keys MUST be generated and stored in the WSCD using at least one of the approaches listed below:</p>
 <ul>
 <li><p><strong>Local Internal WSCD</strong>: in this approach, the WSCD relies entirely on the device's native cryptographic hardware, such as the Secure Enclave on iOS devices or the Hardware Backed Keystore or Strongbox on Android devices.</p></li>
-<li><p><strong>Local External WSCD</strong>: the WSCD is an hardware external to the User's device, such as a smart card compliant with _GlobalPlatform_ and supporting _JavaCard_.</p></li>
+<li><p><strong>Local External WSCD</strong>: the WSCD is an hardware external to the User's device, such as a smart card compliant with <em>GlobalPlatform</em> and supporting <em>JavaCard</em>.</p></li>
 <li><p><strong>Remote WSCD</strong>: Here, the WSCD utilizes a remote Hardware Security Module (HSM).</p></li>
-<li><p><strong>Local Hybrid WSCD</strong>: the WSCD involves a pluggable internal hardware component within the User's device, such as an _eUICC_ that adheres to _GlobalPlatform_ standards and supports _JavaCard_.</p></li>
+<li><p><strong>Local Hybrid WSCD</strong>: the WSCD involves a pluggable internal hardware component within the User's device, such as an <em>eUICC</em> that adheres to <em>GlobalPlatform</em> standards and supports <em>JavaCard</em>.</p></li>
 <li><p><strong>Remote Hybrid WSCD</strong>: the WSCD involves a local component mixed with a remote service.</p></li>
 </ul>
 </li>

diff --git a/versione-corrente/it/.doctrees/environment.pickle b/versione-corrente/it/.doctrees/environment.pickle