diff --git a/content/en/docs/concepts/containers/runtime-class.md b/content/en/docs/concepts/containers/runtime-class.md
index b9815cfccb..d8b025395c 100644
--- a/content/en/docs/concepts/containers/runtime-class.md
+++ b/content/en/docs/concepts/containers/runtime-class.md
@@ -41,7 +41,7 @@ feature gates. The `RuntimeClass` feature gate must be enabled on apiservers _an
 #### 1. Configure the CRI implementation on nodes
 
 The configurations available through RuntimeClass are Container Runtime Interface (CRI)
-implementation dependent. See the corresponding documentation ([below](#cri-documentation)) for your
+implementation dependent. See the corresponding documentation ([below](#cri-configuration)) for your
 CRI implementation for how to configure.
 
 {{< note >}}
diff --git a/content/en/docs/setup/windows/user-guide-windows-nodes.md b/content/en/docs/setup/windows/user-guide-windows-nodes.md
index 454e67084b..ae7d2b3535 100644
--- a/content/en/docs/setup/windows/user-guide-windows-nodes.md
+++ b/content/en/docs/setup/windows/user-guide-windows-nodes.md
@@ -88,9 +88,8 @@ Once you have a Linux-based Kubernetes master node you are ready to choose a net
         }
     ```
 
-    {{< note >}}
-    The VNI must be set to 4096 and port 4789 for Flannel on Linux to interoperate with Flannel on Windows. Support for other VNIs is coming soon. See the VXLAN documentation at https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan for an explanation of these fields.
-    {{< /note >}} 
+    {{< note >}}The VNI must be set to 4096 and port 4789 for Flannel on Linux to interoperate with Flannel on Windows. Support for other VNIs is coming soon. See the [VXLAN documentation](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)
+    for an explanation of these fields.{{< /note >}}
 
 1. In the `net-conf.json` section of your `kube-flannel.yml`, double-check:
     1. The cluster subnet (e.g. "10.244.0.0/16") is set as per your IP plan.