Merge pull request 0xPolygonID#32 from 0xPolygonID/fix/faq-section

fix html in faq section

Author: cerberushades

src/components/FAQAccordion.js

@@ -19,9 +19,9 @@ export const FAQAccordion = (props) => {
       </div>
       <nav className="faq-dropdown-list">
         <div className="faq-dropdown-list-content">
-          <p className="lead grey-text" dangerouslySetInnerHTML={{__html: content}}></p>
+          <div className="lead grey-text" dangerouslySetInnerHTML={{__html: content}}></div>
         </div>
       </nav>
     </div>
   );
-}
+}

src/css/custom.css

@@ -2583,9 +2583,11 @@ p {
   grid-template-rows: 0fr;
   transition: grid-template-rows 0.5s ease-out;
 }
-.faq-dropdown-list p {
+.faq-dropdown-list div.lead {
   margin: 0;
   padding-bottom: 12px;
+  line-height: 1.75rem;
+  letter-spacing: 0.01rem /* for better visibility */;
 }
 .faq-dropdown-list-content {
   overflow: hidden;

src/data/content-data.js

@@ -261,7 +261,7 @@ export const contentData = {
             },
             {
                 title: 'What main aspects make Polygon ID unique?',
-                content: "<ul><li>Private by default solution, as a result of the ZK native protocol used.</li><li>There is no direct communication between issuer and verifiers.<li>Offering a scalable and self-sovereign digital identity solution.</li><li>Allows on-chain and off-chain verification, facilitating the deployment of both web2 and web3 use cases.</li><li>Supports bulk issuance of claims with a highly efficient on-chain storage at a minimum transactional cost.</li><li><ul>It enables a wide range of use cases to settle the foundation for a transformative impact with:</li><li>protection against Sybil attacks while preserving privacy. This is achieved using nullifier techniques that assure that an identity (human being) can undertake an action only once. This becomes a key feature for specific use cases such as voting processes.<li>non-reusable proofs: guaranteeing the verifier that the proof presented by the user was not a copy of a proof generated by another identity, and allowing the verifier to check its validity.</li><li>protection against digital footprint tracking.</ul></ul>"
+                content: "<ul><li>Private by default solution, as a result of the ZK native protocol used.</li><li>There is no direct communication between issuer and verifiers.<li>Offering a scalable and self-sovereign digital identity solution.</li><li>Allows on-chain and off-chain verification, facilitating the deployment of both web2 and web3 use cases.</li><li>Supports bulk issuance of claims with a highly efficient on-chain storage at a minimum transactional cost.</li><li><ul>It enables a wide range of use cases to settle the foundation for a transformative impact with:<li>protection against Sybil attacks while preserving privacy. This is achieved using nullifier techniques that assure that an identity (human being) can undertake an action only once. This becomes a key feature for specific use cases such as voting processes.<li>non-reusable proofs: guaranteeing the verifier that the proof presented by the user was not a copy of a proof generated by another identity, and allowing the verifier to check its validity.</li><li>protection against digital footprint tracking.</ul></ul>"
             },
             {
                 title: 'How do I use the Polygon ID wallet?',