diff --git a/docker-for-windows/faqs.md b/docker-for-windows/faqs.md
index 5b6d155797..882f6e4ea9 100644
--- a/docker-for-windows/faqs.md
+++ b/docker-for-windows/faqs.md
@@ -130,11 +130,14 @@ does not work](troubleshoot.md#inotify-on-shared-drives-does-not-work) in
 ### Are symlinks supported?
 
 Docker for Windows supports symbolic links (symlinks) created within containers.
-Symbolic link (symlinks) created within containers and across containers will
-resolve.
-Symlinks created outside of containers (e.g., on the host) will not work in  containers.
+Symlinks will resolve within and across containers.
+Symlinks created elsewhere (e.g., on the host) will not work.
 
-To learn more about the reasons for this limitation, see this issue on GitHub: [Symlinks don't work as expected](https://github.com/docker/for-win/issues/109#issuecomment-251307391).
+To learn more about the reasons for this limitation, see the following discussions:
+
+* GitHub issue: [Symlinks don't work as expected](https://github.com/docker/for-win/issues/109#issuecomment-251307391)
+
+* Docker for Windows forums topic: [Symlinks on shared volumes not supported](https://forums.docker.com/t/symlinks-on-shared-volumes-not-supported/9288)
 
 ### How do I add custom CA certificates?
 
diff --git a/docker-for-windows/troubleshoot.md b/docker-for-windows/troubleshoot.md
index 69d56ac99c..c16ce8ef7e 100644
--- a/docker-for-windows/troubleshoot.md
+++ b/docker-for-windows/troubleshoot.md
@@ -89,6 +89,10 @@ Here is an example of how to de-bug this problem, given a scenario where you sha
 
 See also, the related issue on GitHub, [Mounted volumes are empty in the container](https://github.com/docker/for-win/issues/25).
 
+### Understand symlinks limitations
+
+Symlinks will work within and across containers. However, symlinks created outside of containers (for example, on the host) will not work. To learn more, see [Are symlinks supported?](faqs.md#are-symlinks-supported) in the FAQs.
+
 ### Avoid unexpected syntax errors, use Unix style line endings for files in containers
 
 Any file destined to run inside a container must use Unix style `\n` line endings. This includes files referenced at the command line for builds and in RUN commands in Docker files.