anchor.diff:  In addition to two provided examples, there is a template project under
   _nRF51/examples/_. This may be used as a basis for your own applications, or you
   could choose to do it yourself from scratch. In theory, the framework should be
  -compatible with most Softdevice based projects, but some restrictions to
  +compatible with most SoftDevice based projects, but some restrictions to
   hardware and software modules apply, see link:docs/how_it_works.adoc#resource-allocation[Resource allocation]  for details.
  -The framework adds a Mesh GATT service to the Softdevice GATT server which
  +The framework adds a Mesh GATT service to the SoftDevice GATT server which
   contain all mesh-global states. This service may be accessed by external nodes,
   just as any other GATT service, through a connection established via the
  -Softdevice. See section link:docs/how_it_works.adoc#gatt-service[GATT service] for details about structure and
  +SoftDevice. See section link:docs/how_it_works.adoc#gatt-service[GATT service] for details about structure and
   access. 
   
   === Serial interface
   
  -The framework also has support for external control via SPI. The serial interface is based on the nRF8001 SPI interface, with different opcodes. An application controller framework is avilable under _application_controller_, with an Arduino example to get you started. Note that the application controller requires the https://github.com/NordicSemiconductor/ble-sdk-arduino[ble-sdk-arduino] framework. This allows you to operate an Arduino along with an nRF51 dev kit in the mesh, making it easier to create mesh applications. Each nRF51 example project has a separate target (named "nRF51822 xxAA serial") that incorporates the serial interface with the rest of the project.
  +The framework also has support for external control via SPI. The serial interface is based on the nRF8001 SPI interface, with different opcodes. An application controller framework is available under _application_controller_, with an Arduino example to get you started. Note that the application controller requires the https://github.com/NordicSemiconductor/ble-sdk-arduino[ble-sdk-arduino] framework. This allows you to operate an Arduino along with an nRF51 dev kit in the mesh, making it easier to create mesh applications. Each nRF51 example project has a separate target (named "nRF51822 xxAA serial") that incorporates the serial interface with the rest of the project.
   
   === Getting started
   
  
positive.code: 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
  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
  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 
  
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
  