diff options
| author | Andy Dulson <andy@dulson.org> | 2019-11-24 20:13:07 -0500 |
|---|---|---|
| committer | Drew DeVault <sir@cmpwn.com> | 2019-11-25 11:57:27 -0500 |
| commit | 88b52b86314f97d0c249edaffb0f0ab8490e0f0b (patch) | |
| tree | a4b4ff205a53ccd1d4ed21db5e3f6cbe825b05ea /tutorials/builds.sr.ht/using-build-secrets.md | |
| parent | bcb466d13c959d1adfa7f6bd8a6948adc31d20be (diff) | |
| download | sr.ht-docs-88b52b86314f97d0c249edaffb0f0ab8490e0f0b.tar.gz | |
Fix a typo in the build secrets tutorial: s/every/ever/
Diffstat (limited to 'tutorials/builds.sr.ht/using-build-secrets.md')
| -rw-r--r-- | tutorials/builds.sr.ht/using-build-secrets.md | 2 |
1 files changed, 1 insertions, 1 deletions
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. --- |