missed UDL links

content/docs/udl/comments.md

@@ -137,7 +137,7 @@ Just define Delimiter 2 (any delimiter will do, I'll use this one for demonstrat
 So, that every new line combination is covered.<br>
 "((EOL))" has been introduced just for this reason. It allows users to define Delimiter equivalent of Line comments.
 
-Notice how I wrapped EOL with special **double brace operator**. This operator has a special meaning in UDL 2.1 and it is explained in more detail in [Delimiters section]({{ site.baseurl }}/delimiters/). For this example it is enough to remember that it **expands EOL into an end of line character**.
+Notice how I wrapped EOL with special **double brace operator**. This operator has a special meaning in UDL 2.1 and it is explained in more detail in [Delimiters section](../delimiters/). For this example it is enough to remember that it **expands EOL into an end of line character**.
 
 As you can see, nesting of delimiters that imitate line comments works just as good.
 

content/docs/udl/delimiters.md

@@ -73,7 +73,7 @@ In general, white space is not important when defining keywords, so you can use
 Second thing to understand is grouping of Continue characters.<br>
 C++ line comment (the first group), defines two continue characters, Python line comment defines just one.
 
-By using grouping with operator "(( ))" I was able to keep the logic of indexing and vertical aligning (both explained in [comments section]({{ site.baseurl }}/comments/)) and to make sure that "??/" applies only to C++ line comments.
+By using grouping with operator "(( ))" I was able to keep the logic of indexing and vertical aligning (both explained in [comments section](../comments/)) and to make sure that "??/" applies only to C++ line comments.
 
 ![](../images/delimiters_08.png)
 

content/docs/udl/folding_in_code.md

@@ -6,7 +6,7 @@ slug: folding-in-code
 
 # UDL > Folding in code
 
-Folding in code is quite different in UDL 2.1. Instead of two keyword sets (open and close), now we have three keyword sets (open, middle and close). Also, there are two Folding in code  groups: one for [forward (style1)]({{ site.baseurl }}/introduction/) and one for [backward (style2)]({{ site.baseurl }}/introduction/) search.
+Folding in code is quite different in UDL 2.1. Instead of two keyword sets (open and close), now we have three keyword sets (open, middle and close). Also, there are two Folding in code  groups: one for [forward (style1)](../introduction/) and one for [backward (style2)](../introduction/) search.
 
 ## Example 1
 
@@ -23,7 +23,7 @@ As you can see both Folding 1 and Folding 2 create folding points, but they work
 
 ![](../images/folding_in_code_02.png)
 
-Note: forward and backward search concept is explained in more detail in [Introduction]({{ site.baseurl }}/introduction/) page.<br>
+Note: forward and backward search concept is explained in more detail in the [UDL Parser](../introduction/) page.<br>
 You should read that part if you haven't already.
 
 ## Example 2

content/docs/udl/operators.md

@@ -6,7 +6,7 @@ title: UDL > Operators
 # UDL > Operators
 
 This section gives short explanation of operator options.<br>
-For detailed discussion about "forward" and "backward" search, please read section [Introduction]({{ site.baseurl }}/introduction/).
+For detailed discussion about "forward" and "backward" search, please read section on the [UDL Parser](../introduction/).
 
 ![Operators dialog](../images/operators_01.png)