diff --git a/_includes/shared/tutorial/headmodel_read_align.md b/_includes/shared/tutorial/headmodel_read_align.md
index 5cfaadab2..6f4774ae0 100644
--- a/_includes/shared/tutorial/headmodel_read_align.md
+++ b/_includes/shared/tutorial/headmodel_read_align.md
@@ -1,6 +1,6 @@
 ### Reading in the anatomical data
 
-Before starting with FieldTrip, it is important that you set up your [MATLAB path](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) properly.
+Before starting with FieldTrip, it is important that you set up your [MATLAB path](/faq/installation) properly.
 
     cd <path_to_fieldtrip>
     ft_defaults
diff --git a/development/project/femfuns.md b/development/project/femfuns.md
index 5acba24b5..a4059ce06 100644
--- a/development/project/femfuns.md
+++ b/development/project/femfuns.md
@@ -70,7 +70,7 @@ Creating the environment is only needed once, but every new session where FEMfun
 
     conda activate femfuns
 
-Before starting with FieldTrip, it is important that you set up your [MATLAB path](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) properly.
+Before starting with FieldTrip, it is important that you set up your [MATLAB path](/faq/installation) properly.
 
     cd <path_to_fieldtrip>
     ft_defaults
diff --git a/download.md b/download.md
index a4ba0acb9..373c8c32d 100644
--- a/download.md
+++ b/download.md
@@ -9,7 +9,7 @@ You can download the FieldTrip toolbox [here](/download.php).
 
 Prior to downloading, you might want to check whether your computer meets the [MATLAB requirements](/faq/requirements).
 
-After downloading, you can follow the instructions in this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) for setting up the MATLAB path.
+After downloading, you can follow the instructions in this [frequently asked question](/faq/installation) for setting up the MATLAB path.
 
 You can download the tutorial data [here](https://download.fieldtriptoolbox.org/tutorial/).
 
diff --git a/faq.md b/faq.md
index f2e8de0b2..6c39b2b19 100644
--- a/faq.md
+++ b/faq.md
@@ -183,7 +183,7 @@ See also the [tutorials](/tutorial) and [example scripts](/example).
 - [MATLAB complains that mexmaci64 cannot be opened because the developer cannot be verified](/faq/mexmaci64_cannot_be_opened_because_the_developer_cannot_be_verified)
 - [MATLAB does not see the functions in the "private" directory](/faq/matlab_does_not_see_the_functions_in_the_private_directory)
 - [MATLAB version 7.3 (2006b)_crashes_when_I_try_to_do_...](/faq/matlab_version_7.3_2006b_crashes_when_i_try_to_do)
-- [Should I add FieldTrip with all subdirectories to my MATLAB path?](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)
+- [Should I add FieldTrip with all subdirectories to my MATLAB path?](/faq/installation)
 - [The databrowser crashes and destroys the whole MATLAB session, how can I resolve this?](/faq/the_databrowser_crashes_and_destroys_the_whole_matlab_session_how_can_i_resolve_this)
 - [What are the MATLAB requirements for using FieldTrip?](/faq/requirements)
 - [What is the relation between "events" (such as_triggers) and "trials"?](/faq/what_is_the_relation_between_events_such_as_triggers_and_trials)
diff --git a/faq/can_i_prevent_external_toolboxes_from_being_added_to_my_matlab_path.md b/faq/can_i_prevent_external_toolboxes_from_being_added_to_my_matlab_path.md
index 495ff8ed2..ecf3105ba 100644
--- a/faq/can_i_prevent_external_toolboxes_from_being_added_to_my_matlab_path.md
+++ b/faq/can_i_prevent_external_toolboxes_from_being_added_to_my_matlab_path.md
@@ -5,7 +5,7 @@ tags: [faq, matlab, toolbox, path]
 
 # Can I prevent "external" toolboxes from being added to my MATLAB path?
 
-The recommended path settings are explained in this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+The recommended path settings are explained in this [frequently asked question](/faq/installation).
 
 The code in the **[ft_defaults](/reference/ft_defaults)** function will execute only once and should preferably be executed in your `startup.m` file. The main FieldTrip functions will also call **[ft_defaults](/reference/ft_defaults)** to ensure that the required subdirectories are on the path.
 
diff --git a/faq/i_am_working_at_the_donders_should_i_also_download_fieldtrip.md b/faq/i_am_working_at_the_donders_should_i_also_download_fieldtrip.md
index e0411e3ba..65395cf55 100644
--- a/faq/i_am_working_at_the_donders_should_i_also_download_fieldtrip.md
+++ b/faq/i_am_working_at_the_donders_should_i_also_download_fieldtrip.md
@@ -15,4 +15,4 @@ The common FieldTrip version on the shared network drive is automatically update
 
 If you want to do your computations on your laptop or at home, you can use the download or github version.
 
-See also this FAQ on [how to setup your FieldTrip path in MATLAB](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+See also this FAQ on [how to setup your FieldTrip path in MATLAB](/faq/installation).
diff --git a/getting_started/blackrock.md b/getting_started/blackrock.md
index e3eaf243d..123bbd588 100644
--- a/getting_started/blackrock.md
+++ b/getting_started/blackrock.md
@@ -11,7 +11,7 @@ To read Blackrock data, you will need the NPMK toolbox. The latest version is av
 
 ## Set the path
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/bti.md b/getting_started/bti.md
index 89b0a22e1..6128e3e91 100644
--- a/getting_started/bti.md
+++ b/getting_started/bti.md
@@ -36,7 +36,7 @@ FieldTrip knows how to deal with raw, i.e. unprocessed, data files. Data files w
 
 ## Set the path
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/ctf.md b/getting_started/ctf.md
index b5c64515c..246705d26 100644
--- a/getting_started/ctf.md
+++ b/getting_started/ctf.md
@@ -44,7 +44,7 @@ You should not store any scripts or mat files in the xxx.ds folder. When analyzi
 
 ## Set the path
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/neuralynx.md b/getting_started/neuralynx.md
index ac6241000..602018e0b 100644
--- a/getting_started/neuralynx.md
+++ b/getting_started/neuralynx.md
@@ -22,7 +22,7 @@ Neuralynx also writes a raw data file (.nrd) in which all the channels are sampl
 
 ## Set the path
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/neuromag.md b/getting_started/neuromag.md
index 249f50dec..66e0c49c3 100644
--- a/getting_started/neuromag.md
+++ b/getting_started/neuromag.md
@@ -20,7 +20,7 @@ Note that the MEG-PD toolbox will only function on 32-bit machines, and requires
 
 ## Set the path
 
-To get started, you need to add the paths where the FieldTrip and MNE toolboxes can be found. You should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you need to add the paths where the FieldTrip and MNE toolboxes can be found. You should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/plexon.md b/getting_started/plexon.md
index ea23d173e..9a4688030 100644
--- a/getting_started/plexon.md
+++ b/getting_started/plexon.md
@@ -19,7 +19,7 @@ The .plx files contain the multiplexed raw acquisition data. During acquisition
 
 There are some constraints related to the way that FieldTrip represents continuous and spike data. All main FieldTrip functions read continuous data using the **[ft_read_header](/reference/fileio/ft_read_header)** and **[ft_read_data](/reference/fileio/ft_read_data)** functions. These functions require the continuous data in all channels contained in the file to have the same sampling frequency. This can be a problem because Plexon file formats often contain both 40kHz spike data and 1kHz sampled LFP data in the same file. One solution is to resave all source files into two separate files. The other is to modify the fileio functions to select the correct sampling frequency and channels.
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/realtime.md b/getting_started/realtime.md
index 1498e61f0..55e4b1076 100644
--- a/getting_started/realtime.md
+++ b/getting_started/realtime.md
@@ -13,7 +13,7 @@ The general idea behind the real-time processing of EEG/MEG data in FieldTrip in
 To get some quick satisfaction with streaming data, you might want to try out the example given in this [frequently asked question](/faq/how_should_i_get_started_with_the_fieldtrip_realtime_buffer).
 {% include markup/end %}
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/ricoh.md b/getting_started/ricoh.md
index d0d59f063..843b38c93 100644
--- a/getting_started/ricoh.md
+++ b/getting_started/ricoh.md
@@ -31,7 +31,7 @@ The functions in FieldTrip that allows you to execute the pre-processing and co-
 
 ## Set the path
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path). You also need to set the path to your data files.
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation). You also need to set the path to your data files.
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/getting_started/yokogawa.md b/getting_started/yokogawa.md
index 0d1abb43e..161015dc4 100644
--- a/getting_started/yokogawa.md
+++ b/getting_started/yokogawa.md
@@ -31,7 +31,7 @@ Usually you will be starting your FieldTrip analysis with raw continuous data wh
 
 ## Set the path
 
-To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+To get started, you should add the FieldTrip main directory to your path, and execute the **[ft_defaults](/reference/ft_defaults)** function, which sets the defaults and configures up the minimal required path settings. See also this [frequently asked question](/faq/installation).
 
     addpath <path_to_fieldtrip>
     ft_defaults
diff --git a/tutorial/distributedcomputing_parfor.md b/tutorial/distributedcomputing_parfor.md
index d4c6a2a58..1b7434262 100755
--- a/tutorial/distributedcomputing_parfor.md
+++ b/tutorial/distributedcomputing_parfor.md
@@ -66,7 +66,7 @@ This tutorial requires the original MEG datasets for the four subjects, plus one
 
 Additional prerequisites:
 
--   Make sure FieldTrip is on your path, see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)
+-   Make sure FieldTrip is on your path, see this [FAQ](/faq/installation)
 -   Have the necessary data next to each other in a single directory: the directories 'Subject01.ds', 'Subject02.ds', 'Subject03.ds', 'Subject04.ds', 'SubjectSEF.ds' should all be next to each other.
 -   Put your test scripts also in this directory
 
diff --git a/tutorial/electrode.md b/tutorial/electrode.md
index 27c3dccc6..a61e940c9 100644
--- a/tutorial/electrode.md
+++ b/tutorial/electrode.md
@@ -47,7 +47,7 @@ The structure sensor is attached to an iPad mini. We use the [Scanner - Structur
 
 [Here](https://download.fieldtriptoolbox.org/tutorial/electrode/3D-Scan.zip) you can download the result of the 3D-scan that we will use in this tutorial. Note that the Structure Sensor data comprises three files that should be kept together: an `.obj` file with the geometry, a `.jpg` file with the color photo texture mapping, and an `.mtl` file that maps between the geometry and the colors. If the `.mtl` and `.jpg` file are missing, there is no color information for the mesh.
 
-Before starting with FieldTrip, it is important that you set up your [MATLAB path](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) properly.
+Before starting with FieldTrip, it is important that you set up your [MATLAB path](/faq/installation) properly.
 
     cd <path_to_fieldtrip>
     ft_defaults
diff --git a/tutorial/epilepsy.md b/tutorial/epilepsy.md
index 3c6adcf4d..34a7f1c43 100644
--- a/tutorial/epilepsy.md
+++ b/tutorial/epilepsy.md
@@ -117,7 +117,7 @@ surgery, though the extent of the polymicrogyria rendered this a difficult
 option.
 {% include markup/end %}
 
-The shared data is available from our [download server](https://download.fieldtriptoolbox.org/tutorial/epilepsy/). After downloading the data, we set up the path and ensure that FieldTrip is the only toolbox on the path. See also [this FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+The shared data is available from our [download server](https://download.fieldtriptoolbox.org/tutorial/epilepsy/). After downloading the data, we set up the path and ensure that FieldTrip is the only toolbox on the path. See also [this FAQ](/faq/installation).
 
     restoredefaultpath
     addpath ~/matlab/fieldtrip/
diff --git a/tutorial/headmodel_meg.md b/tutorial/headmodel_meg.md
index a64672561..b72676f32 100644
--- a/tutorial/headmodel_meg.md
+++ b/tutorial/headmodel_meg.md
@@ -46,7 +46,7 @@ _Figure 2. Pipeline of creating and visualizing a head model_
 
 ### Reading in the anatomical data
 
-Before starting to use FieldTrip, it is important that you set up your MATLAB path properly. You can read about how to set up your MATLAB path [here](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Before starting to use FieldTrip, it is important that you set up your MATLAB path properly. You can read about how to set up your MATLAB path [here](/faq/installation).
 
     cd <path_to_fieldtrip>
     ft_defaults
diff --git a/tutorial/human_ecog.md b/tutorial/human_ecog.md
index 39532aae2..d9492ef55 100644
--- a/tutorial/human_ecog.md
+++ b/tutorial/human_ecog.md
@@ -11,7 +11,7 @@ Intracranial EEG (iEEG) allows simultaneous recordings from tens to hundreds of
 
 Before we start, it is important to emphasize that human iEEG datasets are solely acquired for clinical purposes and come in different shapes and sizes. Some medical institutes use photography or X-ray (e.g., see [Analysis of monkey ECoG recordings)](/tutorial/monkey_ecog) for including anatomy in the analysis of the functional recordings, whilst others use CT (3D image from a series of X-rays) and/or MR, or combinations thereof. The example iEEG dataset used in this tutorial is not representative for all the datasets obtained in the field but it is meant to serve as a platform for thinking and dealing with the challenges associated with analyzing this type of data.
 
-The tutorial demonstrates the analysis of task-related high-frequency-band activity (~70 to 150 Hz), a prominent neural signature in intracranial data that has been associated with neuron population level firing rate. Many other supported analyses such as event-related potential analysis, connectivity analysis, and statistical analysis have been described in detail elsewhere (Oostenveld et al., 2011; Maris & Oostenveld, 2007; Bastos & Schoffelen, 2016). You will need the iEEG data of SubjectUCI29, which can be obtained from [here](https://doi.org/10.5281/zenodo.1201560). If you are getting started with FieldTrip, download the most recent version from its homepage or GitHub and [set up your MATLAB path](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+The tutorial demonstrates the analysis of task-related high-frequency-band activity (~70 to 150 Hz), a prominent neural signature in intracranial data that has been associated with neuron population level firing rate. Many other supported analyses such as event-related potential analysis, connectivity analysis, and statistical analysis have been described in detail elsewhere (Oostenveld et al., 2011; Maris & Oostenveld, 2007; Bastos & Schoffelen, 2016). You will need the iEEG data of SubjectUCI29, which can be obtained from [here](https://doi.org/10.5281/zenodo.1201560). If you are getting started with FieldTrip, download the most recent version from its homepage or GitHub and [set up your MATLAB path](/faq/installation).
 
 {% include markup/warning %}
 The information on this page originates from the human intracranial data analysis protocol described in Stolk, Griffin et al., **[Integrated analysis of anatomical and electrophysiological human intracranial data](https://doi.org/10.1038/s41596-018-0009-6)**, Nature Protocols, 2018. Please cite that paper when you use the methods described here.
diff --git a/tutorial/introduction.md b/tutorial/introduction.md
index cb89da0b5..880305f7b 100644
--- a/tutorial/introduction.md
+++ b/tutorial/introduction.md
@@ -94,7 +94,7 @@ FieldTrip is composed of a collection of scripts running in MATLAB. The toolbox
 
 It is now possible to execute the MATLAB scripts by copying/pasting the relevant text from the tutorials (To copy from a Window browser to MATLAB running under Linux from X-Win32, use the mouse to highlight the text in the browser and press crtl-c. Then use ctrl-v or the middle mouse button to paste in MATLAB).
 
-Make sure that the path is set correctly to the directory of the FieldTrip toolbox and the data. For the tutorials it is recommend to 'cd' to the directory where the data are. Look at [this FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) for more information on how to correctly set your path for FieldTrip.
+Make sure that the path is set correctly to the directory of the FieldTrip toolbox and the data. For the tutorials it is recommend to 'cd' to the directory where the data are. Look at [this FAQ](/faq/installation) for more information on how to correctly set your path for FieldTrip.
 
 ## Making an analysis protocol
 
diff --git a/tutorial/nirs_singlechannel.md b/tutorial/nirs_singlechannel.md
index 3cd1b9e55..e62b6b012 100644
--- a/tutorial/nirs_singlechannel.md
+++ b/tutorial/nirs_singlechannel.md
@@ -52,7 +52,7 @@ _Figure 1: Overview of a standard fNIRS analysis procedure._
 
 ### Getting Started
 
-The dataset that we would like to analyze is called 'motor_cortex.oxy3'. First, we need to point FieldTrip to this file. Note that FieldTrip does not feature a graphical-user interface, but instead requires you to script your way to the end goal. To let MATLAB know that we want to use FieldTrip and it's file locations, add the FieldTrip folder to your path ([without subfolders](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)) and then execute the **[ft_defaults](/reference/ft_defaults)** function by typing:
+The dataset that we would like to analyze is called 'motor_cortex.oxy3'. First, we need to point FieldTrip to this file. Note that FieldTrip does not feature a graphical-user interface, but instead requires you to script your way to the end goal. To let MATLAB know that we want to use FieldTrip and it's file locations, add the FieldTrip folder to your path ([without subfolders](/faq/installation)) and then execute the **[ft_defaults](/reference/ft_defaults)** function by typing:
 
     ft_defaults
 
diff --git a/workshop/bcbt2022.md b/workshop/bcbt2022.md
index 10dc0089e..591bea6ae 100644
--- a/workshop/bcbt2022.md
+++ b/workshop/bcbt2022.md
@@ -64,7 +64,7 @@ The `<your_fieldtrip_location>` is the directory in which all the code is after
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the `startup.m` file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/installation).
 {% include markup/end %}
 
 The `restoredefaultpath` command clears your path, keeping only the official MATLAB toolboxes. The `addpath(pwd)` statement adds the present working directory, i.e. the directory containing the FieldTrip main functions. The `ft_defaults` command ensures that all required subdirectories are added to the path.
diff --git a/workshop/cuttingeeg2021.md b/workshop/cuttingeeg2021.md
index d84b4b4ad..11399278d 100644
--- a/workshop/cuttingeeg2021.md
+++ b/workshop/cuttingeeg2021.md
@@ -46,7 +46,7 @@ The `<your_fieldtrip_location>` is the directory in which all the code is after
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the `startup.m` file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/installation).
 {% include markup/end %}
 
 The `restoredefaultpath` command clears your path, keeping only the official MATLAB toolboxes. The `addpath(pwd)` statement adds the present working directory, i.e. the directory containing the FieldTrip main functions. The `ft_defaults` command ensures that all required subdirectories are added to the path.
diff --git a/workshop/davis2019.md b/workshop/davis2019.md
index 85171d58a..74f412c5d 100644
--- a/workshop/davis2019.md
+++ b/workshop/davis2019.md
@@ -78,7 +78,7 @@ To ensure that everything runs smooth, please use a recent version of FieldTrip.
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/installation).
 {% include markup/end %}
 
 The `restoredefaultpath` command clears your path, keeping only the official MATLAB toolboxes. The `addpath(pwd)` statement adds the present working directory, i.e. the directory containing the FieldTrip main functions. The `ft_defaults` command ensures that all required subdirectories are added to the path.
diff --git a/workshop/fitng2023.md b/workshop/fitng2023.md
index 9beb742f7..3290f3320 100644
--- a/workshop/fitng2023.md
+++ b/workshop/fitng2023.md
@@ -82,7 +82,7 @@ to add the scripts directory to your path. This should work if you have unzipped
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the `startup.m` file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed. See also this [frequently asked question](/faq/installation).
 {% include markup/end %}
 
 Finally, you have to tell the scripts where all the (input and output) data is with
diff --git a/workshop/jyvaskyla2017.md b/workshop/jyvaskyla2017.md
index ae45b557d..a3c49d57c 100644
--- a/workshop/jyvaskyla2017.md
+++ b/workshop/jyvaskyla2017.md
@@ -45,7 +45,7 @@ Next, the hands-on sessions are pretty self explanatory. The tutorials contain q
 {% include markup/danger %}
 In general, please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)).
+Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation)).
 {% include markup/end %}
 
 - morning
diff --git a/workshop/kiel.md b/workshop/kiel.md
index c70e82aee..f8e404298 100644
--- a/workshop/kiel.md
+++ b/workshop/kiel.md
@@ -79,7 +79,7 @@ After copying all files to your computer and unzipping then, you start MATLAB. T
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation)).
 {% include markup/end %}
 
 The `restoredefaultpath` command clears your path, keeping only the
diff --git a/workshop/marseille.md b/workshop/marseille.md
index 01182e4d6..799077bed 100644
--- a/workshop/marseille.md
+++ b/workshop/marseille.md
@@ -114,7 +114,7 @@ After copying all files to your computer and unzipping then, you start MATLAB. T
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation)).
 {% include markup/end %}
 
 The `restoredefaultpath` command clears your path, keeping only the official MATLAB toolboxes. The `addpath(pwd)` statement adds the present working directory, i.e. the directory containing the FieldTrip main functions. The `ft_defaults` command ensures that all required subdirectories are added to the path.
diff --git a/workshop/marseille2016b.md b/workshop/marseille2016b.md
index 14ac6f3f9..3bb8d69b1 100644
--- a/workshop/marseille2016b.md
+++ b/workshop/marseille2016b.md
@@ -76,7 +76,7 @@ After copying all files to your computer and unzipping then, you start MATLAB. T
 {% include markup/danger %}
 Please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)).
+Please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation)).
 {% include markup/end %}
 
 The `restoredefaultpath` command clears your path, keeping only the
diff --git a/workshop/practicalmeeg2022.md b/workshop/practicalmeeg2022.md
index 3e2c97115..29256fe62 100644
--- a/workshop/practicalmeeg2022.md
+++ b/workshop/practicalmeeg2022.md
@@ -42,7 +42,7 @@ Please take a quick look at the [FieldTrip reference paper](https://doi.org/10.1
 
 Please download the most recent version of the FieldTrip toolbox from [here](/download) or from [GitHub](https://github.com/fieldtrip/fieldtrip/tags). As we did some last miniute bugfixes to make all tutorials run smoothly, you should have version **20221207** or later.
 
-Please read [this FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path/) on how to set your path. After adding the FieldTrip main directory to your path, you should type `ft_defaults` which will add the required subdirectories (which depend on your MATLAB version). We recommend to put `ft_defaults` in your MATLAB [startup.m](https://nl.mathworks.com/help/matlab/ref/startup.html) file.
+Please read [this FAQ](/faq/installation/) on how to set your path. After adding the FieldTrip main directory to your path, you should type `ft_defaults` which will add the required subdirectories (which depend on your MATLAB version). We recommend to put `ft_defaults` in your MATLAB [startup.m](https://nl.mathworks.com/help/matlab/ref/startup.html) file.
 
 ### Download and organize the scripts and data
 
diff --git a/workshop/toolkit2016.md b/workshop/toolkit2016.md
index 72cee6d9d..ed1930601 100644
--- a/workshop/toolkit2016.md
+++ b/workshop/toolkit2016.md
@@ -95,5 +95,5 @@ The `restoredefaultpath` command clears your path, keeping only the official MAT
 {% include markup/danger %}
 In general, please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)).
+Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation)).
 {% include markup/end %}
diff --git a/workshop/toolkit2017.md b/workshop/toolkit2017.md
index 6738e199e..465a9cebe 100644
--- a/workshop/toolkit2017.md
+++ b/workshop/toolkit2017.md
@@ -85,5 +85,5 @@ The `restoredefaultpath` command clears your path, keeping only the official MAT
 {% include markup/danger %}
 In general, please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path)).
+Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation)).
 {% include markup/end %}
diff --git a/workshop/toolkit2018.md b/workshop/toolkit2018.md
index de397886b..a520bc1b6 100644
--- a/workshop/toolkit2018.md
+++ b/workshop/toolkit2018.md
@@ -91,5 +91,5 @@ The `restoredefaultpath` command clears your path, keeping only the official MAT
 {% include markup/danger %}
 In general, please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation).
 {% include markup/end %}
diff --git a/workshop/toolkit2020/test_installation.md b/workshop/toolkit2020/test_installation.md
index 7569fac09..729fceef2 100644
--- a/workshop/toolkit2020/test_installation.md
+++ b/workshop/toolkit2020/test_installation.md
@@ -27,4 +27,4 @@ Therefore, please start MATLAB on your computer, copy-and-paste the code below i
     fprintf('spm is:          %s\n', which('spm'));     % should not be found yet, or the fieldtrip version
     fprintf('################################################################\n');
 
-If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) for more information about adding FieldTrip to the MATLAB search path.
+If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/installation) for more information about adding FieldTrip to the MATLAB search path.
diff --git a/workshop/toolkit2021/test_installation.md b/workshop/toolkit2021/test_installation.md
index fc19c3303..45d48d4e3 100644
--- a/workshop/toolkit2021/test_installation.md
+++ b/workshop/toolkit2021/test_installation.md
@@ -25,4 +25,4 @@ Therefore, please start MATLAB on your computer, copy-and-paste the code below i
     fprintf('spm is:          %s\n', which('spm'));     % should not be found yet, or the fieldtrip version
     fprintf('################################################################\n');
 
-If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) for more information about adding FieldTrip to the MATLAB search path.
+If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/installation) for more information about adding FieldTrip to the MATLAB search path.
diff --git a/workshop/toolkit2022.md b/workshop/toolkit2022.md
index 8f26ffb1f..f1b3f623a 100644
--- a/workshop/toolkit2022.md
+++ b/workshop/toolkit2022.md
@@ -110,7 +110,7 @@ The `restoredefaultpath` command clears your path, keeping only the official MAT
 {% include markup/danger %}
 In general, please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation).
 {% include markup/end %}
 
 
diff --git a/workshop/toolkit2022/test_installation.md b/workshop/toolkit2022/test_installation.md
index 81caaaca8..4960c2130 100644
--- a/workshop/toolkit2022/test_installation.md
+++ b/workshop/toolkit2022/test_installation.md
@@ -23,4 +23,4 @@ Prior to the hands-on sessions, we want you to provide us with some information
     fprintf('spm is:          %s\n', which('spm'));     % should not be found yet, or the fieldtrip version
     fprintf('################################################################\n');
 
-If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) for more information about adding FieldTrip to the MATLAB search path.
+If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/installation) for more information about adding FieldTrip to the MATLAB search path.
diff --git a/workshop/toolkit2023.md b/workshop/toolkit2023.md
index 81a821cbc..205acf9d4 100644
--- a/workshop/toolkit2023.md
+++ b/workshop/toolkit2023.md
@@ -113,7 +113,7 @@ The `restoredefaultpath` command clears your path, keeping only the official MAT
 {% include markup/danger %}
 In general, please do NOT use the graphical path management tool from MATLAB. In this hands-on session we'll manage the path from the command line, but in general you are much better off using the startup.m file than the path GUI.
 
-Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path).
+Furthermore, please do NOT add FieldTrip with all subdirectories, subdirectories will be added automatically when needed, and only when needed (see this [FAQ](/faq/installation).
 {% include markup/end %}
 
 ## Code of conduct
diff --git a/workshop/toolkit2023/test_installation.md b/workshop/toolkit2023/test_installation.md
index 81caaaca8..4960c2130 100644
--- a/workshop/toolkit2023/test_installation.md
+++ b/workshop/toolkit2023/test_installation.md
@@ -23,4 +23,4 @@ Prior to the hands-on sessions, we want you to provide us with some information
     fprintf('spm is:          %s\n', which('spm'));     % should not be found yet, or the fieldtrip version
     fprintf('################################################################\n');
 
-If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/should_i_add_fieldtrip_with_all_subdirectories_to_my_matlab_path) for more information about adding FieldTrip to the MATLAB search path.
+If you get an error that says `Undefined function or variable 'ft_version'.` please add FieldTrip to the MATLAB path and try again. See [here](/faq/installation) for more information about adding FieldTrip to the MATLAB search path.