link issues in README

diff --git a/README.md b/README.md
index 0b620f53ff5f962f39b9007f3b30aba622bf906b..282b20d75b4aa45458d74ab62a9fd81a5f36d3b6 100644 (file)
--- a/README.md
+++ b/README.md
@@ -67,15 +67,15 @@ No (it shouldn't be, unless you are watching where it was moved to).
 
 **When I watch a directory, are all subdirectories watched as well?**
 
-No, you must add watches for any directory you want to watch (a recursive watcher is in the works #56).
+No, you must add watches for any directory you want to watch (a recursive watcher is in the works [#56][]).
 
 **Do I have to watch the Error and Event channels in a separate goroutine?**
 
-As of now, yes. Looking into making this single-thread friendly (see #7)
+As of now, yes. Looking into making this single-thread friendly (see [#7][])
 
 **Why am I receiving multiple events for the same file on OS X?**
 
-Spotlight indexing on OS X can result in multiple events (see #62). A temporary workaround is to add your folder(s) to the *Spotlight Privacy settings* until we have a native FSEvents implementation (see #54).
+Spotlight indexing on OS X can result in multiple events (see [#62][]). A temporary workaround is to add your folder(s) to the *Spotlight Privacy settings* until we have a native FSEvents implementation (see [#54][]).
 
 **How many files can be watched at once?**
 
@@ -83,3 +83,10 @@ There are OS-specific limits as to how many watches can be created:
 * Linux: /proc/sys/fs/inotify/max_user_watches contains the limit,
 reaching this limit results in a "no space left on device" error.
 * BSD / OSX: sysctl variables "kern.maxfiles" and "kern.maxfilesperproc", reaching these limits results in a "too many open files" error.
+
+
+[#62]: https://github.com/howeyc/fsnotify/issues/62
+[#56]: https://github.com/howeyc/fsnotify/issues/56
+[#54]: https://github.com/howeyc/fsnotify/issues/54
+[#7]: https://github.com/howeyc/fsnotify/issues/7
+