From 8c1ca6d90fc066f8a13f8c6dd77be42fdd543554 Mon Sep 17 00:00:00 2001
From: giles knap <gilesknap@gmail.com>
Date: Wed, 4 Dec 2024 16:08:44 +0000
Subject: [PATCH] clarify re UDP

---
 docs/explanations/epics_protocols.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/explanations/epics_protocols.md b/docs/explanations/epics_protocols.md
index 7637b3a4..1d715ceb 100644
--- a/docs/explanations/epics_protocols.md
+++ b/docs/explanations/epics_protocols.md
@@ -50,7 +50,7 @@ Experiments with Channel Access servers running in containers reveal:
 Specification <https://docs.epics-controls.org/en/latest/pv-access/Protocol-Messages.html>.
 
 Experimentation with PV Access servers running in containers reveal:
-- Port Mapping for PVA always fails because PVA servers open a new random port for each circuit and this is not NAT friendly.
+- Port Mapping for PVA using UDP always fails because PVA servers open a new random port for each circuit and this is not NAT friendly.
 - Using EPICS_PVA_NAME_SERVERS always works with Port Mapping
 - But the client and server must both be PVXS
 - To talk to a non PVXS server, a pvagw running in the same container network may be used.