From ba62d2a98d6ed8aaa2e9489c504785ff8ff5911a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= Date: Mon, 29 Mar 2021 16:48:34 +0200 Subject: [PATCH] fix(blog): typos in "Policy Objects: Introduction" --- blog/_posts/2020-09-02-policy-objects-introduction.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/blog/_posts/2020-09-02-policy-objects-introduction.md b/blog/_posts/2020-09-02-policy-objects-introduction.md index ff085a8..ab78d87 100644 --- a/blog/_posts/2020-09-02-policy-objects-introduction.md +++ b/blog/_posts/2020-09-02-policy-objects-introduction.md @@ -74,7 +74,7 @@ direction of traffic. This diagram shows `policyA` that applies to traffic flowing from the `public` zone to the `libvirt` zone. `policyB` applies to traffic flowing from the -`internal` zone to the `public` zone. +`libvirt` zone to the `public` zone. The configuration changes necessary to result in the diagram above are: @@ -96,7 +96,7 @@ Policies must be created by the user. ``` ### Ingress and Egress Zones -As shown in the diagram above policies exists between zones. This means a set +As shown in the diagram above policies exist between zones. This means a set of ingress and egress zones must be defined before the policy becomes active. In this context an ingress zone is the zone from which the packet originated. The egress zone is the zone to which the packet is destined. @@ -159,8 +159,8 @@ originating from or destined to the host running firewalld. `ANY` is used to apply a policy to all current and future zones. `ANY` is effectively a wildcard for all zones. -This example, creates a policy that applies to traffic originating from the -host running firewalld and is destined to any zone. Or said differently +This example creates a policy that applies to traffic originating from the +host running firewalld and destined to any zone. Or said differently traffic in the `OUTPUT` chain. ```