typo

Shlomi Noach · Shlomi Noach · commit 3bf64d8280b7 · 2016-12-27T09:16:27.000+02:00
diff --git a/doc/subsecond-lag.md b/doc/subsecond-lag.md
@@ -16,4 +16,4 @@ You can explicitly define how frequently will `gh-ost` inject heartbeat events,
 
 In earlier versions, the `--throttle-control-replicas` list was subjected to `1` second resolution or to 3rd party heartbeat injections such as `pt-heartbeat`. This is no longer the case. The argument `--replication-lag-query` has been deprecated and no longer needed.
 
-Our production migrations use sub-second lag throttling and are able to keep our entire fleet of replicas well below `1sec` lag. We use `--heartbeat-interval-millis=100` on our production migrations with a `--mas-lag-millis` value of between `300` and `500`.
+Our production migrations use sub-second lag throttling and are able to keep our entire fleet of replicas well below `1sec` lag. We use `--heartbeat-interval-millis=100` on our production migrations with a `--max-lag-millis` value of between `300` and `500`.

Original file line number	Diff line number	Diff line change
@@ -16,4 +16,4 @@ You can explicitly define how frequently will `gh-ost` inject heartbeat events,
`16`	`16`
`17`	`17`	In earlier versions, the `--throttle-control-replicas` list was subjected to `1` second resolution or to 3rd party heartbeat injections such as `pt-heartbeat`. This is no longer the case. The argument `--replication-lag-query` has been deprecated and no longer needed.
`18`	`18`
`19`		-Our production migrations use sub-second lag throttling and are able to keep our entire fleet of replicas well below `1sec` lag. We use `--heartbeat-interval-millis=100` on our production migrations with a `--mas-lag-millis` value of between `300` and `500`.
	`19`	+Our production migrations use sub-second lag throttling and are able to keep our entire fleet of replicas well below `1sec` lag. We use `--heartbeat-interval-millis=100` on our production migrations with a `--max-lag-millis` value of between `300` and `500`.