diff --git a/integration/network/bridge/nftablesdoc/generated/new-daemon.md b/integration/network/bridge/nftablesdoc/generated/new-daemon.md
index b5137eee68..4b9b6ae05e 100644
--- a/integration/network/bridge/nftablesdoc/generated/new-daemon.md
+++ b/integration/network/bridge/nftablesdoc/generated/new-daemon.md
@@ -124,7 +124,7 @@ The rules are:
   with the same hook._
 - accept packets originating within the network, because inter-container
   communication (ICC) is enabled.
-- drop any other packets, because no there are no containers in the network
+- drop any other packets, because there are no containers in the network
   with published ports. _This means there is no dependency on the filter-FORWARD
   chain's default policy. Even if it is ACCEPT, packets will be dropped unless
   container ports/protocols are published._
diff --git a/integration/network/bridge/nftablesdoc/generated/usernet-portmap.md b/integration/network/bridge/nftablesdoc/generated/usernet-portmap.md
index 604ee99e4b..7a4d383e8c 100644
--- a/integration/network/bridge/nftablesdoc/generated/usernet-portmap.md
+++ b/integration/network/bridge/nftablesdoc/generated/usernet-portmap.md
@@ -9,7 +9,7 @@ Adding a network running a container with a mapped port, equivalent to:
 
 The `ip docker-bridges` table is updated as follows:
 
-        table ip docker-bridges {
+    table ip docker-bridges {
     	map filter-forward-in-jumps {
     		type ifname : verdict
     		elements = { "docker0" : jump filter-forward-in__docker0,