From 6e665560d179e295f33ae3cd05a62c4563d56060 Mon Sep 17 00:00:00 2001 From: Gris Ge Date: Tue, 18 Jun 2024 21:38:21 +0800 Subject: [PATCH] vlan/vxlan: Fix typo Signed-off-by: Gris Ge --- devel/yaml_api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devel/yaml_api.md b/devel/yaml_api.md index 4d2d1e3..f1ca00f 100644 --- a/devel/yaml_api.md +++ b/devel/yaml_api.md @@ -951,7 +951,7 @@ The `vlan` sections contains two parameters: With nmstate 2.2.1+, when using Nmstate with NetworkManager backend, nmstate can creating VLAN over unmanaged interface, hence if you never mention VLAN -parent in `interfafaces` section of desired state, nmstate will not convert +parent in `interfaces` section of desired state, nmstate will not convert VxLAN parent interface from unmanaged to managed. For `generate configuration(gc)` mode, unmentioned VLAN parent will not @@ -992,7 +992,7 @@ Currently, we only support VxLAN based on IEEE 802.1Q protocol. With nmstate 2.2.1+, when using Nmstate with NetworkManager backend, nmstate can creating VxLAN over unmanaged interface, if you never mention VxLAN parent -in `interfafaces` section of desired state, nmstate will not convert VxLAN +in `interfaces` section of desired state, nmstate will not convert VxLAN parent interface from unmanaged to managed. For `generate configuration(gc)` mode, unmentioned VxLAN parent will not