anchor.diff:  | `command` | The {check_name} of the command configured as `command[{check_name}]="/path/to/plugin/check-script"      | required | empty
   | `port`    | Port to access _NRPE_ on the remote server.                                                              | optional | `5666`
   | `padding` | Padding for sending the command to the _NRPE_ agent.                                                     | optional | `2`
  -| `usessl`  | Enable encryption of network communication. _NRPE_ uses SSL with anonymous DH and the following cipher  
  +| `usessl`  | Enable encryption of network communication. _NRPE_ uses SSL with anonymous DH and the following cipher
                 suite _TLS_DH_anon_WITH_AES_128_CBC_SHA_                                                                 | optional | `true`
   |===
   
  -==== Example: Using _check_apt_ with _NRPE_
  +===== Example: Using _check_apt_ with _NRPE_
   
   This examples shows how to configure the _NrpeMonitor_ running the _check_apt_ command on a configured _NRPE_.
   
  
positive.code: 
  === NrpeMonitor
  
  This monitor allows to test plugins and checks running on the link:http://exchange.nagios.org/directory/Addons/Monitoring-Agents/NRPE--2D-Nagios-Remote-Plugin-Executor/details[Nagios Remote Plugin Executor] (_NRPE_) framework.
  The monitor allows to test the status output of any available check command executed by _NRPE_.
  
negative.code: IMPORTANT: _NRPE_ configuration on the server is required and the check command has to be configured, e.g. `command[check_apt]=/usr/lib/nagios/plugins/check_apt`
  
  CAUTION: OpenNMS executes every _NRPE_ check in a Java thread without _fork()_ a process and it is more resource friendly.
           Nevertheless it is possible to run _NRPE_ plugins which combine a lot of external programs like `sed`, `awk` or `cut`.
           Be aware, each command end up in forking additional processes.
  
  ===== Monitor facts
  
  [options="autowidth"]
  |===
  