From 231761146eee39db92524efd464f153f21f938bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20H=C3=B6xtermann?= Date: Fri, 10 Mar 2023 18:07:20 +0100 Subject: [PATCH] Fix typos "=yet" -> "=yes" --- doc/design/encryption.mdwn | 2 +- doc/tips/publishing_your_files_to_the_public/old_method.mdwn | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/design/encryption.mdwn b/doc/design/encryption.mdwn index a30e7f334d..1c64566c15 100644 --- a/doc/design/encryption.mdwn +++ b/doc/design/encryption.mdwn @@ -95,7 +95,7 @@ the cipher can get access to whatever other credentials are needed to use the special remote. For example, the S3 special remote does this if configured with -embedcreds=yet. +embedcreds=yes. ## risks diff --git a/doc/tips/publishing_your_files_to_the_public/old_method.mdwn b/doc/tips/publishing_your_files_to_the_public/old_method.mdwn index 5409dda0d9..fe304cda24 100644 --- a/doc/tips/publishing_your_files_to_the_public/old_method.mdwn +++ b/doc/tips/publishing_your_files_to_the_public/old_method.mdwn @@ -85,4 +85,4 @@ for a bucket, in the AWS dashboard. } This should not be necessary if using a new enough version -of git-annex, which can instead be configured with public=yet. +of git-annex, which can instead be configured with public=yes.