Update docs/upgrade/v1-5-x-to-v1-6-0.md

Co-authored-by: Jillian Maroket <[email protected]>
Signed-off-by: Renuka Devi Rajendran <[email protected]>

Author: rrajendran17

docs/upgrade/v1-5-x-to-v1-6-0.md

@@ -230,17 +230,5 @@ stages:
 ```
 Users expect to create an additional vlan sub interface on mgmt interface `mgmt-br.2113` and assign IPv4 address and use it for L3 connectivity in addition to the primary `mgmt-br.2021` interface after upgrade to v1.6.x.
 The additional vlan sub interface is created, but `mgmt-br` bridge and `mgmt-bo` will no longer be part of vlan `2113` as after reboot only the primary `vlan-id` will be assigned to the `mgmt-br` bridge and `mgmt-bo` using `/oem/90_custom.yaml`.Starting from v1.6.0, only primary vlan will be added to `mgmt-br` bridge and `mgmt-bo` instead of all 2-4094 vlans.Due to this communication using secondary vlans on mgmt interface is affected.
-Users can check this info using `bridge vlan show` command on the host.
-
-Starting from v1.6.0,Users have to explicitly add the secondary vlans required to the `mgmt-br` bridge and `mgmt-bo` using the following and repeat below for every secondary `vlan-id` or vlan range the user requires.
-
-Add the following under contents of /etc/wicked/scripts/setup_bond.sh in /oem/90_custom.yaml
-```
-bridge vlan add vid <vlan-id> dev $INTERFACE
-```
-
-Add the following under contents of /etc/wicked/scripts/setup_bridge.sh in /oem/90_custom.yaml
-```
-bridge vlan add vid <vlan-id> dev $INTERFACE self
-bridge vlan add vid <vlan-id> dev mgmt-bo
+To mitigate the effects of this change, you must perform the workaround described in the previous section. This involves identifying secondary VLAN interfaces and then adding the necessary ones to the `mgmt-br` bridge and the `mgmt-bo` interface.
 ```