README.md in fluent-plugin-latency-0.0.1 vs README.md in fluent-plugin-latency-0.0.2

@@ -2,19 +2,19 @@
 
 [![Build Status](https://secure.travis-ci.org/sonots/fluent-plugin-latency.png?branch=master)](http://travis-ci.org/sonots/fluent-plugin-latency)
 
 Fluentd plugin to measure latency until receiving the messages. 
 
-## What Is It For?
+## What is this for?
 
 This plugin is to investigate the network latency, in addition, the blocking situation of input plugins.
 
 In the Fluentd mechanism, input plugins usually blocks and will not receive a new data until the previous data processing finishes.
 
 By seeing the latency, you can easily find how long the blocking situation is occuring.
 
-## How It Works
+## How this works
 
 Fluentd messages include the time attribute which expresses the time of when the message is created, or when it is written in application logs.
 
 This plugin takes the difference between the current time and the time attribute to obtain the latency. 
 
@@ -25,11 +25,10 @@
     gem install fluent-plugin-latency
 
 ## Configuration
 
 Following example measures the max and average latency until receiving messages. 
-Note that this example uses [fluent-plugin-reemit](https://github.com/sonots/fluent-plugin-reemit) to capture all messages once, measure latencies, and then re-emit. 
 
 ```apache
 <source>
   type forward
   port 24224
@@ -38,25 +37,26 @@
 # Latency plugin output comes here
 <match latency>
   type stdout
 </match>
 
-# All messages come here once. Measure latencies and re-emit
+# Whatever you want to do
+<match rewrite.**>
+  type stdout
+</match>
+
+# All messages come here once. 
 <match **>
   type copy
   <store>
     type latency
     tag latency
     interval 60
   </store>
   <store>
-    type reemit
+    type rewrite
+    add_prefix rewrite
   </store>
-</match>
-
-# Whatever you want to do
-<match **>
-  type stdout
 </match>
 ```
 
 Output will be like