anchor.diff:  #!/usr/bin/groovy
   
   notifiableBuild {
  -	//put here all your pipeline
  -}
  -----
  -
  -To learn more about this, you should the https://jenkins.io/doc/book/pipeline/shared-libraries/[official documentation of the plugin], which will help you getting started.
  +    //put here all your pipeline
  +}
  +----
  +
  +To learn more about this, you should visit the https://jenkins.io/doc/book/pipeline/shared-libraries/[official documentation of the plugin], which will help you getting started.
   
   ## The Experimental Corner
   
   In this part, I will share two projects you should keep an eye on as they should help a bit more spreading the usage of the pipelines.
  -Note that the two projects are a very early stage of development.
  +Note that the two projects are at a very early stage of development.
   
   ### Jenkins Blue Ocean Pipeline Editor Plugin
   
   https://github.com/jenkinsci/blueocean-pipeline-editor-plugin[This plugin] is using the https://jenkins.io/projects/blueocean/[Blue Ocean interface].
  -Side note, if you don't know it, you should definitively have a look as it is far superior to the Jenkins 'classic' interface to display pipelines.
  +Side note, if you don't know Blue Ocean, you should definitively have a look as it is far superior to the Jenkins 'classic' interface to display pipelines.
   Note that it is also work in progress (it is in a beta stage), but I use it in production everyday without any issue (except for the missing features of course).
   
  -That being said, this new Pipeline Editor plugin is a new interface to graphically design your pipeline.
  -This is at very alpha stage, but it was https://youtu.be/TsWkZLLU-s4?t=22m35s[demonstrated in the last Jenkins Meetup] (note that the rest of the meetup is also worth your time if you are into Jenkins).
  +That being said, this new Pipeline Editor plugin proposes a new interface to graphically design your pipeline.
  +This is at very alpha stage, but it was https://youtu.be/TsWkZLLU-s4?t=22m35s[demonstrated in the last Jenkins Meetup] (note that the rest of the meetup is also worth your time if you are into Jenkins) and seems very promising.
   
   ### Declarative Pipeline
   
  
positive.code: #!/usr/bin/groovy
  
  def call(body) {
  	try {
  		notify(start)
      	body()
      	notify(success)
  	} catch(exception) {
  		notify(failure)
      }
  }
  
  def notify(state) {
  	//notify scm
  }
  ----
  
  
negative.code: Its aim is to give a more config like touch to the pipeline.
  Code vs Config, here we are again (let's not replay maven vs gradle and gulp vs grunt all over again...)!
  Again, the plugin was https://youtu.be/TsWkZLLU-s4?t=27m35s[demoed in the last Jenkins Online Meetup].
  The API does not seem stable for the moment, but some stuff seems very interesting.
  For instance, the notification issue I raised before could be adressed with something like:
  
  [source, groovy]
  