From e3169bded2f2f65c144d8efb5d5845b739e25599 Mon Sep 17 00:00:00 2001
From: Daniil Yarancev <21169548+Yardanico@users.noreply.github.com>
Date: Fri, 25 Aug 2017 13:59:41 +0300
Subject: [PATCH] Updated Whitespace FAQ (markdown)

---
 Whitespace-FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Whitespace-FAQ.md b/Whitespace-FAQ.md
index 257baed..c519cbe 100644
--- a/Whitespace-FAQ.md
+++ b/Whitespace-FAQ.md
@@ -50,7 +50,7 @@ Either the indentation is wrong, or the program is buggy, because an "else" alwa
 
 ### Tabs vs Spaces
 
-This is a non-issue in Nim, as only spaces are accepted as an indentation character --- a syntax error will be thrown if the compiler detects tabs being used for indentation (though this can be worked around by using a [syntax filter](http://nim-lang.org/filters.html)). However, languages that allow both of them to be mixed are dangerous. Some languages, like python 2 by default (fixed on python 3), tries to convert a tab to a certain number of spaces, and thus an indentation error introduced by mixing tabs and spaces will only be detected as a run-time failure. Other languages, that ignores any type of indentation, will generate code that behaves differently than it looks at first sight when using an editor with different tab-stops configuration. This can hide/introduce bugs, like in the previous C/C++ example. 
+This is a non-issue in Nim, as only spaces are accepted as an indentation character --- a syntax error will be thrown if the compiler detects tabs being used for indentation (though this can be worked around by using a [syntax filter](https://nim-lang.org/docs/filters.html)). However, languages that allow both of them to be mixed are dangerous. Some languages, like python 2 by default (fixed on python 3), tries to convert a tab to a certain number of spaces, and thus an indentation error introduced by mixing tabs and spaces will only be detected as a run-time failure. Other languages, that ignores any type of indentation, will generate code that behaves differently than it looks at first sight when using an editor with different tab-stops configuration. This can hide/introduce bugs, like in the previous C/C++ example. 
 
 ## Deep nesting