From c4ded15afe73c233e000db2d13cb343b27f63856 Mon Sep 17 00:00:00 2001
From: Jihoon Seo <46767780+jihoon-seo@users.noreply.github.com>
Date: Mon, 8 Mar 2021 14:21:34 +0900
Subject: [PATCH] Fix broken anchor

in content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
---
 .../windows/intro-windows-in-kubernetes.md                    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
index 57f867d0db..3998b48501 100644
--- a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
+++ b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
@@ -237,7 +237,7 @@ Overlay (VXLAN) networks on Windows do not support dual-stack networking today.
 
 Windows is only supported as a worker node in the Kubernetes architecture and component matrix. This means that a Kubernetes cluster must always include Linux master nodes, zero or more Linux worker nodes, and zero or more Windows worker nodes.
 
-#### Compute {compute-limitations}
+#### Compute {#compute-limitations}
 
 ##### Resource management and process isolation
 
@@ -297,7 +297,7 @@ As a result, the following storage functionality is not supported on Windows nod
 * NFS based storage/volume support
 * Expanding the mounted volume (resizefs)
 
-#### Networking {networking-limitations}
+#### Networking {#networking-limitations}
 
 Windows Container Networking differs in some important ways from Linux networking. The [Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture) contains additional details and background.