Even though this is clear from the context, it is nice to actually be
grammatically correct.

Fixes: 0f22ad45f47c ("Documentation: networking: switchdev: clarify device 
driver behavior")
Reported-by: Ido Schimmel <ido...@nvidia.com>
Signed-off-by: Vladimir Oltean <vladimir.olt...@nxp.com>
---
 Documentation/networking/switchdev.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/networking/switchdev.rst 
b/Documentation/networking/switchdev.rst
index aa78102c9fab..f1f4e6a85a29 100644
--- a/Documentation/networking/switchdev.rst
+++ b/Documentation/networking/switchdev.rst
@@ -523,7 +523,7 @@ as untagged packets, since the bridge device does not allow 
the manipulation of
 VID 0 in its database.
 
 When the bridge has VLAN filtering enabled and a PVID is not configured on the
-ingress port, untagged 802.1p tagged packets must be dropped. When the bridge
+ingress port, untagged and 802.1p tagged packets must be dropped. When the 
bridge
 has VLAN filtering enabled and a PVID exists on the ingress port, untagged and
 priority-tagged packets must be accepted and forwarded according to the
 bridge's port membership of the PVID VLAN. When the bridge has VLAN filtering
-- 
2.25.1

Reply via email to