anchor.diff:  
   ### The IDE
   
  -Well, I won't go into an IDE war, this is far from being the point of article.
  +Well, I won't go into an IDE war, this is far from being the point of the article.
   Your favorite java IDE (with potentially a groovy support plugin) will do the trick.
   
   That being said, you can do more than having a simple groovy IDE, you can also teach your IDE to understand the DSL used by Jenkins!
   This works thanks to the GroovyDSL (GDSL).
  -A GDSL is a basically a file that will describe the meta language that a DSL uses.
  +A GDSL is basically a file that will describe the meta language that a DSL uses.
   By putting this file in the classpath of a groovy project, your IDE will be able to assist you write code that follows the DSL.
  -Good news is that the Jenkins pipeline expose a GDSL.
  -Go to *$jenkins_base_url/pipeline_syntax/gdsl* to get it.
  +The good news is that the Jenkins pipeline exposes a GDSL.
  +Go to _$jenkins_base_url/pipeline_syntax/gdsl_ to get it.
   Then add this file in the classpath of your project and voilà, your IDE can now autocomplete!
   
   Note that I only tested this feature in Intellij, but this should work in other groovy compatible IDEs.
  -Also, plugins might enrich the DSL without being described in the GDSL.
  +Also, plugins might enrich the DSL without being described in the GDSL, so don't expect the autocomplete to be absolutely complete.
   
   ### The linter
   
   During development of a pipeline, it's easy to make a typo in your Jenkinsfile and end up with an invalide Jenkinsfile.
   This is a pain, as you lose time understanding the mistake, fix it, commit the fix and push it.
  -Good news it that there is a way to shorten this feedback loop.
  +The good news is that there is a way to shorten this feedback loop.
   
   Jenkins offers a linter for your Jenkinsfile.
  -Best way to use the linter is to the JenkinsCLI.
  +Best way to use the linter is with the JenkinsCLI.
   You will need the https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Model+Definition+Plugin[Pipeline Model Definition] version 0.7 at least.
   You can then ask Jenkins to lint your Jenkinsfile:
   
  
positive.code: * The syntax might be cumbersome
  * Some parameters might seem obscure
  
  Good news is that there is a Pipeline Syntax page in Jenkins that is here to:
  
  * Help you understand the different options you have
  * Generate some code snippets for you
  
  You can reach this page by browsing *$jenkins_base_url/pipeline_syntax*.
  I won't go into details, the usage of the page is pretty self explanatory, you choose the step you wish to generate, then you fill in the options as you would in a good old freestyle job (click on the quotemarks if you need assistance), and finally you click the `Generate Pipeline Script` button to get your snippet.
  On the following screenshot, I generated a junit step.
  Note the presence of the help button (right red arrow) that allowed me to quickly understand the 'Retain long standard output/error' (which finally translated into *keepLingStdio* in the code):
  
  image::https://github.com/PierreBtz/pierrebtz.github.io/raw/master/images/writing-Jenkinsfile.png[Pipeline Syntax Page]
  
  The final part of the Pipeline Syntax page (circled in red in the screenshot) is a reference of many variables you have access to in the pipeline.
  
  Like for the GDSL, plugin sadly do not always support that page.
  
  
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]
  