From 460a03089bdf4c4263ff37c2b38f1c36e37b16e1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Johannes=20M=C3=BCnch?= <git@washiza.eu>
Date: Wed, 8 Nov 2023 19:29:31 +0100
Subject: [PATCH] Fix mixed-up usage of in- and egress for policies

In the man-pages for the firewalld.policies the usage of "ingress" and
"egress" are mixed-up, so "ingress" is mentioned for the "OUTPUT" chain
and "egress" is mentioned for the "INPUT" chain.
This commit fixes this so "ingress" is mentioned for the "INPUT" chain
and "egress" is mentioned for the "OUTPUT" chain.
---
 documentation/man-pages/firewalld.policies.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/man-pages/firewalld.policies.html b/documentation/man-pages/firewalld.policies.html
index 327dc15..b81f54c 100644
--- a/documentation/man-pages/firewalld.policies.html
+++ b/documentation/man-pages/firewalld.policies.html
@@ -46,10 +46,10 @@
                         netfilter (iptables/nftables) chains INPUT and OUTPUT.
                     </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
                                 If used in the egress zones list it will apply to
-                                traffic on the INPUT chain.
+                                traffic on the OUTPUT chain.
                             </p></li><li class="listitem"><p>
                                 If used in the ingress zones list it will apply
-                                to traffic on the OUTPUT chain.
+                                to traffic on the INPUT chain.
                             </p></li></ul></div></li><li class="listitem"><p>ANY</p><p>
                         This symbolic zone behaves like a wildcard for the
                         ingress and egress zones. With the exception that it