diff --git a/docs/concepts/two-layer-trust.md b/docs/concepts/two-layer-trust.md index 7489d0c..2acef50 100644 --- a/docs/concepts/two-layer-trust.md +++ b/docs/concepts/two-layer-trust.md @@ -13,7 +13,7 @@ When you capture media with SignedShot, two things happen: 1. **Capture Trust** — The server issues a signed token proving a verified device started a capture session 2. **Media Integrity** — The device signs the content hash using its Secure Enclave -Together, these prove: *"This exact content was captured on a verified device, in an authorized session, and hasn't been modified since."* +Together, these prove: *"This exact content was captured on a verified device, in an authorized session, and hasn't been modified since."* Verifiers choose which claims to trust and at what level. ## Layer 1: Capture Trust diff --git a/docs/intro.md b/docs/intro.md index a9f28a1..f5ac221 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -7,7 +7,7 @@ slug: / **Signed at capture. Verified anywhere.** -SignedShot is an open protocol for proving photos and videos haven't been altered since capture—cryptographically, not by guessing. +SignedShot is an open protocol that creates cryptographic evidence that photos and videos haven't been altered since capture—proof, not guessing. ## The Problem @@ -15,7 +15,7 @@ Digital manipulation is easy and getting easier. Anyone can alter an image in se This leads to an erosion of trust in visual media—and no way to prove "I didn't edit this." -SignedShot solves this by embedding cryptographic proof at the moment of capture. +SignedShot solves this by creating verifiable evidence at the moment of capture. ## A Different Approach @@ -25,7 +25,7 @@ SignedShot doesn't detect fakes. It proves authenticity at the moment of capture The result: **"This device captured this content at this time."** -Anyone can verify the proof independently. Open source, no vendor lock-in. +Anyone can verify independently. No account, no platform, no vendor lock-in. ## How It Works: Two Layers