Added missing files and tags.

Makefile

@@ -9,12 +9,18 @@ adocs = book.asciidoc \
 	chapters/calls.asciidoc \
 	chapters/compiler.asciidoc \
 	chapters/contributors.txt \
+	chapters/data_structures.asciidoc \
+	chapters/debugging.asciidoc \
+	chapters/hipe.asciidoc \
 	chapters/introduction.asciidoc \
 	chapters/memory.asciidoc \
 	chapters/opcodes_doc.asciidoc \
+	chapters/ops.asciidoc \
 	chapters/preface.asciidoc \
 	chapters/processes.asciidoc \
 	chapters/scheduling.asciidoc \
+	chapters/tracing.asciidoc \
+	chapters/tweak.asciidoc \
 	chapters/type_system.asciidoc \
 	chapters/ap-beam_instructions.asciidoc \
 	chapters/ap-code_listings.asciidoc \

book.asciidoc

@@ -3,6 +3,8 @@
 include::chapters/preface.asciidoc[]
 
 // Part I
+[[P-ERTS]]
+= Understanding ERTS
 
 include::chapters/introduction.asciidoc[]
 
@@ -28,28 +30,27 @@ include::chapters/scheduling.asciidoc[]
 
 include::chapters/memory.asciidoc[]
 
-== Advanced data structures (ETS, DETS, Mnesia)
-// include::chapters/data_structures.asciidoc[]
+include::chapters/data_structures.asciidoc[]
 
 include::chapters/io.asciidoc[]
 
-== Distribution
-// include::chapters/distribution.asciidoc[]
+include::chapters/distribution.asciidoc[]
 
 include::chapters/c.asciidoc[]
 
-== Native code
-// include::chapters/hipe.asciidoc[]
+include::chapters/hipe.asciidoc[]
 
 // Part II
 [[P-Running]]
 = Running ERTS
 
-== Operation and Maintenance
+include::chapters/tracing.asciidoc[]
 
-// include::chapters/ops.asciidoc[]
+include::chapters/debugging.asciidoc[]
 
-// include::chapters/tweak.asciidoc[]
+include::chapters/ops.asciidoc[]
+
+include::chapters/tweak.asciidoc[]
 
 [appendix]
 = Apendicies

chapters/data_structures.asciidoc

@@ -0,0 +1,2 @@
+[[CH-DataStructures]]
+== Advanced data structures (ETS, DETS, Mnesia)

chapters/debugging.asciidoc

@@ -0,0 +1,2 @@
+[[CH-Debugger]]
+== Debugging

chapters/distribution.asciidoc

@@ -0,0 +1,2 @@
+[[CH-Distribution]]
+== Distribution

chapters/hipe.asciidoc

@@ -0,0 +1,2 @@
+[[CH-Native]]
+== Native Code

chapters/introduction.asciidoc

@@ -1,6 +1,3 @@
-[[P-ERTS]]
-= Understanding ERTS
-
 [[introduction]]
 
 == Introducing the Erlang Runtime System
@@ -33,36 +30,37 @@ general definition to be able to identify an implementation specific
 detail. In the Erlang world we are usually too pragmatic to worry about
 this.
 
-I will try to use the term _Erlang Runtime System_ to refer to the
+We will try to use the term _Erlang Runtime System_ to refer to the
 general idea of any Erlang Runtime System as opposed to the specific
-implementation by Ericsson which I'll call the Erlang RunTime System
+implementation by Ericsson which we call the Erlang RunTime System
 or usually just ERTS.
 
 *Note* This book is mostly a book about ERTS in particular and only to
 a small extent about any general Erlang Runtime System. If you assume
-that I talk about the Ericsson implementation unless I clearly state
-that I am talking about a general principle you will probably be
+that we talk about the Ericsson implementation unless is clearly stated
+that we are talking about a general principle you will probably be
 right.
 
 === How to read this book
 
-In xref:P-Running[] of this book I will show you how to tune the
+In xref:P-Running[] of this book we will look at how to tune the
 runtime system for your application and how to profile and debug
 your application and the runtime system. In order to really know
 how to tune the system you also need to know the system. In
 xref:P-ERTS[] of this book you will get a deep understanding of
 how the runtime system works.
 
-In the following chapters of xref:P-ERTS[] I will try to explain each
-component of the system by itself, in a separate chapter for each of
-the major component. You should be able to read any one of these
+The following chapters of xref:P-ERTS[] will go over each
+component of the system by itself.
+You should be able to read any one of these
 chapters without having a full understanding of how the other
 components are implemented, but you will need a basic understanding of
 what each component is. The rest of this introductory chapter should
 give you enough basic understanding and vocabulary to be able to jump
 between the rest of the chapters in part one in any order you like.
 
-However, if you have the time I strongly recommend reading the book in
+However, if you have the time
+read the book in
 order the first time. Words that are specific to Erlang and ERTS or
 used in a specific way in this book are usually explained at their
 first occurrence. Then, when you know the vocabulary, you can come
@@ -72,7 +70,7 @@ particular component.
 [[ERTS]]
 === ERTS
 
-In this section I will give a basic overview of the main components of
+In this there is a basic overview of the main components of
 ERTS (((ERTS))) and some vocabulary needed to understand the more
 detailed descriptions of each component in the following chapters.
 
@@ -108,7 +106,7 @@ need different builds of ERTS depending on whether you want to use
 multicore or not and whether you want to use 32-bit or 64-bit. (See
 xref:CH-BuildingERTS[] for information on how to build different
 versions of ERTS).  This book will not go into any details about
-hardware but I will talk a bit about multicore and NUMA architectures
+hardware but will talk a bit about multicore and NUMA architectures
 in xref:CH-Scheduling[] and xref:CH-Memory[].
 
 The second layer in the stack is the OS level. ERTS runs on most
@@ -126,7 +124,7 @@ application you might have to use Windows. The Windows port of ERTS
 has so far not had the highest priority and might not be the best
 choice from a performance or maintenance perspective. If you want to
 use a 64-bit ERTS you of course need to have both a 64-bit machine and
-a 64-bit OS. I will not cover many OS specific questions in this book.
+a 64-bit OS. This book will not cover many OS specific questions.
 
 The third layer in the stack is the Erlang Runtime System. In our case
 this will be ERTS. This and the next layer, the Erlang Virtual Machine
@@ -153,9 +151,9 @@ Finally, the sixth layer (APP) is your application which can use all
 the functionality provided by the underlying layers. Apart from
 upgrading your hardware this is probably the place where you most
 easily can improve your application's performance. In
-xref:CH-Tracing[] I will give some hints and show some tools that can
-help you profile and optimize your application. In xref:CH-Crash[] and
-xref:CH-Debugger[] I'll give you some hints on how to find the cause
+xref:CH-Tracing[] there are some hints and some tools that can
+help you profile and optimize your application. In
+xref:CH-Debugger[] we will look at how to find the cause
 of crashing applications and how to find bugs in your application.
 
 [shaape]
@@ -309,20 +307,16 @@ shell. In this case the code is not compiled to BEAM code and executed by
 the BEAM, instead the code is parsed and interpreted by the Erlang
 interpreter. In general the interpreted code behaves exactly as compiled
 code, but there a few subtle differences, these differences and all other
-aspects of the shell are explained in xref:CH-Shell[].
+aspects of the shell are explained in xref:CH-Ops[].
 
 [[Other_Erlang_Implementations]]
 === Other Erlang Implementations
 
 This book is mainly concerned with the "standard" Erlang
 implementation by Ericsson/OTP called ERTS, but there are a few other
-implementations available and in this section I will discuss some of
+implementations available and in this section we will look at some of
 them briefly.
 
-Throught the book I will sometimes mention differences between other
-implementations and ERTS, but there is no guarantee that I will
-mention all differences.
-
 ==== Erlang on Xen
 
 Erlang on Xen (link:http://erlangonxen.org) is an Erlang implementation
@@ -398,7 +392,6 @@ each component. If you are eager to understand a certain component,
 you can jump directly to that chapter. Or if you are really eager to
 find a solution to a specific problem you could jump to the right
 chapter in xref:P-Running[], and try the different methods to tune,
-tweak, or debug your system. Although, I strongly suggest that you
-read through the chapters in xref:P-ERTS[] in order to first get
-a deep understanding of how ERTS really works.
+tweak, or debug your system.
+
 

chapters/ops.asciidoc

@@ -0,0 +1,2 @@
+[[CH-Ops]]
+== Operation and Maintenance

chapters/tracing.asciidoc

@@ -0,0 +1,2 @@
+[[CH-Tracing]]
+== Tracing

chapters/tweak.asciidoc

@@ -0,0 +1,2 @@
+[[CH-Tweak]]
+== Tweaking the Runtime System