Skip to content

Update overview.md #263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 19, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/about/overview.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
---
rer---
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentional?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no. I'll remove it.

type: docs
category: About Sigstore
description: Documentation for Sigstore
Expand Down Expand Up @@ -42,7 +42,7 @@ Sigstore addresses these problems by helping users move away from a key-based si
The signer ideally forgoes using long-lived keypairs. With “keyless” or “ephemeral key” signing, users verify the artifact using the transparency log for signature verification rather than keys. Sigstore improves on traditional methods of signing to be more convenient and secure:

- **Convenience**: Users can take advantage of convenient tooling, easy container signing, and can even bypass the difficult problem of key management and rotation.
- **Security**: With Sigstore, the artifact is not just signed; it’s signed, verified, and witnessed.
- **Security**: With Sigstore, the artifact is not just signed; it’s signed, associated, and witnessed.

## How Sigstore works

Expand Down