dead link fixes

docs/cookbooks/3.2.x/core.md

@@ -2417,9 +2417,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/3.3.x/core.md

@@ -2651,9 +2651,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/4.0.x/core.md

@@ -2709,9 +2709,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/4.0.x/core/cfg.md

@@ -42,7 +42,7 @@ It closely resembles the PHP style, ***except*** you **can not use**
 double-slash ( ⁄ ⁄ ) for line comments. Only the hash (#) may be used
 for line comments.  
 
-It can be confusing seeing the C-Style Control Directives ([explained later](cfg#c-style_control_directives)) that begin with a hash-bang (#!)
+It can be confusing seeing the C-Style Control Directives ([explained later](cfg.md#c-style-control-directives)) that begin with a hash-bang (#!)
 mixed with line comments beginning with a hash (#).
 
 | Examples:                                                                           |
@@ -145,7 +145,7 @@ These name/value pairs are normally delimited by an equal sign.
 
 \<fc #FF0000>There are a couple situations where the value needs to be
 enclosed in quotes.\</fc>  
-Check the [core parameters](..//core#core_parameters) for the required
+Check the [core parameters](..//core.md#core_parameters) for the required
 syntax.
 
 | Examples:                |

docs/cookbooks/4.1.x/core.md

@@ -2671,9 +2671,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In boolean expressions:
 

docs/cookbooks/4.2.x/core.md

@@ -2651,9 +2651,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/4.3.x/core.md

@@ -2678,9 +2678,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/4.4.x/core.md

@@ -2916,9 +2916,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.0.x/core.md

@@ -3002,9 +3002,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.1.x/core.md

@@ -3085,9 +3085,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.2.x/core.md

@@ -1016,7 +1016,7 @@ flags
 
 (\*) The named flags feature was propagated from the source code merge
 back in 2008 and is not extensively tested. The recommended way of
-defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+defining flags is using [#!define](core.md#define) (which
 is also valid for branch/script flags):
 
 ``` c
@@ -3213,9 +3213,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.3.x/core.md

@@ -1039,7 +1039,7 @@ flags
 
 (\*) The named flags feature was propagated from the source code merge
 back in 2008 and is not extensively tested. The recommended way of
-defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+defining flags is using [#!define](core.md#define) (which
 is also valid for branch/script flags):
 
 ``` c
@@ -3339,9 +3339,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.4.x/core.md

@@ -1064,7 +1064,7 @@ flags
 
 (\*) The named flags feature was propagated from the source code merge
 back in 2008 and is not extensively tested. The recommended way of
-defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+defining flags is using [#!define](core.md#define) (which
 is also valid for branch/script flags):
 
 ``` c
@@ -3410,9 +3410,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.5.x/core.md

@@ -1138,7 +1138,7 @@ flags
 
 (\*) The named flags feature was propagated from the source code merge
 back in 2008 and is not extensively tested. The recommended way of
-defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+defining flags is using [#!define](core.md#define) (which
 is also valid for branch/script flags):
 
 ``` c
@@ -3613,9 +3613,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[$retcode](devel#retcode) or $? variable.
+[$retcode](#retcode) or $? variable.
 
-return(0) is same as [exit()](devel#exit);
+return(0) is same as [exit()](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.6.x/core.md

@@ -1180,7 +1180,7 @@ flags
 
 (\*) The named flags feature was propagated from the source code merge
 back in 2008 and is not extensively tested. The recommended way of
-defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+defining flags is using [#!define](core.md#define) (which
 is also valid for branch/script flags):
 
 ``` c
@@ -3741,9 +3741,9 @@ Example of usage:
 
 The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
-[`$retcode`](devel#retcode) or `$?` variable.
+[`$retcode`](#retcode) or `$?` variable.
 
-`return(0)` is same as [`exit()`](devel#exit);
+`return(0)` is same as [`exit()`](#exit);
 
 In bool expressions:
 

docs/cookbooks/5.7.x/core.md

@@ -1416,7 +1416,7 @@ flags
 
 - NOTE: The named flags feature was propagated from the source code merge
   back in 2008 and is not extensively tested. The recommended way of
-  defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+  defining flags is using [#!define](core.md#define) (which
   is also valid for branch/script flags):
 
 ``` c
@@ -4383,7 +4383,7 @@ The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
 `$retcode` variable (which is same as `$rc` or `$?`).
 
-`return(0)` is same as [`exit()`](devel#exit);
+`return(0)` is same as [`exit()`](#exit);
 
 In logical evaluation expressions:
 

docs/cookbooks/devel/core.md

@@ -1416,7 +1416,7 @@ flags
 
 - NOTE: The named flags feature was propagated from the source code merge
   back in 2008 and is not extensively tested. The recommended way of
-  defining flags is using [#!define](../cookbooks/5.2.x/core#define.md) (which
+  defining flags is using [#!define](core.md#define) (which
   is also valid for branch/script flags):
 
 ``` c
@@ -4471,7 +4471,7 @@ The return() function allows you to return any integer value from a
 called route() block. You can test the value returned by a route using
 `$retcode` variable (which is same as `$rc` or `$?`).
 
-`return(0)` is same as [`exit()`](devel#exit);
+`return(0)` is same as [`exit()`](#exit);
 
 In logical evaluation expressions:
 

docs/cookbooks/start.md

@@ -1,3 +1,3 @@
 ##### Kamailio Cookbooks
 
-See [index#cookbooks](../index#cookbooks.md)
+See [index#cookbooks](../index.md#cookbooks.md)

docs/devel/git-access.md

@@ -105,4 +105,4 @@ new code that might not get to **master** branch after all.
 Several tutorials about committing with Git and backporting are
 available at:
 
--   [Guidelines TOC](../start#guidelines.md)
+-   [Guidelines TOC](../index.md#guidelines)

docs/devel/how-to/main.md

@@ -6,10 +6,10 @@ new developers or people working with installations from source code.
 ## Table of Content
 
 -   [How to Create and Use an Internal
-    Library](/devel/how-to/internal-lib)
+    Library](internal-lib.md)
 -   [How to Regenerate the Readme File for a
-    Module](/devel/how-to/module-readme)
+    Module](module-readme.md)
 -   [How to Run Kamailio from Source Tree
-    Directory](/devel/how-to/source-tree-run)
+    Directory](source-tree-run.md)
 -   [How to Install Kamailio in a Custom
-    Path](/devel/how-to/install-custom-path)
+    Path](install-custom-path.md)

docs/devel/irc-meetings/2013b.md

@@ -58,4 +58,4 @@ Kamailio related:
 ## Minutes
 
 -   [2013 - Second Meeting Chat Log - Thursday, September 12,
-    14:00UTC](/devel/irc-meetings/2013blog)
+    14:00UTC](2013blog.md)