Fixes for typos, formats

book.asciidoc

@@ -52,7 +52,7 @@ include::chapters/ops.asciidoc[]
 
 include::chapters/tweak.asciidoc[]
 
-[appendix]
+[[appendix]]
 = Appendices
 // include::chapters/index.asciidoc[]
 

chapters/building.asciidoc

@@ -6,11 +6,11 @@ Erlang/OTP to suite your needs. We will use an Ubuntu Linux for most
 of the examples. If you are using a different OS you can find detailed
 instructions on how to build for that OS in the documentation in the
 source code (in HOWTO/INSTALL.md), or on the web
-[INSTALL.html.](http://www.erlang.org/doc/installation_guide/INSTALL.html)
+http://www.erlang.org/doc/installation_guide/INSTALL.html[INSTALL.html].
 
 There are basically two ways to build the runtime system, the traditional
 way with autoconf, configure and make or with the help of
-[kerl.](https://github.com/spawngrid/kerl)
+https://github.com/spawngrid/kerl[kerl].
 
 I recommend that you first give the traditional way a try, that way
 you will get a better understanding of what happens when you
@@ -87,7 +87,7 @@ interfering with any pre built and system wide installations.
 
 === Getting the source
 There are two main ways of getting the source. You can download a
-tarball from [erlang.org](http://www.erlang.org/download.html) or you
+tarball from http://www.erlang.org/download.html[erlang.org] or you
 can check out the source code directly from Github.
 
 If you want to quickly download a stable version of the source try:

chapters/introduction.asciidoc

@@ -59,7 +59,7 @@ 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
+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
@@ -326,7 +326,7 @@ Erlang Node.
 
 ****
 *BEAM:* The name BEAM originally stood for Bogdan's Erlang Abstract
- Machine, but now a days most people refer to it as Björn's
+ Machine, but nowadays most people refer to it as Björn's
 Erlang Abstract machine, after the current maintainer. 
  
 ****

chapters/ops.asciidoc

@@ -51,7 +51,7 @@ Eshell V8.1  (abort with ^G)
 
 Then we start an Elixir node called `node2`:
 
-[sources, iex]
+[source, bash]
 ----
 $ iex --sname node2
 Erlang/OTP 19 [erts-8.1] [source-0567896] [64-bit] [smp:4:4]

chapters/processes.asciidoc

@@ -675,7 +675,7 @@ The field `id` contains the process ID (or PID).
 The process ID is an Erlang term and hence tagged (See xref:CH-TypeSystem[]). This means
 that the 4 least significant bits are a tag (0011). In the
 code section there is a module for inspecting Erlang terms
-(see xref:listing-show[<filename>show.erl</filename>]) which we will cover in
+(see xref:listing-show[show.erl]) which we will cover in
 the chapter on types. We can use it now to to examine the
 type of a tagged word though.