diff --git a/doc/12-livestatus.md b/doc/12-livestatus.md
index 6b364497e..c62da0923 100644
--- a/doc/12-livestatus.md
+++ b/doc/12-livestatus.md
@@ -16,7 +16,7 @@ re-implementation of the Livestatus protocol which is compatible with MK
Livestatus.
Details on the available tables and attributes with Icinga 2 can be found
-in the [Livestatus Schema](19-apendix.md#schema-livestatus) section.
+in the [Livestatus Schema](19-appendix.md#schema-livestatus) section.
You can enable Livestatus using icinga2 feature enable:
@@ -92,7 +92,7 @@ Example using the tcp socket listening on port `6558`:
### Livestatus COMMAND Queries
-A list of available external commands and their parameters can be found [here](19-apendix.md#external-commands-list-detail)
+A list of available external commands and their parameters can be found [here](19-appendix.md#external-commands-list-detail)
$ echo -e 'COMMAND ' | netcat 127.0.0.1 6558
@@ -190,5 +190,5 @@ Default separators.
The `commands` table is populated with `CheckCommand`, `EventCommand` and `NotificationCommand` objects.
-A detailed list on the available table attributes can be found in the [Livestatus Schema documentation](19-apendix.md#schema-livestatus).
+A detailed list on the available table attributes can be found in the [Livestatus Schema documentation](19-appendix.md#schema-livestatus).
diff --git a/doc/3-monitoring-basics.md b/doc/3-monitoring-basics.md
index 9ef9b31ec..5ee3107cd 100644
--- a/doc/3-monitoring-basics.md
+++ b/doc/3-monitoring-basics.md
@@ -1430,7 +1430,7 @@ Rephrased: If the parent service object changes into the `Warning` state, this
dependency will fail and render all child objects (hosts or services) unreachable.
You can determine the child's reachability by querying the `is_reachable` attribute
-in for example [DB IDO](19-apendix.md#schema-db-ido-extensions).
+in for example [DB IDO](19-appendix.md#schema-db-ido-extensions).
### Implicit Dependencies for Services on Host
diff --git a/doc/4-advanced-topics.md b/doc/4-advanced-topics.md
index e7fa23b5a..bf242bb11 100644
--- a/doc/4-advanced-topics.md
+++ b/doc/4-advanced-topics.md
@@ -273,7 +273,7 @@ a forced service check:
Oct 17 15:01:25 icinga-server icinga2: Executing external command: [1382014885] SCHEDULE_FORCED_SVC_CHECK;localhost;ping4;1382014885
Oct 17 15:01:25 icinga-server icinga2: Rescheduling next check for service 'ping4'
-A list of currently supported external commands can be found [here](19-apendix.md#external-commands-list-detail).
+A list of currently supported external commands can be found [here](19-appendix.md#external-commands-list-detail).
Detailed information on the commands and their required parameters can be found
on the [Icinga 1.x documentation](http://docs.icinga.org/latest/en/extcommands2.html).
@@ -610,7 +610,7 @@ Example for PostgreSQL:
(1 Zeile)
-A detailed list on the available table attributes can be found in the [DB IDO Schema documentation](19-apendix.md#schema-db-ido).
+A detailed list on the available table attributes can be found in the [DB IDO Schema documentation](19-appendix.md#schema-db-ido).
## Check Result Files
diff --git a/doc/9-monitoring-remote-systems.md b/doc/9-monitoring-remote-systems.md
index c7fc0dbce..92d65c11c 100644
--- a/doc/9-monitoring-remote-systems.md
+++ b/doc/9-monitoring-remote-systems.md
@@ -789,7 +789,7 @@ SNMP Traps can be received and filtered by using [SNMPTT](http://snmptt.sourcefo
and specific trap handlers passing the check results to Icinga 2.
Following the SNMPTT [Format](http://snmptt.sourceforge.net/docs/snmptt.shtml#SNMPTT.CONF-FORMAT)
-documentation and the Icinga external command syntax found [here](19-apendix.md#external-commands-list-detail)
+documentation and the Icinga external command syntax found [here](19-appendix.md#external-commands-list-detail)
we can create generic services that can accommodate any number of hosts for a given scenario.
#### Simple SNMP Traps