fix: add an explicit example about publishing the pubkey when expiring

1 files changed, 13 insertions, 1 deletions

diff --git a/README.md b/README.md
index cf92f75..4b9a7f4 100644
--- a/README.md
+++ b/README.md
@@ -2026,7 +2026,7 @@ Key is valid for? (0)
 ```
 Follow these prompts to set a new expiration date, then `save` to save your changes.
 
-Next, export the public key:
+Next, [export the public key](#export-public-keys):
 
 ```console
 $ gpg --armor --export $KEYID > gpg-$KEYID-$(date +%F).asc
@@ -2038,6 +2038,18 @@ Transfer that public key to the computer from which you use your GPG key, and th
 $ gpg --import gpg-0x*.asc
 ```
 
+Alternatively, use a public key server (it will update the key if already on the server):
+
+```console
+$ gpg --send-key $KEYID
+```console
+
+and import the newly  on any computer where you wish to use it (it will update the key if previously imported):
+
+```console
+$ gpg --recv $KEYID
+```
+
 This will extend the validity of your GPG key and will allow you to use it for SSH authorization.  Note that you do _not_ need to update the SSH public key located on remote servers.
 
 ## Rotating keys