anchor.diff:  In all cases, the client will need sufficient network access to be able to write to the
   Azure storage and Service Bus accounts used by the MBrace runtime/cluster nodes.
   
  -## Using a Cloud Service for the MBrace Runtime
  +## Authoring a Cloud Service which uses the MBrace Runtime
   
  -This is the normal option.
  +This is the normal option when provisioning eplicitly.
   
   See [using an Azure cloud service for the MBrace runtime instances](https://github.com/mbraceproject/MBrace.Demos/blob/master/azure/AZURE.md).
   
  
positive.code: 
  In this tutorial you will learn how to setup MBrace on Windows Azure.
  
  ## Using Brisk Engine to Provision
  
  The easiest path to provision an MBrace cluster on Azure using
  an Azure Cloud Service is to use Brisk Engine.
  See the [Brisk Engine Tutorial](brisk-tutorial.html).
  
  ## Provisioning Explicitly
  
  In some cases you may decide to provision explicitly.  For example, you may want your cloud service
  to have access to endpoint funcitonality not yet available via the Brisk Engine provisioning
  service.
  
  As a prerequisite you need to have a Windows Azure account, basic knowledge of the Azure computing and
  optionally Microsoft Visual Studio (or any environment supporting F#).
  
  
  Typically you will host your MBrace runtime/cluster nodes in one of
  
  * explicit virtual machines (VMs); or
  
  * the VMs of an Azure cloud service; or 
  
  * the execution environment of an Azure web job.
  
  
negative.code: the Windows Azure VPN service to join the virtual network created in Azure 
  and access the runtime from a remote client (your on-premises computer).
  
  If you use a virtual network, create and upload certificates and finally configure your VPN client. 
  The process is described in [here](http://msdn.microsoft.com/en-us/library/azure/dn133792.aspx).
  
  