From 5c3d3dd8949d4eba0cbf2fffecc3c71fc2b538a4 Mon Sep 17 00:00:00 2001
From: kaitlincarter-hc <43049322+kaitlincarter-hc@users.noreply.github.com>
Date: Wed, 17 Apr 2019 16:12:30 -0500
Subject: [PATCH] Updating network connectivity section based on feedback from
 Pavani. (#5612)

---
 website/source/docs/guides/deployment.html.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/source/docs/guides/deployment.html.md b/website/source/docs/guides/deployment.html.md
index 9a44b75e44..d6d124945e 100644
--- a/website/source/docs/guides/deployment.html.md
+++ b/website/source/docs/guides/deployment.html.md
@@ -99,7 +99,7 @@ The agent's status directly affects the service discovery results. If an agent i
 
 In addition, the agent also periodically performs a full state sync over TCP which gossips each agent’s understanding of the member list around it (node names, IP addresses, and health status). These operations are expensive relative to the standard gossip protocol mentioned above and are synced at a rate determined by cluster size to keep overhead low. It's typically between 30 seconds and 5 minutes. For more details, refer to [Serf Gossip docs](https://www.serf.io/docs/internals/gossip.html)
 
-In a larger network that spans L2 segments, traffic typically traverses through a firewall and/or a router. ACL or firewall rules must be updated to allow the following ports:
+In a larger network that spans L3 segments, traffic typically traverses through a firewall and/or a router. ACL or firewall rules must be updated to allow the following ports:
 
 | Name          | Port | Flag | Description |
 |---------------|------|------|-------------|