Skip to content
This repository was archived by the owner on Jan 15, 2025. It is now read-only.

Commit 79e0201

Browse files
committed
Fixed up the some wording in the README.md doc.
1 parent 4efc477 commit 79e0201

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

README.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -143,10 +143,11 @@ specified to make the jump conditional. For example:
143143
The rules specified under the `rule` attribute will only be evaluate for packets for which
144144
the rule in `chain_condition` holds.
145145

146-
Sometimes we might want to define a chain that can be only jumped from another chain we define.
147-
By default, all `simple_iptables_rule` chains will be jumped from one of the directions
148-
chains. To prevent jumping to the chain from the direction chains, we can set the direction attribute
149-
to the symbol `:none`. For example, consider a chain used to log
146+
Sometimes we might want to define a chain where we only want to jump from another chain we define.
147+
By default, an automatic jump will be made to chains defined using the `simple_iptables_rule` resource
148+
from the chain specified using the `direction` attribute of the resource. To prevent jumping to the
149+
chain from the direction chains, we can set the direction attribute to the symbol `:none`.
150+
For example, consider a chain used to log
150151

151152
simple_iptables_rule "logging_drop" do
152153
direction :none
@@ -155,8 +156,8 @@ to the symbol `:none`. For example, consider a chain used to log
155156
jump false
156157
end
157158

158-
We can then jump to this chain from other simple_iptables_rule chains, but a jump to this
159-
chain won't be added to a direction chain's set of rules.
159+
We can then jump to this chain from other simple_iptables_rule chains, but an automatic jump to
160+
this chain won't be added.
160161

161162

162163
`simple_iptables_policy` Resource

0 commit comments

Comments
 (0)