Index: design.html
===================================================================
--- design.html	(revision 1669688)
+++ design.html	(working copy)
@@ -179,7 +179,7 @@
     <li>A node must be able to maintain its session with ZooKeeper (via ZooKeeper's heartbeat mechanism)
     <li>If it is a slave it must replicate the writes happening on the leader and not fall "too far" behind
 </ol>
-We refer to nodes satisfying these two conditions as being "in sync" to avoid the vagueness of "alive" or "failed". The leader keeps track of the set of "in sync" nodes. If a follower dies, gets stuck, or falls behind, the leader will remove it from the list of in sync replicas. The definition of, how far behind is too far, is controlled by the replica.lag.max.messages configuration and the definition of a stuck replica is controlled by the replica.lag.time.max.ms configuration.
+We refer to nodes satisfying these two conditions as being "in sync" to avoid the vagueness of "alive" or "failed". The leader keeps track of the set of "in sync" nodes. If a follower dies, gets stuck, or falls behind, the leader will remove it from the list of in sync replicas. The definition of stuck and lagging replicas is controlled by the replica.lag.time.max.ms configuration.
 <p>
 In distributed systems terminology we only attempt to handle a "fail/recover" model of failures where nodes suddenly cease working and then later recover (perhaps without knowing that they have died). Kafka does not handle so-called "Byzantine" failures in which nodes produce arbitrary or malicious responses (perhaps due to bugs or foul play).
 <p>
Index: ops.html
===================================================================
--- ops.html	(revision 1669688)
+++ ops.html	(working copy)
@@ -318,7 +318,6 @@
 replica.socket.timeout.ms=30000
 replica.socket.receive.buffer.bytes=65536
 replica.lag.time.max.ms=10000
-replica.lag.max.messages=4000
 
 controller.socket.timeout.ms=30000
 controller.message.queue.size=10
@@ -528,12 +527,12 @@
     <tr>
       <td>Max lag in messages btw follower and leader replicas</td>
       <td>kafka.server:type=ReplicaFetcherManager,name=MaxLag,clientId=Replica</td>
-      <td>&lt replica.lag.max.messages</td>
+      <td>lag should be proportional to the maximum batch size of a produce request.</td>
     </tr>
     <tr>
       <td>Lag in messages per follower replica</td>
       <td>kafka.server:type=FetcherLagMetrics,name=ConsumerLag,clientId=([-.\w]+),topic=([-.\w]+),partition=([0-9]+)</td>
-      <td>&lt replica.lag.max.messages</td>
+      <td>lag should be proportional to the maximum batch size of a produce request.</td>
     </tr>
     <tr>
       <td>Requests waiting in the producer purgatory</td>