Fix links

content/docs/3_cookbook/0_development-deployment/0_git-based-ftp-deployment/cookbook-recipe.txt

@@ -30,7 +30,7 @@ This is a step-by-step guide for FTP-deployment to development, staging and prod
 
 ## Requirements and Prerequisites
 - **Local running Kirby project**
-    First of all, we need a running Kirby project on your local machine. If you need help setting up a local environment, I recommend Sonja's guide: (link: /docs/guide/development-environment text: Local development environment). I use (link:https://laravel.com/docs/valet text:Laravel valet) on my MacBook, but it's up to you to choose a solution that works best for you.
+    First of all, we need a running Kirby project on your local machine. If you need help setting up a local environment, I recommend Sonja's guide: (link: docs/guide/install-guide/development-environment text: Local development environment). I use (link: https://laravel.com/docs/valet text: Laravel valet) on my MacBook, but it's up to you to choose a solution that works best for you.
 - **Web server for staging**
     Second, we need a running web server for staging, e.g. *staging.example.com*. The requirements are very low. It can be a web hosting starter package with a hoster of your choice. Only FTP access is needed, and the FTP path should be the root directory of the web server. SSH is not required.
 - **Web server for production**

content/docs/3_cookbook/0_development-deployment/0_kirby-meets-docker/cookbook-recipe.txt

@@ -25,7 +25,7 @@ Text:
 
 ## The problem
 
-When you develop a website or–more generally speaking—an application, you usually do this on your own computer in the context of a desktop operating system (macOS, Windows or Linux) using some sort of (link: docs/guide/development-environment text: development environment) installed on this computer. However, when you deploy your application to production, it will often run on a different operating system, with different settings and maybe different versions of other dependencies (e.g. Composer, Node.js, bundlers etc.). These differences between environments often cause problems, and what runs without issues on your machine might not run on your colleague's machine or the production server.
+When you develop a website or–more generally speaking—an application, you usually do this on your own computer in the context of a desktop operating system (macOS, Windows or Linux) using some sort of (link: docs/guide/install-guide/development-environment text: development environment) installed on this computer. However, when you deploy your application to production, it will often run on a different operating system, with different settings and maybe different versions of other dependencies (e.g. Composer, Node.js, bundlers etc.). These differences between environments often cause problems, and what runs without issues on your machine might not run on your colleague's machine or the production server.
 
 Or, let's say you want to test and evaluate a new application. Maybe it has a long list of dependencies that you don't have installed on your machine. Do you really want to install all that stuff on your or all the evaluation team's laptops just to find out that it's not the right tool for the job? In the end, your computer is cluttered with stuff that you'll never need again.
 

content/docs/3_cookbook/0_development-deployment/0_nginx/cookbook-recipe.txt

@@ -22,7 +22,7 @@ Tags: deployment, development, webserver
 
 Text:
 
-In its [requirements](https://getkirby.com/docs/guide/quickstart), Kirby states that it is able to run on many different web servers. However, in reality it seems that most of the time it is used on Apache servers. Historically, Apache is pretty common among shared webhosting providers where many people host their Kirby sites. It's also very popular as a local development server because of [tools like LAMP/MAMP/WAMP](https://getkirby.com/docs/guide/development-environment), which make it very easy to install Apache and PHP on your local computer. Even though Nginx has been around for more than 15 years and is widely considered to be more modern and more performant than Apache, it's often still seen as more complicated or not as beginner-friendly.
+Based on its (link: docs/guide/quickstart text: requirements), Kirby is able to run on many different web servers. However, most of the time it is used on Apache servers. Historically, Apache is pretty common among shared webhosting providers where many people host their Kirby sites. It's also very popular as a local development server because of (link: docs/guide/install-guide/development-environment text: tools like LAMP/MAMP/WAMP), which make it very easy to install Apache and PHP on your local computer. Even though Nginx has been around for more than 15 years and is widely considered to be more modern and more performant than Apache, it's often still seen as more complicated or not as beginner-friendly.
 
 ## Nginx: No support for `.htaccess`
 

content/docs/3_cookbook/0_php/0_understanding-oop/cookbook-recipe.txt

@@ -37,7 +37,7 @@ No images, lots of text 😉. But at least some code to play with. So get some c
 
 If you want to code along with this recipe, you need the following:
 
-- A web server (ideally on your (link: docs/guide/development-environment text: local machine))
+- A web server (ideally on your (link: docs/guide/install-guide/development-environment text: local machine))
 - A current version of PHP
 - A code/text editor of your choice
 

content/kosmos/20190511_34/kosmos-issue.txt

@@ -37,7 +37,7 @@ Combine Kirby's file-based architecture with content from any source and edit it
 
 Our cookbook also has some new tips and solutions, among them:
 
-- Popular options for setting up a [local development environment](https://getkirby.com/docs/guide/development-environment)
+- Popular options for setting up a (link: docs/guide/install-guide/development-environment text: local development environment)
 
 - [Paginating long posts](https://getkirby.com/docs/cookbook/navigation/paginating-posts)