From 8e8c6d3de8dbbe6b9d3b68ff75655d7131ded823 Mon Sep 17 00:00:00 2001
From: krufab <10956489+krufab@users.noreply.github.com>
Date: Fri, 3 Apr 2020 16:13:47 +0200
Subject: [PATCH] Minor update

Updated text according to PR comments
---
 .../administer-cluster/kubeadm/adding-windows-nodes.md   | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md b/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
index 8853d90b0e..10fde87f44 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
@@ -119,9 +119,12 @@ Once you have a Linux-based Kubernetes control-plane node you are ready to choos
     {{< /note >}}
 
     {{< note >}}
-    If you're using a different interface rather than Ethernet (i.e. "Ethernet0 2") on the Windows nodes, you have to modify the line
-    ```wins cli process run --path /k/flannel/setup.exe --args "--mode=overlay --interface=Ethernet"```
-    in the flannel-*.yml file and specify your interface accordingly.
+    If you're using a different interface rather than Ethernet (i.e. "Ethernet0 2") on the Windows nodes, you have to modify the line:
+    
+    ```powershell
+    wins cli process run --path /k/flannel/setup.exe --args "--mode=overlay --interface=Ethernet"
+    ```
+    in the flannel-host-gw.yml or flannel-overlay.yml file and specify your interface accordingly.
     {{< /note >}}
     
     ```bash