From 88b52b86314f97d0c249edaffb0f0ab8490e0f0b Mon Sep 17 00:00:00 2001 From: Andy Dulson Date: Sun, 24 Nov 2019 20:13:07 -0500 Subject: Fix a typo in the build secrets tutorial: s/every/ever/ --- tutorials/builds.sr.ht/using-build-secrets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tutorials/builds.sr.ht') diff --git a/tutorials/builds.sr.ht/using-build-secrets.md b/tutorials/builds.sr.ht/using-build-secrets.md index 87cbee6..bcd965e 100644 --- a/tutorials/builds.sr.ht/using-build-secrets.md +++ b/tutorials/builds.sr.ht/using-build-secrets.md @@ -94,7 +94,7 @@ when submitting build manifests from GitHub pull requests. However, some degree of responsibility lies with you for keeping your secrets secure. Avoid writing build manifests that would print your secrets to the logs, -particularly if using file secrets. If a secret is every leaked in this manner, +particularly if using file secrets. If a secret is ever leaked in this manner, you should consider that secret compromised - revoke it and generate a new one. --- -- cgit