diff --git a/content/blog/mail_server_alpine_postfix_dovecot_tutorial/index.md b/content/blog/mail_server_alpine_postfix_dovecot_tutorial/index.md
index 8aa1b5a..5c4e719 100644
--- a/content/blog/mail_server_alpine_postfix_dovecot_tutorial/index.md
+++ b/content/blog/mail_server_alpine_postfix_dovecot_tutorial/index.md
@@ -748,7 +748,7 @@ Dovecot has a [mail\_crypt plugin](https://doc.dovecot.org/main/core/plugins/mai
 client with your server with no changes, and no difference in user experience. Mail is decrypted on the server and sent
 over IMAP.
 
-We will optionally set up global key mail\_crypt encryption. This does not provider protection against an attacker with
+We will optionally set up global key mail\_crypt encryption. This does not provide protection against an attacker with
 root access, or full disk access (which is basically root access), however it can protect against other processes
 reading our mail since they can't read the private key.
 
@@ -798,6 +798,8 @@ Restart Dovecot for the changes to take effect:
 
     # rc-service dovecot restart
 
+Note that this will not make any difference to reading unencrypted email that was previously stored in your mailbox.
+
 # Use a local email client
 
 You are now ready to try logging in on a local email client such as Thunderbird, Evolution, Geary, KMail, etc.
@@ -1771,6 +1773,9 @@ etc. The `sieve_after` option also exists, and works the same way.
 This is not the same as `sieve_default`, which is *overridden* by user sieve scripts and only executes when a user has
 no sieve script.
 
+You can review [this documentation](https://doc.dovecot.org/main/core/plugins/sieve.html) for a full list of Pigeonhole
+options.
+
 ## ManageSieve
 
 Users can configure their own user sieve scripts using a protocol called ManageSieve. Like how IMAP allows users to