anchor.diff:  people learned Go by contributing to Packetbeat & libbeat, including the
   original Packetbeat authors.
   
  -To exemplify this guide with a working example, we will follow
  +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 ships them to Elasticsearch for storage.
  +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:
  +Topbeat and libeat and compiling them at the same time is to do:
   
   [source,shell]
   ----------------------------------------------------------------------
  
positive.code: = Developer guide: creating a new Beat
  
  This guide walks you through the steps for creating a new Elastic Beat.
  The Beats are a collection of lightweight daemons that collection
  operational data from your servers and ship it to Logstash or Elasticsearch.
  The common parts from all Beats are placed in the libbeat library, which
  contains packages for sending data to Elasticsearch and Logstash, for
  configuration file handling, for signal handling, for logging and so on. By
  using this common framework, we can ensure that all Beats are behaving the same
  and they are easy to package and run with common tools.
  
  == Getting ready
  
  
negative.code: }
  ----------------------------------------------------------------------
  
  Now that you have the big picture, let's dig into the code.
  
  == Beat specific code
  
  