anchor.diff:  messages that are transmitted within their range, and any node may update the
   mesh-global states. There is no hierarchy, and no directed data links. 
   
  -The framework resides on top of the nRF51 Softdevice, utilizing the Timeslot
  +The framework resides on top of the nRF51 SoftDevice, utilizing the Timeslot
   API to allocate radio time. The framework will attempt to allocate as much time
   as possible, in order to listen for other nodes' messages.
   
  -All nodes in the mesh share a set of indexed dataslots. The data contained at each
  +All nodes in the mesh share a set of indexed data slots. The data contained at each
   index is propagated through the mesh with version numbers, with the objective of 
   synchronizing the same version of the data across all nodes in the mesh. Each 
   time a node overwrites a value, it increments the version number, and all nodes 
  
positive.code: 
  The value propagation is controlled by an implementation of the IETF RFC6206
  "Trickle", a flood control algorithm for lossy, low power networks. The Trickle
  algorithm dynamically decides intervals at which a value will be broadcasted by
  a node, based on how many consistent messages the node picks up, and when the last
  update to the state it manages was. The Trickle algorithm dynamically adapts to
  node density and value update frequency.
  
  The framework provides each handle-value pair with one Trickle-instance (an
  isolated version of the algorithm), and utilizes the Softdevice GATT server
  structure to store the values. All values are stored as characteristics within
  one "Mesh"-GATT Service, which is accessible to external nodes through a
  classic BLE Softdevice connection, implemented in application space. The "BLE
  Gateway example" displays a way to achieve such behavior.
  
  == Architecture details
  
negative.code: _rebroadcasts_ it, letting its neighbors hear the new message. 
  The neighbors rebroadcast the message to their neighbors, and the process
  is repeated until all devices in the mesh have received the message. This 
  lets wireless devices talk to each other without being within direct radio 
  range, as devices between them help relaying the messages.
  
  The Rebroadcasting Mesh framework (hereby referred to as "the framework" or
  