From c3ed7005bac24097819348d69b270f4af2c07026 Mon Sep 17 00:00:00 2001
From: Kostya Serebryany <konstantin.s.serebryany@gmail.com>
Date: Mon, 21 Nov 2016 13:25:39 -0800
Subject: [PATCH] Update reproducing.md

---
 docs/reproducing.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/reproducing.md b/docs/reproducing.md
index cda93445f..0aa3a47f1 100644
--- a/docs/reproducing.md
+++ b/docs/reproducing.md
@@ -21,13 +21,15 @@ If you are not sure how to build the fuzzer using the project's build system,
 you may also use the Docker ([how?](installing_docker.md), [why?](faq.md#why-do-you-use-docker)) commands 
 to replicate the exact build steps used by OSS-Fuzz and then feed the reproducer input to the target.
 
-- *Reproduce using the most recent successfull OSS-Fuzz build:* 
+- *Reproduce using the latest OSS-Fuzz build:* 
 
    <pre>
 docker run --rm -v <b><i>$testcase_file</i></b>:/testcase -t ossfuzz/<b><i>$target</i></b> reproduce <b><i>$fuzzer</i></b>
    </pre>
 
-  It builds the fuzzer from nightly sources (in the image) and runs it with testcase input.
+  It builds the fuzzer from  the most recent successfull OSS-Fuzz build (roughly, last night's sources)
+  and feeds the testcase file to the target function. 
+  
   E.g. for the [libxml2](../target/libxml2) fuzzer named `libxml2_xml_read_memory_fuzzer` it will be: 
   
    <pre>