From 152413b8bd720c3e813db23b1173832e42d0e2f0 Mon Sep 17 00:00:00 2001
From: Dan <5867710+danial23@users.noreply.github.com>
Date: Mon, 3 Mar 2025 01:16:23 -0500
Subject: [PATCH] Update encrypt-backups.md (#550)

Updated docs to reflect changes made in #530
---
 docs/how-tos/encrypt-backups.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/how-tos/encrypt-backups.md b/docs/how-tos/encrypt-backups.md
index 647b941..baa60cc 100644
--- a/docs/how-tos/encrypt-backups.md
+++ b/docs/how-tos/encrypt-backups.md
@@ -21,12 +21,10 @@ gpg -o backup.tar.gz -d backup.tar.gz.gpg
 
 ## Using age encryption
 
-{: .note }
-Even though the `age` CLI tools supports encryption using SSH keys, this is not supported by this tool.
-`AGE_PUBLIC_KEYS` currently expects `age` keys to be given.
-
 age allows backups to be encrypted with either a symmetric key (password) or a public key. One of those options are available for use.
 
 Given `AGE_PASSPHRASE` being provided, the backup archive will be encrypted with the passphrase and saved as a `.age` file instead. Refer to age documentation for how to properly decrypt.
 
 Given `AGE_PUBLIC_KEYS` being provided (allowing multiple by separating each public key with `,`), the backup archive will be encrypted with the provided public keys. It will also result in the archive being saved as a `.age` file.
+
+You can use SSH keys in addition to `age` keys for encryption; `AGE_PUBLIC_KEYS` accepts both.