anchor.diff:  
   At the high level, a simple Beat like Topbeat has two main components: one that
   collects the actual data and the Publisher. They communicate via a Go channel,
  -over which *events* are sent. The Publisher is implemented in libbeat, so you
  +over which **events** are sent. The Publisher is implemented in libbeat, so you
   typically only have to worry about the logic specific to your Beat. Besides the
   Publisher, libbeat offers common services like configuration management,
  -logging, daemonizing/windows service handling and in the future it will offer
  +logging, daemonizing/Windows service handling and in the future it will offer
   data processing modules like filtering or sampling.
   
   image:./images/beat_overview.png[Beat overview architecture]
   
  -An event is JSON like object (Golang type `map[string]interface{}`) that
  +An event is a JSON like object (Golang type `map[string]interface{}`) that
   contains the collected data and which is indexed into Elasticsearch. The only
   rules are that it must contain a `timestamp` field and a `type` field. Beyond
  -that, it doesn't matter what these events contain or how often they are created.
  -Here is an example Topbeat event:
  +that, these events can contain anything and they can be created as often as
  +needed.
   
   [source,json]
   ----------------------------------------------------------------------
  
positive.code:   procs: [".*"]
  ----------------------------------------------------------------------
  
  And here are the corresponding Go structures:
  
  [source,go]
  ----------------------------------------------------------------------
  
negative.code: people learned Go by contributing to Packetbeat & libbeat, including the
  original Packetbeat authors.
  
  To exemplify this guide with a working example, we will follow the
  https://github.com/elastic/topbeat[Topbeat] source code. Topbeat is similar to
  the `top` command line tool but instead of printing the statistics to the screen
  it periodically ships them to Elasticsearch for storage.
  
  After having https://golang.org/doc/install[installed Go] and having setup the
  https://golang.org/doc/code.html#GOPATH[GOPATH] environment variable to point to
  your preferred workspace location, a simple way of getting the source code for
  Topbeat and libeat and compiling them at the same time is to do:
  
  [source,shell]
  ----------------------------------------------------------------------
  