anchor.diff:    deployments also provide the ability to transition from an existing deployment (_v1_ for instance) of an image to a new
     one (_v2_ for instance) and also define hooks to be run before or after creating the replication controller.
   
  -Openshift deployments proposes a set of strategy. One of them named _rolling_ implements a rolling updates and ensure
  - that you don't disrupt your service. Before stopping the pod, it ensures that the new _version_ is alive and ready.
  - Then it routes requests to this new pod and dispose the old one.
  +Openshift deployments propose a set of strategies. The default is _rolling_ which implements (as the name implies) rolling 
  +updates and ensures that you don't disrupt your service. Before stopping the pod, it ensures that the new _version_ is alive and 
  +ready. Then, it routes requests to this new pod and dispose the old one.  Other strategies provided include _recreate_, 
  +_blue-green_, _A/B_, and the ability to create a custom strategy.
   
   #### Build and Image
   
  -As said in the previous section, `deployments` are responsible to keep the application running. But we need to
  -provide this application first. This application is pushed to OpenShift as an (container) _image_. This image is
  +As stated in the previous section, `deployments` are responsible for keeping the application running. But we need to
  +provide the application first. The application is pushed to OpenShift as an (container) _image_. This image is
   created by a _build_ and instantiated by the _deployment_.
   
   A build is the process of transforming your code into an image. The process is described in a `BuildConfig` object. Build
  
positive.code: oc policy add-role-to-group view system:serviceaccounts -n vertx-kubernetes-workshop
  ----
  
  The first instruction creates the project. The 3 last instructions grants permissions in order to use all the
  OpenShift capabilities.
  
  In the OpenShift Web Console, you should see the newly created project. Click on it. It's empty, let's deploy our
  first application.
  
  In the workshop source code, locate the `currency-3rdparty-service`, and navigate in the directory in your terminal.
  Then issue the `mvn fabric8:deploy` command:
  
  [source, bash]
  ----
  
negative.code: 
  We are going to use _minishift_ (https://github.com/minishift/minishift) to run OpenShift locally on your machine.
  
  Before starting minishift, you need to install a hypervisor. Check the https://docs.openshift.org/latest/minishift/getting-started/installing.html 
  to check what are the supported ones for your operating system. When in doubt, use VirtualBox (https://www.virtualbox.org/wiki/Downloads). 
  Be sure to have a hypervisor before continuing.
  
  If not already done, download the latest release from https://github.com/minishift/minishift/releases (do not
  use beta). Download the archive and copy the `minishift` executable in the directory of your choice. Add this
  directory to your system `$PATH`. 
  
  