From f73670a94d595b8ba88e5f8f55e2c7b0750fa72c Mon Sep 17 00:00:00 2001 From: Vivian Plasencia Date: Tue, 23 Sep 2025 18:50:54 +0200 Subject: [PATCH] docs: update phrase to make it easier to understand (#562) --- content/articles/zk-kit-cultivating-the-garden-of-progcrypto.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/articles/zk-kit-cultivating-the-garden-of-progcrypto.md b/content/articles/zk-kit-cultivating-the-garden-of-progcrypto.md index c3ab0b3..9b4b268 100644 --- a/content/articles/zk-kit-cultivating-the-garden-of-progcrypto.md +++ b/content/articles/zk-kit-cultivating-the-garden-of-progcrypto.md @@ -16,7 +16,7 @@ ProgCrypto libraries are _especially_ special because they shield developers fro But that is only true when libraries are: - Open-sourced for maximal eye-ball attention and bug detection -- Well-tested and re-(re-(..))-audited +- Well-tested and audited - Carefully designed to avoid accidental mishaps that can result from poorly designed interfaces and leaky data-function encapsulations - Well-documented not only to minimize onboarding overhead on developers but also ensure proper use and understanding of security assumptions