Fix up minor typo.

dskatz · Jun 30, 2017 · 0c492ab · 0c492ab
1 parent 37fadb8
commit 0c492ab
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/master/usage/troubleshooting/faq.md b/master/usage/troubleshooting/faq.md
@@ -34,7 +34,7 @@ In a Calico network, each host acts as a gateway router for the
 workloads that it hosts.  In container deployments, Calico uses
 169.254.1.1 as the address for the Calico router.  By using a
 link-local address, Calico saves precious IP addresses and avoids
-burdoning the user with configuring a suitable address.
+burdening the user with configuring a suitable address.
 
 While the routing table may look a little odd to someone who is used to
 configuring  LAN networking, using explicit routes rather than

diff --git a/v1.6/usage/troubleshooting/faq.md b/v1.6/usage/troubleshooting/faq.md
@@ -29,7 +29,7 @@ In a Calico network, each host acts as a gateway router for the
 workloads that it hosts.  In container deployments, Calico uses 
 169.254.1.1 as the address for the Calico router.  By using a 
 link-local address, Calico saves precious IP addresses and avoids 
-burdoning the user with configuring a suitable address.
+burdening the user with configuring a suitable address.
 
 While the routing table may look a little odd to someone who is used to 
 configuring  LAN networking, using explicit routes rather than 

diff --git a/v2.0/usage/troubleshooting/faq.md b/v2.0/usage/troubleshooting/faq.md
@@ -34,7 +34,7 @@ In a Calico network, each host acts as a gateway router for the
 workloads that it hosts.  In container deployments, Calico uses
 169.254.1.1 as the address for the Calico router.  By using a
 link-local address, Calico saves precious IP addresses and avoids
-burdoning the user with configuring a suitable address.
+burdening the user with configuring a suitable address.
 
 While the routing table may look a little odd to someone who is used to
 configuring  LAN networking, using explicit routes rather than

diff --git a/v2.1/usage/troubleshooting/faq.md b/v2.1/usage/troubleshooting/faq.md
@@ -34,7 +34,7 @@ In a Calico network, each host acts as a gateway router for the
 workloads that it hosts.  In container deployments, Calico uses
 169.254.1.1 as the address for the Calico router.  By using a
 link-local address, Calico saves precious IP addresses and avoids
-burdoning the user with configuring a suitable address.
+burdening the user with configuring a suitable address.
 
 While the routing table may look a little odd to someone who is used to
 configuring  LAN networking, using explicit routes rather than

diff --git a/v2.2/usage/troubleshooting/faq.md b/v2.2/usage/troubleshooting/faq.md
@@ -34,7 +34,7 @@ In a Calico network, each host acts as a gateway router for the
 workloads that it hosts.  In container deployments, Calico uses
 169.254.1.1 as the address for the Calico router.  By using a
 link-local address, Calico saves precious IP addresses and avoids
-burdoning the user with configuring a suitable address.
+burdening the user with configuring a suitable address.
 
 While the routing table may look a little odd to someone who is used to
 configuring  LAN networking, using explicit routes rather than

diff --git a/v2.3/usage/troubleshooting/faq.md b/v2.3/usage/troubleshooting/faq.md
@@ -35,7 +35,7 @@ In a Calico network, each host acts as a gateway router for the
 workloads that it hosts.  In container deployments, Calico uses
 169.254.1.1 as the address for the Calico router.  By using a
 link-local address, Calico saves precious IP addresses and avoids
-burdoning the user with configuring a suitable address.
+burdening the user with configuring a suitable address.
 
 While the routing table may look a little odd to someone who is used to
 configuring  LAN networking, using explicit routes rather than