Update Help and release notes

1 files changed, 5 insertions, 1 deletions

diff --git a/res/about/help.gmi b/res/about/help.gmi
index 0256fed2..12da980b 100644
--- a/res/about/help.gmi
+++ b/res/about/help.gmi
@@ -218,7 +218,11 @@ As the sidebar is not keyboard-navigable, note that identities can also be acces
 
 ### 1.6.3 Importing existing certificates
 
-At launch, Lagrange looks through its "idents" directory to see if any new certificates have been copied there. (See "Runtime files" below for the location.) The file format must be PEM. Both a certificate (.crt) and its private key (.key) must be found in "idents" and they must have matching file names. For example:
+To import an existing X.509 certificate as an identity, press ${SHIFT+}${CTRL+}I or click on 👤 and select "Import..." (macOS: Identities menu → Import...).
+
+When the Import Identity dialog opens, it checks the currently open page for any certificates and private keys in PEM format. If found, these are automatically loaded in. You can also press ${CTRL+}V to paste PEM-formatted certificates and/or private keys, or drag-and-drop a PEM-formatted .crt/.key files on the Lagrange window while the dialog is open.
+
+Alternatively, you can manually copy the certificate files so Lagrange can find them. At launch, Lagrange looks through its "idents" directory to see if any new certificates have been copied there. (See "Runtime files" below for the location; it is platform-specific) The file format must be PEM. Both a certificate (.crt) and its private key (.key) must be found in "idents" and they must have matching file names. For example:
 * mycert.crt
 * mycert.key
 Lagrange will add a note to the imported identities to mark them as "Imported".