diff --git a/FAQ.d/FAQ.Massive.txt b/FAQ.d/FAQ.Massive.txt
index a227d32..fdc33f8 100644
--- a/FAQ.d/FAQ.Massive.txt
+++ b/FAQ.d/FAQ.Massive.txt
@@ -178,7 +178,7 @@ Here comes some measurements.
      dstat -n -N eth0 6  # Linux only (in 2018)
 
    Another excellent tool to measure the network trafic is iftop.
-   The following command will monitor imap and imaps connexions
+   The following command will monitor imap and imaps connections
    on interfce eth0, only them, and sum them up:
    
      iftop -i eth0 -f 'port imap or port imaps' -B # Linux
@@ -250,9 +250,9 @@ Possible bottlenecks:
 
 - Bandwidth. 
   Usually available bandwidth is NOT a bottleneck.
-  Meanwhile, it can be a bottleneck on small Internet connexions.
+  Meanwhile, it can be a bottleneck on small Internet connections.
   Imapsync downloads messages from host1 and upload messages to host2,
-  consider this in case the connexion are asymmetric.
+  consider this in case the connections are asymmetric.
   
 - I/O on disks. 
   I/O are a classical bottleneck, almost always forgotten.
diff --git a/FAQ.d/FAQ.Yahoo.txt b/FAQ.d/FAQ.Yahoo.txt
index ffd44bf..493c4e4 100644
--- a/FAQ.d/FAQ.Yahoo.txt
+++ b/FAQ.d/FAQ.Yahoo.txt
@@ -41,7 +41,7 @@ Yahoo IMAP does not honor well the SEARCH imap command (Dec 2017).
 So don't use the --search option.
 You can use --minage or/and --maxage but then add also --noabletosearch
 
-Yahoo bandwidth per connexion is relatively low, 50 KiB/s to 500 KiB/s max, usually 100 KiB/s.
+Yahoo bandwidth per connection is relatively low, 50 KiB/s to 500 KiB/s max, usually 100 KiB/s.
 Consider using --useuid to speed up large accounts.