Update README.md

Author: vsilaev

README.md

@@ -52,7 +52,7 @@ You have to add the following configuration to enable build-time instrumentation
 		</plugins>
 	</build>
 ```
-Note that if you are using continuations with Java 1.8 lambdas then you need to add Tascalate JavaFlow instrumentation agent at run-time as command-line option, while lambda-related classes are generated by JVM on the fly and there is no other way to instrument them.
+Note that if you are using continuations with Java 1.8 lambdas then you need to add [Tascalate JavaFlow instrumentation agent](https://github.com/vsilaev/tascalate-javaflow/releases/download/2.0/javaflow.instrument-continuations.jar) at run-time as command-line option, while lambda-related classes are generated by JVM on the fly and there is no other way to instrument them.
 
 Please refer to [pom.xml](https://github.com/vsilaev/tascalate-javaflow/blob/master/net.tascalate.javaflow.examples/pom.xml) in examples project for typical Maven configuration
 
@@ -78,4 +78,4 @@ It's possibe to instrument compiled Java classes as below:
         <javaflow srcdir="${jar.dir}" destdir="${i-jar.dir}" classpathref="classpath"/>
     </target>
 ```
-You may take a look at [examples project](https://github.com/vsilaev/tascalate-javaflow/tree/master/net.tascalate.javaflow.examples) for complete configuration template. Please pay attention to <code>ant-lib</code> folder with Ant TaskDef and <code>lib</code> folder with compile-/runtime-dependencies.
+You may download a complete [examples project setup](https://github.com/vsilaev/tascalate-javaflow/releases/download/2.0/tascalate-javaflow-ant-project-setup1.zip) from [the latest release](https://github.com/vsilaev/tascalate-javaflow/releases/tag/2.0) for complete configuration template. Please pay attention to <code>ant-lib</code> folder with Ant TaskDef and <code>lib</code> folders with compile-/runtime-dependencies.