From cde8a5549b859376d15c4efe39c29331ee6ed427 Mon Sep 17 00:00:00 2001
From: tschettervictor <85497460+tschettervictor@users.noreply.github.com>
Date: Sat, 14 Jun 2025 22:10:01 -0600
Subject: [PATCH] Update README.md

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3f7739e7..bfaa8dd3 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,8 @@ Starting with version 1.0.20250714, we are now handling all epairs dynamically,
 the use of both types of VNET jails without issue. We have also selected a naming scheme
 that will allow for consistency across these jail types. The naming scheme is as follows...
 
-`e0a_jailname` and `e0b_jailname` are the default interfaces for every jail. This will allow better management
+`e0a_jailname` and `e0b_jailname` are the default epair interfaces for every jail. The `a` side
+is on the host, while the `b` is in the jail. This will allow better management
 when trying to figure out which jail a given epair is linked to. Due to a limitation in how long
 an interface name can be, Bastille will truncate "jailname" to avoid errors if it is too long. So, `mylongjailname`
 will be `e0a_mylongjxxme` and `e0b_mylongjxxme`. The `xx` part is necessary due to another limitation