diff --git a/vxlan-and-evpn.adoc b/vxlan-and-evpn.adoc
index ec1bc07..12bcea9 100644
--- a/vxlan-and-evpn.adoc
+++ b/vxlan-and-evpn.adoc
@@ -20,7 +20,7 @@ VXLAN encapsulation add 50bytes overhead, so you need to increase mtu on your ho
 physical interfaces to 1550 at minimum. (or decrease mtu inside your vms to 1450)
 
 For BUM traffic (broadcast / unknown unicast traffic, multicast),
-we have 3 differents vxlan setup modes : multicast, unicast, bgp-evpn
+we have 3 different VXLAN setup modes : multicast, unicast, bgp-evpn
 
 image::images/vxlan-l2-vlanunaware.svg["vxlan l2 bridge vlan unaware",align="center"]
 
diff --git a/vzdump.adoc b/vzdump.adoc
index 3d9c1f9..a2b908d 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -363,7 +363,7 @@ Note that this comes with two caveats:
 This mode of operation is especially useful for large VMs, where only a small
 amount of data is required for initial operation, e.g. web servers - once the OS
 and necessary services have been started, the VM is operational, while the
-background task continues copying seldomly used data.
+background task continues copying seldom used data.
 
 Single File Restore
 ~~~~~~~~~~~~~~~~~~~