anchor.diff:  }
   ----
   
  -Then expose the function in the _timeslot_handler.h_ header. This function should be called from the `static void sys_evt_dispatch(uint32_t sys_evt)` function in _main.c_ (around L885), with sys_evt as parameter. This leaves the consumation of the event to the softdevice-handler, and other modules, such as pstorage won't miss out on incoming system events.
  +Then expose the function in the _timeslot_handler.h_ header. This function should be called from the `static void sys_evt_dispatch(uint32_t sys_evt)` function in _main.c_, with sys_evt as parameter. This leaves the consumation of the event to the softdevice-handler, and other modules, such as pstorage won't miss out on incoming system events.
   
   === Step 4: Picking up BLE events
   The next step is also exhibited in the BLE_Gateway example in the framework: we need to get the BLE events from the Softdevice. This is necessary if we want the mesh to react to changes made to the Softdevice GATT server by external devices through a regular Softdevice connection, as the framework is unable to pull these events directly from the Softdevice without a little help. 
   
  -All that is required for this step is to add this line to the end of `static void ble_evt_dispatch(ble_evt_t * p_ble_evt)` in _main.c_ (around L865):
  +All that is required for this step is to add this line to the end of `static void ble_evt_dispatch(ble_evt_t * p_ble_evt)` in _main.c_:
   
   [source,c]
  -.main.c:L874
  +.main.c
   ----
   rbc_mesh_ble_evt_handler(p_ble_evt);
   ----
  
positive.code: === Step 3: Softdevice event handler
  The rbc_mesh has to check for Softdevice events related to the Timeslot API in order to function. In the original framework, this is conducted in the function `ts_sd_event_handler(void)` in _timeslot_handler.c_. This function is not very considerate of other Softdevice related activities on the chip, however, and consumes the SD_events as they come. In order to overcome this, we can replace it with a more cooperative version. Delete the `ts_sd_event_handler(void)` function and all its references, and insert this function instead: 
  [source,c]
  .timeslot_handler.c:L246
  ----
  void rbc_mesh_sys_evt_handler(uint32_t evt)
  {
  
negative.code: In order to get feedback from the rbc_mesh, the application must implement `void rbc_mesh_event_handler(rbc_mesh_event_t* evt)` somewhere in the application space. See the examples under _/nRF51/examples/_ for implementations of this function.
  
  === Step 6: initialization
  The final step is to initialize the rbc_mesh framework. First off, the framework calls `sd_ble_enable()` in _mesh_srv.c_. This is already done as part of the initialization in the Proximity example, and can be left out of the _mesh_srv.c_ code. Remove the line calling the Softdevice function.
  
  Finally, we must initialize the framework from the application. This is also displayed in the examples under _/nRF51/examples/_, but note that `uint32_t rbc_mesh_init(rbc_mesh_init_params_t)` must be called after `ble_stack_init()` in the application in order to secure correct behavior (more specifically, after `sd_ble_enable()`). We also recommend that you initialize the framework before you start advertising, to ensure that the application includes the mesh service in its GATT server for external devices.
  
  