Merge branch v3.2 into master

docs/content/routing/providers/kubernetes-gateway.md

@@ -750,4 +750,4 @@ spec:
 [...]
 ```
 
-{!traefik-for-business-applications.md!}
+{!traefik-for-business-applications.md!}

docs/content/routing/providers/swarm.md

@@ -680,10 +680,10 @@ You can tell Traefik to consider (or not) the container by setting `traefik.enab
 
 This option overrides the value of `exposedByDefault`.
 
-#### `traefik.docker.network`
+#### `traefik.swarm.network`
 
 ```yaml
-- "traefik.docker.network=mynetwork"
+- "traefik.swarm.network=mynetwork"
 ```
 
 Overrides the default docker network to use for connections to the container.
@@ -691,13 +691,10 @@ Overrides the default docker network to use for connections to the container.
 If a container is linked to several networks, be sure to set the proper network name (you can check this with `docker inspect <container_id>`),
 otherwise it will randomly pick one (depending on how docker is returning them).
 
-!!! warning
-    The Docker Swarm provider still uses the same per-container mechanism as the Docker provider, so therefore the label still uses the `docker` keyword intentionally.
-
 !!! warning
     When deploying a stack from a compose file `stack`, the networks defined are prefixed with `stack`.
 
-#### `traefik.docker.lbswarm`
+#### `traefik.swarm.lbswarm`
 
 ```yaml
 - "traefik.docker.lbswarm=true"
@@ -707,6 +704,3 @@ Enables Swarm's inbuilt load balancer (only relevant in Swarm Mode).
 
 If you enable this option, Traefik will use the virtual IP provided by docker swarm instead of the containers IPs.
 Which means that Traefik will not perform any kind of load balancing and will delegate this task to swarm.
-
-!!! warning
-    The Docker Swarm provider still uses the same per-container mechanism as the Docker provider, so therefore the label still uses the `docker` keyword intentionally.