update vale settings

Signed-off-by: Paweł Gronowski <[email protected]>

Author: vvoland

_vale/Docker/Acronyms.yml

@@ -12,6 +12,7 @@ exceptions:
   - AI
   - API
   - ARM
+  - ARP
   - ASP
   - AUFS
   - AWS
@@ -30,6 +31,7 @@ exceptions:
   - CSV
   - CUDA
   - CVE
+  - DAD
   - DCT
   - DEBUG
   - DHCP
@@ -55,6 +57,7 @@ exceptions:
   - GRUB
   - GTK
   - GUI
+  - GUID
   - HEAD
   - HTML
   - HTTP
@@ -113,6 +116,7 @@ exceptions:
   - SCIM
   - SCM
   - SCSS
+  - SCTP
   - SDK
   - SLES
   - SLSA

_vale/config/vocabularies/Docker/accept.txt

@@ -64,6 +64,7 @@ Laradock
 Linux
 LinuxKit
 Logstash
+MAC
 Mac
 Mail(chimp|gun)
 Microsoft
@@ -183,6 +184,8 @@ musl
 nameserver
 namespace
 namespacing
+netfilter
+netlabel
 npm
 osquery
 osxfs

content/manuals/engine/release-notes/28.md

@@ -201,10 +201,10 @@ For a full list of pull requests and changes in this release, refer to the relev
 - The deprecated OCI `prestart` hook is now only used by build containers. For other containers, network interfaces are added to the network namespace after task creation is complete, before the container task is started. [moby/moby#47406](https://github.com/moby/moby/pull/47406)
 - Add a new `gw-priority` option to `docker run`, `docker container create`, and `docker network connect`. This option will be used by the Engine to determine which network provides the default gateway for a container. On `docker run`, this option is only available through the extended `--network` syntax. [docker/cli#5664](https://github.com/docker/cli/pull/5664)
 - Add a new netlabel `com.docker.network.endpoint.ifname` to customize the interface name used when connecting a container to a network. It's supported by all built-in network drivers on Linux. [moby/moby#49155](https://github.com/moby/moby/pull/49155)
-  - When a container is created with multiple networks specified, there's no guarantee on the order networks will be connected to the container. So, if a custom interface name uses the same prefix as the auto-generated names (eg. `eth`), the container might fail to start.
-  - The recommended practice is to use a different prefix (eg. `en0`), or a numerical suffix high enough to never collide (eg. `eth100`).
-  - This label can be specified on `docker network connect` via the `--driver-opt` flag, eg. `docker network connect --driver-opt=com.docker.network.endpoint.ifname=foobar …`.
-  - Or via the long-form `--network` flag on `docker run`, eg. `docker run --network=name=bridge,driver-opt=com.docker.network.endpoint.ifname=foobar …`
+  - When a container is created with multiple networks specified, there's no guarantee on the order networks will be connected to the container. So, if a custom interface name uses the same prefix as the auto-generated names (e.g. `eth`), the container might fail to start.
+  - The recommended practice is to use a different prefix (e.g. `en0`), or a numerical suffix high enough to never collide (e.g. `eth100`).
+  - This label can be specified on `docker network connect` via the `--driver-opt` flag, e.g. `docker network connect --driver-opt=com.docker.network.endpoint.ifname=foobar …`.
+  - Or via the long-form `--network` flag on `docker run`, e.g. `docker run --network=name=bridge,driver-opt=com.docker.network.endpoint.ifname=foobar …`
 - If a custom network driver reports capability `GwAllocChecker` then, before a network is created, it will get a `GwAllocCheckerRequest` with the network's options. The custom driver may then reply that no gateway IP address should be allocated. [moby/moby#49372](https://github.com/moby/moby/pull/49372)
 
 #### Port Publishing in Bridge Networks