improvements and corrections to the content

app/page.tsx

@@ -50,7 +50,7 @@ export default function Home() {
         inverse
       >
         <div className="flex justify-center items-center bg-slate-200 rounded-2xl h-[260px] md:h-[400px]">
-          <span className="font-sans text-primary">PLACEHOLDER</span>
+          <iframe width="400" height="260" src="https://www.youtube-nocookie.com/embed/bNGSdlvIPfI?si=ajKeL15xl1NLarrU" title="YouTube video player" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerPolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
         </div>
       </Banner>
     </main>

content/about.tsx

@@ -7,40 +7,31 @@ Markdown supported for description
 export const ABOUT_CONTENT = {
   WHO_WE_ARE: {
     TITLE: "Who we are",
-    DESCRIPTION: `TLSNotary is an open-source protocol developed by the <u>Privacy and Scaling Exploration (PSE)</u> research lab of the Ethereum Foundation.
-    \nTLSNotary is not a new project; in fact, it has been around for <u>more than a decade</u>. In 2022, TLSNotary was rebuilt from the ground up in <ins>Rust</ins> incorporating state-of-the-art cryptographic protocols. This renewed version of the TLSNotary protocol offers enhanced security, privacy, and performance.
+    DESCRIPTION: `TLSNotary is an open-source protocol developed by the **Privacy and Scaling Exploration (PSE)** research lab of the Ethereum Foundation.
+    \nTLSNotary is not a new project; in fact, it has been around for **more than a decade**. In 2022, TLSNotary was rebuilt from the ground up in **Rust** incorporating state-of-the-art cryptographic protocols. This renewed version of the TLSNotary protocol offers enhanced security, privacy, and performance.
     `,
   },
   HOW_IT_WORKS: {
     TITLE: "How it works",
     DESCRIPTION: `TLSNotary is a protocol which allows people to export data from any web application and prove facts about it to a third-party in a privacy-preserving way by leveraging secure multi-party computation (MPC) to authenticate data communicated between a Prover and a TLS-enabled web server.
-        <img class="w-full" src="/images/ts-notaly-diagram.svg" />
+        <img class="w-full" src="/images/tlsnotary-diagram.svg" />
       `,
 
     STEPS: [
       {
         TITLE: "Step 1: Multiparty TLS Request",
         DESCRIPTION:
-          "The Prover requests data from a Server over TLS while cooperating with the Verifier in secure and privacy-preserving multi-party computation (MPC).",
-        icon: <Icons.GeometricPattern1 size={120} />,
+          "The Prover requests data from a Server over TLS. The verifier cooperates in secure and privacy-preserving multi-party computation (MPC). This cooperation guaranties that the Prover can not cheat and allows the Verifier to check the authenticity of the data in step 3.",
       },
       {
         TITLE: "Step 2: Selective Disclosure",
         DESCRIPTION:
-          "The Prover selectively discloses the data to the Verifier by redacting sensitive information prior to sharing it. Selective disclosure may involve simple redactions, or more advanced techniques such as a zero-knowledge proofs that can prove properties of redacted data without revealing the data itself.",
-        icon: <Icons.GeometricPattern2 size={120} />,
+          "The Prover selectively discloses the data to the Verifier by redacting sensitive information prior to sharing it. Selective disclosure may involve simple redactions, or more advanced techniques such as a zero-knowledge proofs that can prove properties of redacted data without revealing the data itself."
       },
       {
-        TITLE: "Step 3: Notarization",
+        TITLE: "Step 3: Data Verification",
         DESCRIPTION:
-          "A Notary cryptographically signs commitments to the data and the server's identity. Verifiers will only accept the signed data if they trust the Notary. They can also require signed data from multiple Notaries to rule out collusion between the Prover and a Notary.",
-        icon: <Icons.GeometricPattern6 size={120} />,
-      },
-      {
-        TITLE: "Step 4: Data Verification",
-        DESCRIPTION:
-          "The Verifier validates the proof by verifying the origin of the data. This can be verified by inspecting the Server certificate through trusted certificate authorities (CAs). The Verifier can now make assertions about the non-redacted content of the transcript.",
-        icon: <Icons.GeometricPattern3 size={120} />,
+          "The Verifier verifies that the prover did not tamper with the data and also verifiers the data origin, by inspecting the Server certificate through trusted certificate authorities (CAs). The Verifier can now make assertions about the non-redacted content of the transcript."
       },
     ],
   },

content/faq.tsx

@@ -25,7 +25,12 @@ export const FAQS: FAQItem[] = [
   {
     question: "What is the overhead of using TLSNotary?",
     answer:
-      "To the server, the TLS connection appears the same as any other connection. Only the User communicates with the Server, not the Notary or the Verifier. However, the timing patterns of TLS communication might have a different fingerprint, so through statistical analysis, specific identifying patterns might be uncovered.",
+      "The Multi-Party Computation (MPC) between the Prover and the Verifier requires significant bandwidth, orders of magnitude more than the Server’s data size."
+  },
+  {
+    question: "Can the server detect that a TLS session is being notarized?",
+    answer: `
+      To the server, the TLS connection appears the same as any other connection. Only the User communicates with the Server, not the Notary or the Verifier. However, the timing patterns of TLS communication might have a different fingerprint, so through statistical analysis, specific identifying patterns might be uncovered.`,
   },
   {
     question: "Can TLSNotary be used for public data?",
@@ -35,7 +40,7 @@ export const FAQS: FAQItem[] = [
   {
     question: "How can I inspect and verify a TLSNotary proof?",
     answer:
-      "The easiest way is to use the proof-of-concept proof visualizer: TLSNotary Proof Visualizer",
+      "The easiest way is to use the proof-of-concept proof visualizer: [TLSNotary Proof Visualizer](https://tlsnotary.github.io/proof_viz/)",
   },
   {
     question: "Which TLS versions are supported?",

content/homepage.tsx

@@ -1,14 +1,14 @@
 export const HOMEPAGE_CONTENT = {
-  TITLE: "Privately verify any data on the web",
+  TITLE: "Privacy-preserving data portability for any data on the web",
   SUBTITLE: "TLSNotary",
   INTRO: {
     TITLE:
-      "An open-source protocol for authentication with selective disclosure.",
+      "An open-source protocol for private and verifiable data disclosure.",
     DESCRIPTION:
       "TLSNotary can be used to verify the origin of any piece of data, ensuring it hasn't been fabricated or tampered with, while allowing users to redact sensitive information. As a result, the data becomes portable, reusable, and endlessly composable!",
   },
   DOWNLOAD: {
-    TITLE: "Download the browser extension",
-    DESCRIPTION: "PageSigner - the easy way to use TLSNotary",
+    TITLE: "Data portability with endless possibilities",
+    DESCRIPTION: "Watch the TLSNotary presentation at ETHDam 2024",
   },
 };