diff --git a/tools/README-jack-code-coverage.md b/tools/README-jack-code-coverage.md
index f706289..d1be035 100644
--- a/tools/README-jack-code-coverage.md
+++ b/tools/README-jack-code-coverage.md
@@ -8,6 +8,9 @@
 Besides, Jack will also produce a coverage metadata file (or description file) in a JSON format.
 It will be used to generate the report so we can match coverage execution file with source code.
 
+Starting with the Jack Douarn release (4.x), the code coverage is provided with the Jack plugin
+`jack-coverage-plugin.jar`.
+
 ## Enabling code coverage with Jack
 
 ### Using the Android build system
@@ -35,24 +38,38 @@
 
 ### Using Jack command-line
 
-To enable code coverage with Jack command-line, pass the following property flags:
+To enable code coverage with Jack command-line, pass the following command-line options:
 
->  -D jack.coverage=true  
->  -D jack.coverage.metadata.file=<coverage_metadata_file_path>  
->  -D jack.coverage.jacoco.package=<jacoco_internal_package_name>
+```
+--pluginpath <code_coverage_plugin_jar>
+--plugin com.android.jack.coverage.CodeCoverage
+-D jack.coverage=true
+-D jack.coverage.metadata.file=<coverage_metadata_file_path>
+-D jack.coverage.jacoco.package=<jacoco_internal_package_name>
+```
 
 where
-* `<coverage_metadata_file_path>` is the path of the file that will contain coverage information
-                                to generate the report
-* `<jacoco_internal_package_name>` is the name of the internal package name containing the class
-                                 'Offline' in the associated jacoco-agent.jar file. This package
-                                 name is different for each release of JaCoCo.
-                                 (Note: this may be removed in the future)
+* `<code_coverage_plugin_jar>` is the path to the plugin jar file. In the Android tree, it is
+  located in the `prebuilts/sdk/tools` directory.
+* `<coverage_metadata_file_path>` is a *mandatory* property that indicates the path of the file that
+  will contain coverage information. This file must be passed to reporting tool to generate the
+  report (see section Generating the report below)
+* `<jacoco_internal_package_name>` is an *optional* property that indicates the fully qualified name
+  of the internal package name containing the class 'Offline' in the associated jacoco-agent.jar
+  file. This package name is different for each release of JaCoCo library. If this property is not
+  provided, Jack will automatically look for a Jacoco package which starts with
+  `org.jacoco.agent.rt.internal`.
 
-Jack also supports include and exclude filtering based on class name:
+Note: because Jack's code coverage support is based on Jacoco, it is mandatory that Jacoco classes
+are available at compilation time. They can be either on the classpath (--classpath) or imported
+as a static library in the output (--import).
 
-> -D jack.coverage.jacoco.include=<includes>  
-> -D jack.coverage.jacoco.exclude=<excludes>
+Jack also supports optional include and exclude class filtering based on class name:
+
+```
+-D jack.coverage.jacoco.include=<includes>
+-D jack.coverage.jacoco.exclude=<excludes>
+```
 
 where
 * `<includes>` is a comma-separated list of fully-qualified class names to include
@@ -61,6 +78,14 @@
 Wildcards characters '?' and '*' are accepted to replace respectively one character or multiple
 characters.
 
+You can find the full command-line usage with
+
+    java -jar <jack_jar> --help
+
+You can also find the description of all properties (including those for code coverage) with
+
+    java -jar <jack_jar> --pluginpath <code_coverage_plugin_jar> --plugin com.android.jack.coverage.CodeCoverage --help-properties
+
 ## Collecting code coverage
 
 To produce coverage execution data, instrumented classes must be executed and coverage data be
@@ -81,8 +106,8 @@
 A coverage report can be generated using the `jack-jacoco-reporter.jar` file. This is a command-line
 tool taking at least three inputs:
 
-* the coverage metadata file produced by Jack
-* the coverage execution file produced during execution
+* the coverage metadata file(s) produced by Jack
+* the coverage execution file(s) produced during execution
 * an existing directory where the report is generated
 
 It is also recommended to indicate the directories containing the source code of classes being