1 files changed, 1 insertions, 1 deletions

diff --git a/documentation/content/en/articles/filtering-bridges/_index.adoc b/documentation/content/en/articles/filtering-bridges/_index.adoc
index ae744fb88d..5452add1bc 100644
--- a/documentation/content/en/articles/filtering-bridges/_index.adoc
+++ b/documentation/content/en/articles/filtering-bridges/_index.adoc
@@ -176,7 +176,7 @@ Sophisticated things like `divert`, `forward` or `reject` are not available.
 Such options can still be used, but only on traffic to or from the bridge machine itself (if it has an IP address).
 
 New in FreeBSD 4.0, is the concept of stateful filtering.
-This is a big improvement for UDP traffic, which typically is a request going out, followed shortly thereafter by a response with the exact same set of IP addresses and port numbers (but with source and destination reversed, of course).
+This is a big improvement for UDP traffic, which typically is a request going out, followed shortly thereafter by a response with the same set of IP addresses and port numbers (but with source and destination reversed, of course).
 For firewalls that have no statekeeping, there is almost no way to deal with this sort of traffic as a single session.
 But with a firewall that can "remember" an outgoing UDP packet and, for the next few minutes, allow a response, handling UDP services is trivial.
 The following example shows how to do it.