anchor.diff:  The `Beat` parameter received by most of these methods contains data about the
   Beat, such as the name, version, and common configuration options.
   
  -For more complex beats, the optional FlagsHandler interface is available.
  +For more complex Beats, the optional `FlagsHandler` interface is available.
   
   [source,go]
   ----------------------------------------------------------------------
  
positive.code: }
  ----------------------------------------------------------------------
  
  The FlagsHandler Beater extension is for handling flags input on startup.
  The HandleFlags callback will be called after parsing the command line
  arguments and handling the '--help' or '--version' flags. Use this interface
  to add additional command line flags to your beat. For an example on how to
  implement HandleFlags, have a look at
  https://github.com/elastic/packetbeat/blob/master/beat/packetbeat.go[packetbeat]
  
  We strongly recommend to only put the main method into the main package.
  This will allow all other parts of your beat to be used as library by
  other beats if needed. This means all your beat specific code goes for example
  into the beat folder and package.
  
  NOTE: To be consistent with other Beats, you should append `beat` to your Beat name.
  
  
negative.code: }
  ----------------------------------------------------------------------
  
  We recommend that you implement a `New` function that creates your Beats object.
  
  === Sharing Your Beat with the Community
  
  