Fix the links to Appendices

chapters/introduction.asciidoc

@@ -254,7 +254,7 @@ xref:CH-Debugging[] we will look at how to find the cause
 of crashing applications and how to find bugs in your application.
 
 For information on how to build and run an Erlang node
-see xref:CH-BuildingERTS[], and read the rest of the book to
+see xref:AP-BuildingERTS[], and read the rest of the book to
 learn all about the components of an Erlang node.
 
 ==== Distribution
@@ -366,7 +366,7 @@ is just one process running in the VM. On a multicore machine Erlang
 actually runs more than one scheduler, usually one per physical core,
 each having their own queues. This way Erlang achieves true
 parallelism. To utilize more than one core ERTS has to be built (see
-xref:CH-BuildingERTS[]) in _SMP_(((SMP))) mode. SMP stands for
+xref:AP-BuildingERTS[]) in _SMP_(((SMP))) mode. SMP stands for
 _Symmetric MultiProcessing_, that is, the ability to execute a
 processes on any one of multiple CPUs.
 

chapters/ops.asciidoc

@@ -543,7 +543,7 @@ just the node name.
 
 If you have built your runtime with OPPROF or DEBUG you will be able
 to get even more information.  We will look at how to do this in
-xref:CH-BuildingERTS[]. The code for the break mode can be found in
+xref:AP-BuildingERTS[]. The code for the break mode can be found in
 <filename>[OTP_SOURCE]/erts/emulator/beam/break.c</filename>.
 
 Note that going into break mode freezes the node. This is

chapters/processes.asciidoc

@@ -481,7 +481,7 @@ There are new versions of these BIFs that do a better
 job, hopefully they will be included in ERTS at the
 time of the printing of this book. Otherwise you
 can build your own version with the patch provided
-in the code section and the instructions in xref:CH-BuildingERTS[].
+in the code section and the instructions in xref:AP-BuildingERTS[].
 
 ****